Anonymous | Login | Signup for a new account | 2025-06-13 21:46 UTC | ![]() |
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0004508 | Zandronum | [All Projects] Bug | public | 2025-04-18 16:44 | 2025-04-20 17:30 | ||||
Reporter | unknownna | ||||||||
Assigned To | Kaminsky | ||||||||
Priority | normal | Severity | text | Reproducibility | always | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 3.1 | ||||||||
Target Version | Fixed in Version | 3.2 | |||||||
Summary | 0004508: "Draw Game!" string with "sv_suddendeath 0" uses inconsistent red or green colors across modes | ||||||||
Description | This was just something I noticed while testing some recent fixes. For some reason this string uses different coloring depending on which mode you play on. It would be better if it was unified with consistent coloring across all modes that support it. Confirmed modes with green coloring: * DM * Terminator Confirmed modes with red coloring: * TeamDM * CTF * OneFlagCTF * Skulltag * Domination | ||||||||
Steps To Reproduce | Example with green coloring: 1. zandronum -host -file countdown_deathcount_02.wad +timelimit 0.1 +sv_suddendeath 0 +deathmatch 1 +sv_maprotation 1 +addmap map01 2. Connect a client to the server to let the timelimit run out. The green string will appear. Example with red coloring: 1. zandronum -host -file countdown_deathcount_02.wad +timelimit 0.1 +sv_suddendeath 0 +teamplay 1 +sv_maprotation 1 +addmap map01 2. Connect a client to the server and join the game. You have to join the game for TeamDM, otherwise blue team wins due to some hard-coded issue. The red string will appear. | ||||||||
Attached Files | ![]() | ||||||||
![]() |
||||||
|
![]() |
|
Kaminsky (developer) 2025-04-19 11:12 |
'https://foss.heptapod.net/zandronum/zandronum-stable/-/merge_requests/315 [^]' |
unknownna (updater) 2025-04-19 22:24 edited on: 2025-04-19 23:00 |
Thanks, this fixed the issue, but it revealed some discrepancy between 3.1 and 3.2: Right before the intermission screen kicks in, the win sequence message repeats briefly with a flash before entering the intermission screen. This does not happen in 3.1. What gives? The message duration also differs between the two. I think the longer duration in 3.2 looks better, but the flash is different and maybe distracting. Players also are force-respawned during this flash in some modes like CTF, though the force-respawn also happens in 3.1. |
Kaminsky (developer) 2025-04-20 16:25 |
Quote from unknownna This topic should fix this issue:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commits/topic/default/level-timer-regression-fix [^]' Let me know if it works for you too, and that there's no other side effects. Quote from unknownna Didn't these kinds of messages always had a five second duration (i.e. fully opaque for three seconds, then fading out for two seconds)? At least, I can't seem to notice a difference in the message duration between 3.1 and 3.2 when I wait for the timer to expire and see the message pop up. |
unknownna (updater) 2025-04-20 17:30 |
Quote from Kaminsky Maybe, but if you start a game with the following: zandronum -host -file countdown_deathcount_02.wad +timelimit 0.1 +sv_suddendeath 0 +teamplay 1 +sv_maprotation 1 +addmap map01 +map map01 and then connect a client and join a team before the timelimit runs out, the "draw game" string fades back much faster in 3.1 compared to 3.2. I think it's a separate bug in 3.1 that got fixed in 3.2 somehow. On a side note, the string handling just seems to be broken in 3.1 or something, as I managed to get an all-gray message by using the following command and joining the game before the timelimit runs out: zandronum -file countdown_deathcount_02.wad +timelimit 0.1 +sv_suddendeath 0 +teamplay 1 +sv_maprotation 1 +addmap map01 +map map01 Quote from Kaminsky I went through most modes with 2 clients, one using a local connection and one using a ping of 160. Most things worked fine, but I found some issue in CTF. It's actually a regression from the recent "multi-team tie" message fixes. I'll make a separate report for it ASAP. * DM: OK * TeamDM: OK * Duel: OK * Terminator: OK * LMS: OK * TeamLMS: OK * Possession: OK * TeamPossession: OK * CTF: OK, but the final score message only displays the sub-text now * OneFlagCTF: OK * Skulltag: OK * Domination: OK * TeamGame: OK Since your fix took care of the issue here, I'll mark this as resolved. Thank you very much! I made a note of the auto-spawn behavior and will maybe make a separate report for it some other later time. |
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why. |
|
Supporters: | No one explicitly supports this issue yet. |
Opponents: | No one explicitly opposes this issue yet. |
![]() |
|||
Date Modified | Username | Field | Change |
2025-04-18 16:44 | unknownna | New Issue | |
2025-04-18 16:44 | unknownna | File Added: Screenshot_Doom_20250418_182645.png | |
2025-04-19 11:12 | Kaminsky | Note Added: 0024482 | |
2025-04-19 11:12 | Kaminsky | Assigned To | => Kaminsky |
2025-04-19 11:12 | Kaminsky | Status | new => needs review |
2025-04-19 22:24 | unknownna | Note Added: 0024483 | |
2025-04-19 22:24 | unknownna | Status | needs review => feedback |
2025-04-19 22:26 | unknownna | Note Edited: 0024483 | View Revisions |
2025-04-19 22:33 | unknownna | Relationship added | related to 0001092 |
2025-04-19 23:00 | unknownna | Note Edited: 0024483 | View Revisions |
2025-04-20 16:25 | Kaminsky | Note Added: 0024485 | |
2025-04-20 17:30 | unknownna | Note Added: 0024486 | |
2025-04-20 17:30 | unknownna | Status | feedback => assigned |
2025-04-20 17:30 | unknownna | Status | assigned => resolved |
2025-04-20 17:30 | unknownna | Fixed in Version | => 3.2 |
2025-04-20 17:30 | unknownna | Resolution | open => fixed |
Copyright © 2000 - 2025 MantisBT Team |