MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000385Zandronum[All Projects] Bugpublic2011-04-18 21:252018-09-30 20:07
Reporterunknownna 
Assigned ToTorr Samaho 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version98d 
Target VersionFixed in Version1.0 
Summary0000385: Dead TLMS spectators and sv_keepteams 1
DescriptionContinued from: 0000203: sv_keepteams + changemap == can't join same team

If you are a dead team spectator and a changemap/nextmap map change takes place, you'll be a dead team spectator in the next map.
Steps To Reproduce1. Start a standard TLMS server. Make sure that sv_keepteams is set to 1.
2. Connect a client to the server.
3. Join the game.
4. Add 3 bots.
5. When the warm-up countdown ends, "kill" in the console.
6. After turning into a spectator, "changemap X/nextmap" in the server console.
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng Screenshot_Doom_20110418_232235.png (38,956) 2011-04-18 21:25
/tracker/file_download.php?file_id=251&type=bug
png

png Screenshot_Doom_20110418_234420.png (26,940) 2011-04-18 21:44
/tracker/file_download.php?file_id=252&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2011-04-18 21:25unknownnaNew Issue
2011-04-18 21:25unknownnaFile Added: Screenshot_Doom_20110418_232235.png
2011-04-18 21:33unknownnaDescription Updatedbug_revision_view_page.php?rev_id=727#r727
2011-04-18 21:41unknownnaNote Added: 0001397
2011-04-18 21:44unknownnaFile Added: Screenshot_Doom_20110418_234420.png
2011-04-18 22:52unknownnaNote Edited: 0001397bug_revision_view_page.php?bugnote_id=1397#r729
2011-04-23 15:00Torr SamahoNote Added: 0001410
2011-04-23 15:00Torr SamahoAssigned To => Torr Samaho
2011-04-23 15:00Torr SamahoStatusnew => feedback
2011-04-23 20:12unknownnaNote Added: 0001414
2011-04-23 20:12unknownnaStatusfeedback => assigned
2011-04-23 21:22Torr SamahoNote Added: 0001417
2011-04-23 21:22Torr SamahoStatusassigned => feedback
2011-04-23 21:45unknownnaNote Added: 0001420
2011-04-23 21:45unknownnaStatusfeedback => assigned
2011-04-23 22:59Torr SamahoStatusassigned => resolved
2011-04-23 22:59Torr SamahoFixed in Version => 1.0
2011-04-23 22:59Torr SamahoResolutionopen => fixed
2012-06-09 13:22Torr SamahoCategoryGeneral => Bug
2018-09-30 20:07Blzut3Statusresolved => closed

Notes
(0001397)
unknownna   
2011-04-18 21:41   
(edited on: 2011-04-18 22:52)
This also breaks the team slots for bots. If a bot is dead before a changemap/nextmap map change, it might join the opposite team in the next map.

Edit:

This also happens offline.
(0001410)
Torr Samaho   
2011-04-23 15:00   
This hopefully fixes the problem (I didn't test the bot specific part though). Note: To fix this properly I needed to unify how dead spectators are treated after a map change, so the fix may also have an influence on survival and survival invasion.
(0001414)
unknownna   
2011-04-23 20:12   
> This hopefully fixes the problem (I didn't test the bot specific part though).

It seems that it took care of both issues.

> Note: To fix this properly I needed to unify how dead spectators are treated after a map change, so the fix may also have an influence on survival and survival invasion.

In regular survival, a spectator waiting in line in the former map will not be able to join the game after a changemap/nextmap map change. This is a major issue.

I also found a separate issue: If a survival invasion game is in effect, a changemap map change to one of the vanilla maps will turn the game into cooperative, but with the lives counter in effect. Should I create a new ticket for this issue?
(0001417)
Torr Samaho   
2011-04-23 21:22   
> In regular survival, a spectator waiting in line in the former map will not be able to join the game after a changemap/nextmap map change. This is a major issue.

Yeah, that's serious. This should fix it.

> Should I create a new ticket for this issue?

Please do so. This is a completely separate issue.
(0001420)
unknownna   
2011-04-23 21:45   
It fixed the issue. You may mark this ticket as resolved for now.