MantisBT - Zandronum
View Issue Details
0000185Zandronum[All Projects] Bugpublic2010-11-08 15:272018-09-30 22:36
Anonymous 
 
lowtrivialalways
closedfixed 
MicrosoftWindowsXP/Vista/7
98c 
 
0000185: [98d actually] Single player "spectate" and "nextmap" shenanigans
When in single player mode, the player types "spectate" on a map then uses "nextmap", the player will start the next map as a spectator, however, when player joins, (s)he is still able to fly and the weapon is not shown (only sound is heard/ammo is seen).
Open any wad, it can be an iwad, in single player mode. Start a map, spectate, then use "nextmap" to switch to next map. When next map is loaded, join.
I am unsure if this has been reported yet, as I've seen something familiar like this but not exactly as I've experienced it.
No tags attached.
Issue History
2010-11-08 15:27AnonymousNew Issue
2010-11-08 17:45user35Note Added: 0000581
2010-11-08 19:35Torr SamahoNote Added: 0000582
2010-11-08 19:36Torr SamahoStatusnew => feedback
2010-11-12 18:38user35Note Deleted: 0000581
2012-03-29 15:28unknownnaNote Added: 0003004
2012-03-29 15:36unknownnaNote Edited: 0003004bug_revision_view_page.php?bugnote_id=3004#r1550
2012-03-29 15:37unknownnaNote Edited: 0003004bug_revision_view_page.php?bugnote_id=3004#r1551
2012-06-09 13:22Torr SamahoCategoryGeneral => Bug
2016-04-18 01:59Ru5tK1ngNote Added: 0014731
2016-04-18 01:59Ru5tK1ngStatusfeedback => resolved
2016-04-18 01:59Ru5tK1ngResolutionopen => fixed
2018-09-30 22:36Blzut3Statusresolved => closed

Notes
(0000582)
Torr Samaho   
2010-11-08 19:35   
Has already been reported:'http://www.skulltag.com/forum/viewtopic.php?f=33&t=20390 [^]'

Anyway, the spectator mode was never meant for true single player. The only proper way to fix this I see right now would be to simply forbid the use of nextmap / changemap in single player while the player is a spectator.
(0003004)
unknownna   
2012-03-29 15:28   
(edited on: 2012-03-29 15:37)
How about preventing players from being able to save their game if they're a spectator?

(0014731)
Ru5tK1ng   
2016-04-18 01:59   
Unable to reproduce this bug with 2.1.2. Must have been fixed eventually.