MantisBT - Zandronum
View Issue Details
0000748Zandronum[All Projects] Bugpublic2012-04-01 01:252013-09-27 10:39
Dusk 
Dusk 
normalminoralways
confirmedopen 
1.0-beta 
 
0000748: Survival desync when changemap happens during mission failure
When the last player dies, the big message "MISSION FAILED!" shows up and all players freeze. If a changemap happens during this period, mission failure will carry on to the next map.

In this state, players will be frozen - but they don't think they are, causing a desync as the client attempts to move but the server keeps them in place.

I believe that the best way to handle this situation is to clear mission failure and skip to the countdown on a changemap like this.
Attached a demo detailing the problem so as to demonstrate what's going on.
No tags attached.
zip surv_missfail_desync.cld.zip (16,402) 2012-04-01 01:30
https://zandronum.com/tracker/file_download.php?file_id=506&type=bug
Issue History
2012-04-01 01:25DuskNew Issue
2012-04-01 01:25DuskStatusnew => assigned
2012-04-01 01:25DuskAssigned To => Dusk
2012-04-01 01:30DuskFile Added: surv_missfail_desync.cld.zip
2012-04-01 01:31DuskAdditional Information Updatedbug_revision_view_page.php?rev_id=1603#r1603
2012-04-01 02:35Torr SamahoNote Added: 0003074
2012-04-01 02:35Torr SamahoNote Edited: 0003074bug_revision_view_page.php?bugnote_id=3074#r1605
2012-04-01 19:18unknownnaNote Added: 0003085
2012-06-09 13:22Torr SamahoCategoryGeneral => Bug
2013-09-27 10:39DuskStatusassigned => confirmed

Notes
(0003074)
Torr Samaho   
2012-04-01 02:35   
> If a changemap happens during this period, mission failure will carry on to the next map.

FYI, some time ago I made some changes to forbid map changes during the survival countdown. Probably we should extend this to forbid map changes also during the mission failed sequence.

(0003085)
unknownna   
2012-04-01 19:18   
> Probably we should extend this to forbid map changes also during the mission failed sequence.

Make sure to extend this to all the other win/lose sequences as well. I noticed this in TeamPossession too.