-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Small issue] If you pause bots, they get disconnected due to inactivity. #165
Comments
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
I think somewhere in commit history there were However that one seems about killing bots in Elimination in order for humans to wait less before respawning (by forcing a random winner by randomly killing bots? :-/ Or by following some criteria like the health left at that moment? I don't know...)" ... while this issue instead looks like related to some mechanism meant to kick inactive human players (which have their connection interrupted?), but being mistakenly also applied to bots. I'll try to make a few tests later. |
This comment was marked as abuse.
This comment was marked as abuse.
About the topic of this issue (bots kicked), I just tested in B53, following the example of the opening post, and the bot still got kicked after three minutes. About the side topic of the "killing bots in eliminitation mode when no human players are left", the current implementation seems good enough to me, as it looks like if the teams were composed only of bots since the start, then the feature doesn't kick in. I should do a few more test to check whether it considers "since the start" of the whole match or of the single round. |
This comment was marked as abuse.
This comment was marked as abuse.
That's fine for me. Maybe even the 5hp/sec is a bit too much, as maybe 3hp/sec might alrady be enough... But my tests of today were too few to tell for sure. |
Description:
This is just a small issue because it's only relevant to a few development/testing scenarios, however I write it down anyway, as it actually happened to me while doing a few tests.
If you "pause" bots, they will be "disconnected" after three minutes, due to inactivity. In case you are doing some testing which requires to keep them quiet, stationary and unaggressive for a long time, this can be a problem.
How to reproduce:
UPDATE: It looks like the above happens with non-team-based modes (I tested gametype 0): in team-based modes (I tested 3, 5 and 8) the bot disconnects earlier (like one minute and half?) and with "server command overflow" in console instead of "timed out".
Suggested behavior:
I guess the inactivity check routine should verify whether the client is a bot, and whether bot_pause<>0: if both are true, the client should not be disconnected, assuming that there is a developer/tester which is purposedly testing something.
Or maybe just ignore bots at all?
The text was updated successfully, but these errors were encountered: