-
Notifications
You must be signed in to change notification settings - Fork 4
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
Initial infection is out of order #126
Comments
If there are players A, B, C, D and player S is spectating, instead of infecting [A, B], then [C, D], then [A, B], one of the players, for example, A will always be chosen to become initial zombie and initial infected will be [A, B], [A, C], [A, D].
The steps do not mention people reconnecting |
I came up with the following patch on my server |
My assumption is that If a client is tagged with "m_WasInfected" which is a consequence of InfecteClient(), then this client can't get infected the next round. |
This is a bug, yes. I think this bug is "better" than one client always getting infected.
I don't understand. What is the consequence of the bug? How does it affect the behavior? |
Thanks for further details. feature outline: after infection trigger
initiation 1:
fair infection process:
initiation 2:
unfair infection process:
|
Steps to reproduce:
Expected: initial infected are chosen in order
Observed: after some time, almost always one person gets selected to become initial zombie
This is not reproducible on oi8306. This is reproducible on test oi8306 or any other server based on current
master
.The text was updated successfully, but these errors were encountered: