Notes |
|
|
* Skulltag mode is also affected by the same issue.
* None of the messages appear at all in OneFlagCTF, not even online. |
|
|
|
|
|
|
Thank you, amazing work.
* Would it be a good idea to print "x flag returned automatically." when it auto-returns? It would perhaps clear it up a bit more between player-returns and auto-returns, and be clearer when looking at the server console log.
* The server seems to crash when getting killed while carrying the white flag.
* If a "x flag dropped." message appears immediately after "x has taken the y flag.", the "held by:" portion still remains. The smaller headers remain on different messages that appear without small headers. This behavior is also present in 3.1.
Would it be good to change this behavior, or would it be too abrupt? See the attached screenshot.
I know it might sound nitpicky as usual, but I'm just letting you know my thoughts while testing it. |
|
|
|
All the points you mentioned above (especially the crash) should be addressed now. |
|
|
(0024278)
|
unknownna
|
2025-03-20 21:00
(edited on: 2025-03-20 21:41) |
|
Nice, good work on the fixes.
* The carrier name on the HUD in 1-flag-CTF seems to be missing the proper team coloring. See the attached screenshot. Super Shotgunner is on blue team, yet the name is drawn in white.
* Missing "x flag dropped." message when removing bots that carry flags.
|
|
|
|
The "x flag dropped" message not appearing in online games when a player disconnects should be fixed now. The HUD text colouring in 1-flag CTF will be handled in a separate MR. |
|
|
(0024302)
|
unknownna
|
2025-03-23 16:32
(edited on: 2025-03-23 21:09) |
|
* I tested the latest pipeline build, and the "x lost the y flag" appears twice for bots if they are removed while carrying the flag online only.
* The drop message is in reversed order for bots/players when removed/disconnected, they "leave the game" before dropping the flag. This does not happen if a player turns into a spectator or gets fragged.
It's very unrealistic scenarios, but it was just something I noticed while testing it.
Edit:
Tested the latest pipeline build, and it fixed the message order issue, but the double bot message remains. Not sure if the other fix was supposed to take care of it, but just letting you know.
Actually, it might just be some RCON double message.
|
|
|
|
I noticed you went ahead and fixed the double RCON message. Tested the pipeline build and can confirm it fixed the issue.
All of the issues here are now resolved. Great work as usual. It definitely feels more consistent and clean now compared to before. |
|