[BUG] Side-effect of "slowready" being default of "toggleready"

[suddendeathTV]

Describe the bug
If multiple players are slowready (I think that's what it was called?) @tcsabina meaning your ready status is maintained after changing maps, and a map is changed, the game will start depending on who loads the next map first.

To explain further, imagine a 2on2 game with 4 players. Players 1 and 3 are slowready (or toggleready), Players 2 and 4 are not. If they vote a different map, if players 1 and 3 load in quicker, the match will start and player 2 and 4 will be kicked off the server with the error code being that a game is already in process. Players 1 and 3 remain in a 2on2 but with only 2 players-situation.

To Reproduce
Steps to reproduce the behavior:

1. Go to any gamemode with multiple players and go slowready/toggleready
2. Vote for a map change
3. Expect match on new map to begin immediately if ready tagged players load in first

Expected behavior
Match should not start when only some of the players are ready, and should not boot non-ready players off when server changes map.

Additional context
This may mean slowready inherently can't work, as I doubt the server knows which players load in first and only checks for the ready tag. Ergo, the issue may be in the functionality of slowready rather than the server.

[BLooD-DoG]

Not sure if exactly the same thing (I use /ready and not /toggleready), but in NA we've experienced some side effects that might be related to this too.

After a map ends and you change maps, everyone is unexpectedly already /ready. There is sometimes confusion that one person has to /break then /ready again to start the next map, which is weird.

Also, usually someone stepped away during the map change so the "quick" map start is also not good because we have to /break the game after countdown and re-ready when everyone is back. People don't expect to automatically be /ready for the next map during map change.