Category: Code
Reproducibility: Always
Summary: The wave zed count is affected by players that aren't playing yet.
Description: Players that join a server midgame but haven't readied up yet, so they're not playing yet for the wave, count toward the number of zeds that will spawn in that wave.
Example: Wave 3/10 solo Suicidal should have 41 zeds,
but since I joined this server that had one person on it and couldn't ready up before the end of trader time, this Sui wave 3/10 with one player playing had >74 zeds.
(they had killed some zeds before the screenshot. I think it would've been 83 zeds, for 2pSui W3/10)
I've seen this happen where multiple players that aren't playing yet get counted; this can make a wave a real endurance match for one player, and an extra wait for the people not yet playing.
Along with including the unreadied players, I suspect it may also include those that have connected to the server but not even loaded the map yet, though I can't confirm that.
Online/Offline: Online
Reproducibility: Always
Summary: The wave zed count is affected by players that aren't playing yet.
Description: Players that join a server midgame but haven't readied up yet, so they're not playing yet for the wave, count toward the number of zeds that will spawn in that wave.
Example: Wave 3/10 solo Suicidal should have 41 zeds,
but since I joined this server that had one person on it and couldn't ready up before the end of trader time, this Sui wave 3/10 with one player playing had >74 zeds.
(they had killed some zeds before the screenshot. I think it would've been 83 zeds, for 2pSui W3/10)
I've seen this happen where multiple players that aren't playing yet get counted; this can make a wave a real endurance match for one player, and an extra wait for the people not yet playing.
Along with including the unreadied players, I suspect it may also include those that have connected to the server but not even loaded the map yet, though I can't confirm that.
Online/Offline: Online
Last edited: