MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000561Zandronum[All Projects] Bugpublic2011-08-15 06:002014-06-11 18:13
Reportercq75 
Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
StatusconfirmedResolutionopen 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version98d 
Target VersionFixed in Version 
Summary0000561: Repeated Changemaps during intermission causes all players to timeout
DescriptionThis effect changes based on game mode.

It was also tested in the 98E Alpha, r3299
Steps To Reproduce1. Start a server (for this test, I started on Doom 2 MAP01)
2. Type Changemap MAP02
3. During intermission, type

changemap map02
changemap map03
...
changemap map10 (only spectators will be timed out)
changemap map11 (all players will be timed out)

In CTF, it's different.

(starting at d2ctf1)
changemap d2ctf2
changemap d2ctf3
...
changemap d2ctf8 (spectators time out)
changemap d2ctf9 (all players time out)

if you tell it to change to a nonsense/nonexistent map before the last map change, you can get different results

(starting at d2ctf1)
changemap d2ctf2
changemap d2ctf3
...
changemap nonsense
changemap d2ctf6 (all players time out)


Also, if you repeatedly change to the same map, it takes at least 50 changemap commands to cause this effect.
Additional InformationIt is possible that this effect is intensified as the number of players on the server increases. At the time of the test, I only had two (one playing, one spectating), but during the official beta testing server, there were at least 7 players on my server. I remember that it was much easier to make all of the players time out when there were more participants.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-08-15 06:00cq75New Issue
2011-08-17 16:00DuskNote Added: 0002127
2011-08-17 16:00DuskNote Edited: 0002127bug_revision_view_page.php?bugnote_id=2127#r1104
2012-06-09 13:22Torr SamahoCategoryGeneral => Bug
2014-06-11 16:11WatermelonNote Added: 0009059
2014-06-11 16:11WatermelonStatusnew => feedback
2014-06-11 18:08FritsNote Added: 0009085
2014-06-11 18:13WatermelonNote Added: 0009089
2014-06-11 18:13WatermelonStatusfeedback => confirmed

Notes
(0002127)
Dusk   
2011-08-17 16:00   
"It is possible that this effect is intensified as the number of players on the server increases."
This is probably true - back then I accidentally triggered this on a rather full AOW server and after like 2-3 changemaps everybody timed out.
(0009059)
Watermelon   
2014-06-11 16:11   
Does this happen in 2.0?
(0009085)
Frits   
2014-06-11 18:08   
still present in zan 2.0
The more changemap is called during an intermission the longer the delay before the map switches/a time-out for clients happens.
It's possible to make myself timeout on a lan server but it's alot harder than using for example a grandvoid server.
(0009089)
Watermelon   
2014-06-11 18:13   
Thanks yet again for checking

I'm wondering if the server floods the client while trying to re-auth every time.

The question is if there should be some kind of limit on how fast users can change, or when? Ex: should users be only able to change after a map is fully loaded? Or after all the map loading instructions were sent out? I'm unsure if zan just piles all the map updates into a buffer and deploys it... if it does, then we're probably toast in this case