0000404: Death on Scorboard For Online

Notes
(0008994) Watermelon (developer) 2014-06-10 15:52	I would like to make my own custom scoreboard to replace the old one. I did this with the CTF stuff, but a more extended option would be nice. I dont know if Dusk was working on this or not

(0022849) Kaminsky (developer) 2023-06-19 15:36	The deaths column now appears in online games on the revamped scoreboard, as explained here:'https://zandronum.com/tracker/view.php?id=1829#c22848 [^]'

(0023741) unknownna (updater) 2024-06-01 03:30 edited on: 2024-06-01 03:47	It appears now, but it resets in every round in LMS and TLMS for some reason, and duel, though it's probably intentional in duel.

(0023849) Kaminsky (developer) 2024-07-29 15:15	Right now, it's intentional for a player's time and death counters to reset at the start of a new round (I discussed this with Torr a while ago, and he suggested that map resets should reset everything including these). While this makes sense for cooperative-based game modes and duel where indeed everything is supposed to reset, it does seem weird to reset deaths in (T)LMS where players are supposed to keep their frags and wins between rounds.

(0024377) Kaminsky (developer) 2025-04-02 15:32	FYI, I pushed this new topic to the repository:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commits/topic/default/tlms-player-death-count [^]' With this topic, a player's death count shouldn't reset in (T)LMS at the start of a new round anymore. It still resets outside of these two game modes, though, since a map reset still constitutes as a full reset (e.g. survival). Note that their death count still increases during countdown sequences. I don't know for sure what should be the desired behaviour here, since players don't earn frags during countdown sequences.

(0024378) unknownna (updater) 2025-04-02 21:15 edited on: 2025-04-02 21:18	Thanks for this. Quote from Kaminsky I don't know for sure what should be the desired behaviour here, since players don't earn frags during countdown sequences. I tested it, and I think it would perhaps be a better idea to freeze the death counter during countdowns, as to not confuse players when looking at the score. Each player death (non-suicide ones etc.) should ideally correspond with another player frag, so it would be better if it only kept counting deaths (like frags) during actual live rounds. At least that's my impression from testing it. By the way, any updates to letting true spectators keep their wins in duel before the final release of 3.2? It would make the wins counter actually work for once.

(0024379) unknownna (updater) 2025-04-03 11:16	I saw you added the functionality for allowing true spectators to retain their wins in duel, nice work. However, nobody can actually observe how many wins they have on the scoreboard and during the intermission screen since their counters (like their frag and death counters) are hidden.

(0024381) Kaminsky (developer) 2025-04-05 02:07 edited on: 2025-04-05 02:50	Quote from unknownna However, nobody can actually observe how many wins they have on the scoreboard and during the intermission screen since their counters (like their frag and death counters) are hidden. The wins column, among many others, is not something that should show a true spectator's values, even if we want to allow them to keep their win count in duel. It's also not easy to make a column show a true spectator's values in one specific game mode only, but hide them in all others. From briefly testing the wins column to show the values of true spectators, I found it to look extremely "off" too, especially when many other columns are still hidden for them, and I personally don't like it. I think it's good enough if everyone can now keep their win counts when they join spectators, but only show it for those in the game (this is also now getting off topic from the original issue of this ticket).

(0024384) unknownna (updater) 2025-04-05 17:45 edited on: 2025-04-05 17:48	Interesting, I see. I’m sorry to hear it didn’t look right to you. With the current behavior, a spectator with the most wins that didn’t win/lose the final duel will not be displayed as having any wins at all, which is a bit sad from the spectator’s perspective. Would it be better if it only displayed a win counter for any spectator that has earned at least one win? That way, you wouldn’t have a bunch of "0" win spectators lined up, if that’s what looked wrong. One could additionally sort true spectators by win count, where specators with wins and most wins are placed highest above the others. I understand it’s a bit late for this, but I still think it would be worth looking into further sometime.

(0024387) Kaminsky (developer) 2025-04-07 21:59	I think for now, the best course of action is to keep the current behaviour (i.e. players lose their win count upon joining spectators) and then address this properly after 3.2's release. I don't think it's urgent to change this right now. Since this ticket pertains to the deaths column, and these two commits:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/1293f0b4260ec334b12f66a8879a1ce307a35712 [^]' and'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/ca98f858de27f0a35e23dcd0a364a7001fcc9ee6 [^]' are pushed in now, is there anything else that needs to be addressed or can this ticket be marked as resolved?

(0024390) unknownna (updater) 2025-04-08 04:27	I see, I'd at least let spectators keep wins silently even if they're not displayed, so other observers get an idea how of many games they played. But that's just my opinion, if you insist on the other way however. I'll go ahead and make a separate ticket for the spectator duel win issue so it's not lost in unrelated tickets. We can mark this one as resolved indeed.

This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	Armitage
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2011-04-25 01:58	Frank	New Issue
2014-06-10 15:52	Watermelon	Note Added: 0008994
2014-06-10 15:52	Watermelon	Status	new => acknowledged
2014-06-11 01:55	Watermelon	Relationship added	related to 0001829
2023-06-19 15:36	Kaminsky	Note Added: 0022849
2023-06-19 15:36	Kaminsky	Status	acknowledged => needs testing
2024-06-01 03:30	unknownna	Note Added: 0023741
2024-06-01 03:30	unknownna	Status	needs testing => feedback
2024-06-01 03:47	unknownna	Note Edited: 0023741	View Revisions
2024-07-29 15:15	Kaminsky	Note Added: 0023849
2025-04-02 15:32	Kaminsky	Note Added: 0024377
2025-04-02 21:15	unknownna	Note Added: 0024378
2025-04-02 21:18	unknownna	Note Edited: 0024378	View Revisions
2025-04-03 11:16	unknownna	Note Added: 0024379
2025-04-05 02:07	Kaminsky	Note Added: 0024381
2025-04-05 02:50	Kaminsky	Note Edited: 0024381	View Revisions
2025-04-05 17:45	unknownna	Note Added: 0024384
2025-04-05 17:48	unknownna	Note Edited: 0024384	View Revisions
2025-04-07 21:59	Kaminsky	Note Added: 0024387
2025-04-07 21:59	Kaminsky	Assigned To	=> Kaminsky
2025-04-07 21:59	Kaminsky	Status	feedback => needs testing
2025-04-08 04:27	unknownna	Note Added: 0024390
2025-04-08 04:27	unknownna	Status	needs testing => resolved
2025-04-08 04:27	unknownna	Fixed in Version	=> 3.2
2025-04-08 04:27	unknownna	Resolution	open => fixed