Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004515Zandronum[All Projects] Bugpublic2025-04-24 13:172025-04-25 20:05
Reporterunknownna 
Assigned ToKaminsky 
PrioritynormalSeveritytweakReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version3.1 
Target VersionFixed in Version3.2 
Summary0004515: Don't allow flag (team items) to auto-return automatically during win sequences in CTF
DescriptionThis is just a small thing I noticed while testing the latest fix for the final CTF score message in 0004513. I noticed the flag is able to auto-return during win sequences when the game is over. It would be better and feel a lot cleaner if this wasn't the case. When the game is over, the flag should not be affected by any player and/or world events and should remain in place where it was the moment the round ended.
Steps To Reproduce1. zandronum -host -file countdown_deathcount_02.wad +ctf 1 +timelimit 0.52 +sv_suddendeath 0 +sv_cheats 1 +sv_maprotation 1 +addmap map01
2. Connect 2 clients to the server and join a team with both so you can take a flag.
3. Take a flag with either client.
4. When the timelimit counter reaches "00:12", use the "kill" command to drop the flag. This will make the flag auto-return during the final "draw game!" message.
Additional InformationLink to example wad:'https://zandronum.com/tracker/file_download.php?file_id=3225&type=bug [^]'

This is not a regression and can safely be ignored for now.
And since the final central win message and the flag messages share the same HudMessage index, the "draw game!" string disappears at the moment the flag auto-returns.
Attached Files

- Relationships
related to 0004520resolvedKaminsky Terminator (and possession?) artifacts can auto-return during result sequences 

-  Notes
User avatar (0024505)
Kaminsky (developer)
2025-04-25 14:12

 Despite this not being a regression, this was extremely easy to fix. So, I created a new topic for it:'https://foss.heptapod.net/zandronum/zandronum-stable/-/tree/topic/default/team-item-tweaks [^]'

Note that I also fixed players from being able to pick up the white flag in 1-Flag CTF after the game's ended.

If you can thoroughly check to make sure that everything works correctly in CTF, 1-Flag CTF, and Skulltag, both offline and online, then I'll gladly open a new merge request for this. Thanks.
User avatar (0024510)
unknownna (updater)
2025-04-25 17:48

 I tested it both online and offline, and in both instances the flags and skulls can only be auto-returned during active rounds. When the result sequence kicks in, the flags and skulls remain still as expected.

For some reason though, this pipeline build seemed to automatically turn on sv_limitcommands when I hosted a server with it for the first time. I never touch this and always keep it off, so it was unexpected when I couldn't use the "kill" command so often anymore.
User avatar (0024514)
Kaminsky (developer)
2025-04-25 19:27
Quote from unknownna
For some reason though, this pipeline build seemed to automatically turn on sv_limitcommands when I hosted a server with it for the first time. I never touch this and always keep it off, so it was unexpected when I couldn't use the "kill" command so often anymore.


That's strange. The changes I made in the topic above have nothing to do, nor touch, sv_limitcommands in any way. Is there something else at play here?

In any case, it sounds like the issue(s) in this ticket are resolved now, right?
User avatar (0024515)
unknownna (updater)
2025-04-25 19:40
Quote from Kaminsky
That's strange. The changes I made in the topic above have nothing to do, nor touch, sv_limitcommands in any way. Is there something else at play here?


No idea, maybe I accidentally enabled it somehow, though I can't remember I did.

Quote from Kaminsky
In any case, it sounds like the issue(s) in this ticket are resolved now, right?


Correct. Thank you for the very fast fix again.
User avatar (0024518)
Kaminsky (developer)
2025-04-25 20:05

 Awesome! I'll go ahead and open the merge request. Thanks for testing.

Issue Community Support
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.

- Issue History
Date Modified Username Field Change
2025-04-24 13:17 unknownna New Issue
2025-04-25 14:12 Kaminsky Note Added: 0024505
2025-04-25 14:12 Kaminsky Assigned To => Kaminsky
2025-04-25 14:12 Kaminsky Status new => assigned
2025-04-25 17:48 unknownna Note Added: 0024510
2025-04-25 18:23 unknownna Relationship added related to 0004520
2025-04-25 19:27 Kaminsky Note Added: 0024514
2025-04-25 19:40 unknownna Note Added: 0024515
2025-04-25 19:40 unknownna Status assigned => resolved
2025-04-25 19:40 unknownna Fixed in Version => 3.2
2025-04-25 19:40 unknownna Resolution open => fixed
2025-04-25 20:05 Kaminsky Note Added: 0024518




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker