MantisBT - Zandronum
View Issue Details
0004434Zandronum[All Projects] Bugpublic2024-10-28 10:122025-01-30 13:44
pkmx 
Kaminsky 
normalmajoralways
resolvedfixed 
x86_64Arch Linux
 
3.23.2 
0004434: sv_randomcoopstarts and compat_oldrandom breaks player spawning
In the latest alpha r241027-2139, when the server enables both sv_randomcoopstarts and compat_oldrandom, the player sometimes get spawned into void.
$ zandronum -iwad DOOM2.WAD +sv_randomcoopstarts 1 +compat_oldrandom 1 -host
$ zandronum -iwad DOOM2.WAD -connect 127.0.0.1:10666
No tags attached.
Issue History
2024-10-28 10:12pkmxNew Issue
2024-10-28 22:17pkmxNote Added: 0024107
2024-10-29 00:02DrinkyBirdNote Added: 0024108
2024-10-29 00:02DrinkyBirdStatusnew => confirmed
2024-10-29 00:03DrinkyBirdNote Edited: 0024108bug_revision_view_page.php?bugnote_id=24108#r14422
2024-10-29 17:38DrinkyBirdNote Added: 0024111
2024-10-29 17:38DrinkyBirdAssigned To => Kaminsky
2024-10-29 17:38DrinkyBirdStatusconfirmed => needs review
2024-11-03 23:11DrinkyBirdStatusneeds review => needs testing
2024-11-03 23:11DrinkyBirdTarget Version => 3.2
2025-01-30 13:44KaminskyNote Added: 0024209
2025-01-30 13:44KaminskyStatusneeds testing => resolved
2025-01-30 13:44KaminskyFixed in Version => 3.2
2025-01-30 13:44KaminskyResolutionopen => fixed

Notes
(0024107)
pkmx   
2024-10-28 22:17   
On TSPG's BYOC servers we have been getting some rare reports where people get spawned into the void, even though both of those settings are disabled. It seems like there is something else that could be triggering this bug.
(0024108)
DrinkyBird   
2024-10-29 00:02   
(edited on: 2024-10-29 00:03)
Yep it's unrelated to those settings, we encountered it testing JumpMaze earlier.
Seems to only affect player IDs above 0.
Only affects certain maps, in JM all/most LJM maps are affected, but I'm not sure what the common factor is.

(0024111)
DrinkyBird   
2024-10-29 17:38   
Kaminsky submitted an MR for this:'https://foss.heptapod.net/zandronum/zandronum-stable/-/merge_requests/226 [^]'
(0024209)
Kaminsky   
2025-01-30 13:44   
It's been a few months and I haven't seen any more reports of this bug still happening, so I'll mark this as resolved now.