-
Notifications
You must be signed in to change notification settings - Fork 141
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
SI player can be assigned multiple tanks in a row in finale #851
Comments
The commit below will probably solve this problem, I will test it for a few days and get back to you. |
I'm confused, considering what you're describing is part of the plugin's logic. |
I see what you are saying and while the tank selection process is inherently fair in terms of giving everyone an equal chance at playing as tank, I believe issues arise when other factors are considered:
So by preventing duplicate consecutive tank selection in the finale, perceived imbalance and player frustration can be minimized while still ensuring that everyone has their fair share of time as tank. This also adds variety to the tank fights, making the finale more dynamic and enjoyable for everyone. |
Sometimes in the finale, one player can get tank twice in a row.
I believe this occurs when:
a) there are less than 5 maps in a campaign
b) the survivors wipe before spawning tanks on early maps.
c) all of the above
I think this is because if the initial tank player queue isn't exhausted before the finale map, the 4th player will get the first finale tank, and then the queue will be reset and that player will be put back into the queue and have the chance to play tank again in that same finale map, creating the potential for a situation where the same player plays tank in finale twice in a row.
Maybe after the first tank in the finale (or any map with more than 1 tank), exclude that player from being selected again during that round until the other 3 players have had their chance to play tank. If all other players have already played tank once during the round, then allow the queue to reset. (this would also account for weird custom maps/servers/mods when a map has 4+ tanks in a round).
The text was updated successfully, but these errors were encountered: