0004227: Allow users to override some properties (e.g. colours, opacity) on new scoreboard

Notes
(0023603) Kaminsky (developer) 2024-04-13 14:30 edited on: 2024-04-13 14:31	You can control the row background colours and opacity via SCORINFO:'https://wiki.zandronum.com/SCORINFO [^]' (a non-protected lump, so you may also save it in your skins folder). In a scoreboard block, use the "LightRowBackgroundColor", "DarkRowBackgroundColor", "LocalRowBackgroundColor", and "RowBackgroundAmount" properties to change their appearances. Also for reference, these are the values used in zandronum.pk3: LightRowBackgroundColor = "40 40 40" DarkRowBackgroundColor = "20 20 20" LocalRowBackgroundColor = "80 80 80" RowBackgroundAmount = 0.65

(0023607) unknownna (updater) 2024-04-14 17:01	Ok, I was trying to get the scoreboard background to look less busy and more like the example requested by the user in the other ticket:'https://zandronum.com/tracker/view.php?id=4011 [^]' I want "LightRowBackgroundColor" and "DarkRowBackgroundColor" to have the same color and opacity as "BackgroundAmount". It seems that lowering them to "10 10 10" gets them in the ballpark, but I can't seem to quite match the general background, as the rows still seem to have some color to them. Then I noticed that I had to set "GapBetweenRows" to 0 to completely get rid of the lines after lowering "LightRowBackgroundColor" and "DarkRowBackgroundColor" to a level that almost matches "BackgroundAmount". And then I noticed dead players' rows were still highlighted, which I don't want. Changing "DeadPlayerRowBackgroundAmount" to 0.5 seemed to fix it to match the regular background color. Setting "RowBackgroundAmount" to 0 fixes the contrast lines when "GapBetweenRows" is the standard value of 2, but then my own player isn't highlighted anymore. Still, I find it overkill to expect simple users to create a mod to alter the scoreboard visuals a little. I had to check back and forth numerous times to try to match the colors for instance. The names aren't as intuitive as expected either, I didn't expect "RowColor" to change only the text color as an example. "RowTextColor" would be better understood by simple users like me. Anyway, I still appreciate and applaud your work however.

(0023608) Kaminsky (developer) 2024-04-14 17:33	Right, I neglected to mention that there's separate properties that control the opacity of the text and background of the row for dead players. Maybe I'll also need to add a new flag that only draws the local player's row background since I think that's what you're looking for. I want to avoid adding (and then having to maintain) hard-coded CVars to control stuff on the scoreboard that's already modifiable with the SCORINFO lump. However, if modifying just a few minor things (e.g. background colour and opacity) with the lump is too cumbersome for the majority of users, then maybe I'll re-consider this. I'll also see what I can do about renaming properties like "RowColor" to "RowTextColor" to make their function more clear. Thanks for the feedback.

(0023815) unknownna (updater) 2024-07-25 19:50	I noticed you updated some of these things, nice work. I got some additional feedback if you don't mind: * I'd like ONLYSHOWLOCALROWBACKGROUND as a CVar. It would be an option to toggle in the scoreboard menu, e.g. "contrast rows" on/off. I believe it would be appreciated for users with less-than-perfect vision to make the scoreboard look less busy. * I'd want a slider to control the opacity of the background, i.e. BackgroundAmount. * Maybe some users would want to change the color of the background, i.e. BackgroundColor. * I'd also maybe want USETEAMTEXTCOLOR as a CVar, "team text colors", for users who'd wish to emulate the older look of Zandronum/Skulltag. * I'd maybe want an option to toggle between borders on/off, since you can use "BackgroundAmount = 0" and "AddFlag USETEAMTEXTCOLOR" to almost match the look of old Zandronum/Skulltag if you want to. * I'd also recommend to maybe rename the USETEAMTEXTCOLOR flag to USETEAMTEXTCOLORS, since there are multiple teams with different colors. * Maybe rename the "# Player" header to "# Players" on the scoreboard. It would maybe feel more intuitive as a plural next to "frags", "points", "wins" etc. But if it's intended the way it currently is, it's ok. * Maybe some CVars to change the font of the various texts, like the HeaderFont. At minimum I'd expect something like ONLYSHOWLOCALROWBACKGROUND as a CVar and a slider to control BackgroundAmount, if nothing else. It's not so fun to have to copy a skin folder with a wad for the scoreboard for every future instance of Zandronum past 3.2 installed on my PC. I believe other ports like ZDaemon has options for these things. Minor bugs: * When you use "AddFlag UseTeamTextColor", "LocalRowTextColor" is cancelled in coop/survival modes. * When you use "AddFlag DontDrawBorders", there are still some team-colored borders drawn in team modes.

(0023818) Kaminsky (developer) 2024-07-26 04:09 edited on: 2024-07-26 04:10	FYI, I was already working on adding CVars to override a few properties on the scoreboard (it's not ready yet). I already considered adding CVar overrides to these properties: - Text colours - Border colours - Scoreboard background colour and opacity - Row background colour and opacity - The DONTUSELOCALROWBACKGROUNDCOLOR and ONLYSHOWLOCALROWBACKGROUND flags Note: I thought about adding a "cl_overridescorinfoflags" flagset CVar, so users can choose certain properties that they want to override, instead of all or none. I didn't think about adding a CVar to override USETEAMTEXTCOLOR, but I wouldn't have anything against it. I don't think it's necessary to handle every single property, so I probably wouldn't consider adding overrides for the fonts. I'd prefer focusing on the few properties that people are more likely to override. Quote from "unknownna" I'd also recommend to maybe rename the USETEAMTEXTCOLOR flag to USETEAMTEXTCOLORS, since there are multiple teams with different colors. This sounds reasonable. Quote from "unknownna" Maybe rename the "# Player" header to "# Players" on the scoreboard. It would maybe feel more intuitive as a plural next to "frags", "points", "wins" etc. But if it's intended the way it currently is, it's ok. I'm not sure about pluralizing the "Player" header. Most scoreboards that I've seen in other games that have such a header don't pluralize it either. It somewhat makes sense: while players can have multiple frags, kills, points, wins, etc., they can only have one name. Quote from "unknownna" When you use "AddFlag DontDrawBorders", there are still some team-colored borders drawn in team modes. This is tricky because I never considered the lines that appear in the team/spectator headers to be part of the borders that surround the column headers and player rows. The team headers are margins that are handled differently in SCORINFO. Thanks for the valuable feedback either way!

(0024090) Kaminsky (developer) 2024-10-24 15:51 edited on: 2024-10-24 15:57	These commits add CVars that allow users to override a few properties/flags on the scoreboard, including text colours, border colours, background colour/opacity, and row backgrounds: -'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/8f6f4f5bbb8ab0f36b1da83531972ca1e7e104b4 [^]' -'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/32165b32cc8f1d984d324eacf77f51e6c4be1661 [^]' A full list of options can be found in the "customize scoreboard" sub-menu found in the scoreboard options menu. This should cover almost all of the properties that users might be interested in modifying for themselves. The USETEAMTEXTCOLOR flag has also been renamed to USETEAMTEXTCOLORS and fixed to not override text colours in non-team game modes:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/85bede33999ab37b050336d2f984c86b462a9b1f [^]' I updated the title of this ticket to something more appropriate, since this is now about adding options to modify various parts of the scoreboard instead of just the row background colours.

(0024105) unknownna (updater) 2024-10-26 07:37	Thank you very much for adding these features and also adding them to a separate menu, much appreciated! So I assume there won't be a way to remove the borders for fun if you want to emulate the Skulltag visuals, since they are part of the script. There seems to be some confusion with the header text colors, sb_useheadertextcolorforborders. Even with it off, the borders still use the header text (sb_headertextcolor) as color. After testing some more, this seems to happen because "sb_customizebordercolors 0" for some reason turns it on. And the "customize row" stuff doesn't really work in team modes, but maybe it's not too important there.

(0024134) Kaminsky (developer) 2024-11-10 23:26	Quote from "unknownna" So I assume there won't be a way to remove the borders for fun if you want to emulate the Skulltag visuals, since they are part of the script. Good idea. I figured that other users might been interested in disabling borders on their scoreboard too, so I added the CVar, "sb_noborders", to make it possible:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/2b3de5da73efb192ef2fcc2f28c06996a440fc33 [^]' Quote from "unknownna" There seems to be some confusion with the header text colors, sb_useheadertextcolorforborders. Even with it off, the borders still use the header text (sb_headertextcolor) as color. After testing some more, this seems to happen because "sb_customizebordercolors 0" for some reason turns it on. This is because by default, the scoreboard has the USEHEADERTEXTCOLORFORBORDERS flag enabled (which is also why the default value of "sb_useheadertextcolorforborders" is true), whether "sb_headertextcolor" or the SCORINFO property are used. If "sb_customizeborders" is disabled, then the borders will still use the same colour as the header text unless that flag is disabled. This is how it should work. Quote from "unknownna" And the "customize row" stuff doesn't really work in team modes, but maybe it's not too important there. I'm assuming that you're referring to the row background colours, right? In team-based game modes, the background of each player row appears in the same colour as their team's, but the row background colour properties/CVars are still blended in. You'll probably notice some differences in shading if you keep playing around with the colours.

(0024152) unknownna (updater) 2024-11-17 09:09	Quote from Kaminsky If "sb_customizeborders" is disabled, then the borders will still use the same colour as the header text unless that flag is disabled. So you have to enable "sb_customizetext" first, then enable "sb_customizeborders", and then finally disable "sb_useheadertextcolorforborders". * "use header text color" doesn't work if "customize text" is disabled, though it's maybe intended and not significant since users would probably enable custom text colors before altering the borders. * "no borders" still has some hard-coded borders in team modes, probably due to the script in SCORINFO. * Regarding the hard-coded borders in team modes, would it be good for them to also be affected by "sb_useheadertextcolorforborders", or do you think it would look bad? * Could we perhaps have a "header font" option? I think it would look cool using BIGFONT for them sometimes, and I believe Skulltag used this. Quote from Kaminsky I'm assuming that you're referring to the row background colours, right? In team-based game modes, the background of each player row appears in the same colour as their team's, but the row background colour properties/CVars are still blended in. You'll probably notice some differences in shading if you keep playing around with the colours. Exactly, and after testing some more, it seems to alter the shading a little indeed, so I was wrong.

(0024162) unknownna (updater) 2024-11-27 06:47	I saw you went ahead and fixed the border issue and added the font option feature, much appreciated, it looks really cool and fun! I hate to nitpick and feel like I'm overstaying my welcome with these suggestions by now, but would it be possible to make it so it would cycle through the fonts with the arrow keys instead of having to type them manually? I don't think many of regular users know what the other fonts are named.

(0024180) Kaminsky (developer) 2024-12-15 21:59	I'd think that allowing users to type the name of the desired font would offer the most versatility, instead of cycling through only three fonts ("SmallFont", "BigFont", and "ConFont"). A user might even want to use a different font than those three. If anything, we could mention these three fonts on a wiki page specifically for the scoreboard options.

(0024186) unknownna (updater) 2024-12-22 14:18	Ok, I see. I thought it would identify all loaded fonts automatically and allow you to cycle through them. But if it's too much of a hassle to implement something like that, a wiki page mention of the fonts would be nice and acceptable indeed.

(0024235) Kaminsky (developer) 2025-03-06 03:11 edited on: 2025-03-06 03:12	Quote from unknownna I thought it would identify all loaded fonts automatically and allow you to cycle through them. I'm afraid that automatically listing all loaded fonts will also list incompatible fonts (e.g. those that don't have alphabetical characters like the ones used in the status bar, or those intended purely for graphical purposes), which isn't desirable. If manually typing the name of the font is too cumbersome, and there's a huge demand to generate a list of loaded fonts to cycle from, it can be re-considered in the future. Other than that, is there anything else that needs to be addressed in this ticket before marking it as resolved?

(0024239) unknownna (updater) 2025-03-06 18:04	I see. It's sufficient as is for someone like me, but I was simply thinking of making it as easy as possible for younger, less tech-savvy users that discover Zandronum in the future. I believe 1 or 2 of the other ports allow you to cycle through various fonts for the scoreboard IIRC. Could you omit the incompatible fonts? Anyway, I get the impression it's not easy to change it up further, so marking as resolved. Thank you for all of the changes so far, appreciate it.

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
2024-04-13 13:13	unknownna	New Issue
2024-04-13 13:13	unknownna	File Added: Screenshot_Doom_20240413_145825.png
2024-04-13 14:30	Kaminsky	Note Added: 0023603
2024-04-13 14:31	Kaminsky	Note Edited: 0023603	View Revisions
2024-04-14 17:01	unknownna	Note Added: 0023607
2024-04-14 17:05	unknownna	File Added: Screenshot_Doom_20240414_184953.png
2024-04-14 17:33	Kaminsky	Note Added: 0023608
2024-07-25 19:50	unknownna	Note Added: 0023815
2024-07-25 19:50	unknownna	Status	new => feedback
2024-07-26 04:09	Kaminsky	Note Added: 0023818
2024-07-26 04:10	Kaminsky	Note Edited: 0023818	View Revisions
2024-10-24 15:51	Kaminsky	Note Added: 0024090
2024-10-24 15:51	Kaminsky	Assigned To	=> Kaminsky
2024-10-24 15:51	Kaminsky	Status	feedback => needs testing
2024-10-24 15:51	Kaminsky	Target Version	=> 3.2
2024-10-24 15:51	Kaminsky	Summary	Allow users to decide whether to use alternate contrast lines on new scoreboard => Allow users to override some properties (e.g. colours, opacity) on new scoreboard
2024-10-24 15:51	Kaminsky	Note Edited: 0024090	View Revisions
2024-10-24 15:57	Kaminsky	Note Edited: 0024090	View Revisions
2024-10-26 07:37	unknownna	Note Added: 0024105
2024-10-26 07:37	unknownna	Status	needs testing => feedback
2024-11-10 23:26	Kaminsky	Note Added: 0024134
2024-11-10 23:27	Kaminsky	Status	feedback => needs testing
2024-11-17 09:09	unknownna	Note Added: 0024152
2024-11-17 09:10	unknownna	Status	needs testing => feedback
2024-11-27 06:47	unknownna	Note Added: 0024162
2024-11-27 06:47	unknownna	Status	feedback => assigned
2024-12-15 21:59	Kaminsky	Note Added: 0024180
2024-12-22 14:18	unknownna	Note Added: 0024186
2025-03-06 03:11	Kaminsky	Note Added: 0024235
2025-03-06 03:12	Kaminsky	Note Edited: 0024235	View Revisions
2025-03-06 18:04	unknownna	Note Added: 0024239
2025-03-06 18:04	unknownna	Status	assigned => resolved
2025-03-06 18:04	unknownna	Fixed in Version	=> 3.2
2025-03-06 18:04	unknownna	Resolution	open => fixed

Relationships