custom Colour Slot 10 always dispalys as "choose this colour to be light blue"

Bug #1777262 reported by Jai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Invalid
Undecided
AlexB

Bug Description

i Cannot seem to get my custom colour slot 10 to do as it is meant to.

here is my code:

Slot10.DisplayColor=128,64,64 ;brown

Slot10.ColorScheme=Brown ;also tried as LightBlue as it still seems to be somewhat hard coded and uses them in certain list

Slot10.Tooltip=STT:PlayerColorBrown

ra2md.csf

STT:PlayerColorBrown
"Choose this to be brown."

i have also tried

STT:PlayerColorLightBlue
"Choose this to be brown."

when i chose my brown, id DOES NOT say "missing string" error.
it says "Choose this to be ligh blue."

Please Help!

Revision history for this message
AlexB (alexander-b) wrote :

I used this line to check whether there's a problem loading uimd.ini:
Slot10.Tooltip=NOSTR:My custom color description.
This worked, and the string is shown.

Ares.csf overwrites the strings in the original ra2md.csf, and this is likely what's causing you trouble here. Can you either put the text with a new name into ra2md.csf, or put it in a string table CSF?

Revision history for this message
Jai (junior8805) wrote :

Hey mate!

Sorry for the late reply, I have been really busy.

I was not aware of the "NOSTR" string command. it worked a treat and i use it all the time now rather than editing the CSF file anymore.

A few things I tried before you got back to me were:

I found a CSF file in ares.mix and I changed the "choose this color to be light blue" to "brown", and it seemed to stop the whole of the mix file from being read. It seems as this mix file has been hashed and this changed it's hash value, therefore rendering it the "wrong" file.

This did fix the issue, but then a lot of other strings broke.

Another way i found to work:

I set "Color=10" but have "Slot11.ColorScheme=XXX" filled and this also seems to fix the issue as it now bugged slot 11, but as i only had a count of 10 it didn't matter.

Thank you for your speedy response and keep up the great work.

Really loving Ares!

Junior

Revision history for this message
Jai (junior8805) wrote :

Sorry to bug you,

2 more things.

Is there any drawback for using "NOSTR:XXXX" on everything?

and is there ANYTHING i can help you with, on Ares? I would like to help, if possible for such a great cause.

Revision history for this message
AlexB (alexander-b) wrote :

Hey, and thank you! :)
To help, it's usually enough to use the latest unstable testing build and report issues with it. There's usually a pinned thread on PPM (https://ppmforums.com/index.php?f=875) about the latest development.

Drawbacks using NOSTR: is that you lose the ability for localization. INIs have 8 bit wide chars, CSFs use 16 bit wide chars. Also, a NOSTR: string cannot by design be longer than 31 chars, including the NOSTR: part, thus only 25 usable characters.

You could use a stringtable file. It would only contain your strings, it would override Ares.csf, and would support more characters and text lengths greater than 25.

I guess what happened while you edited the Ares.csf file was that the language setting was changed. Ares.csf should be language neutral to work with every language version. In the documentation I explained how you can change that setting manually using a hex editor (ares-developers.github.io/Ares-docs/new/misc/stringtableenhancements.html).

Though, I'm not sure I understand correctly. How is slot 11 now bugged?

Revision history for this message
Jai (junior8805) wrote :

Hey mate,

Thanks for the information!

So as I said before, if I make 11 colours and then set the count to 11, the 10th colour (brown) shows up as brown and 11 bugs out, so i set count to 10 and 10 still works while still having 11 in the list. Removing 11 from the list makes 10 bugged. It appears after 9 or 10 the last one seems to bug out, so I simply added more than needed and cut the list 1 short.

I will look into how to make use of a stringtable file tomorrow.

As for hex editing, i didnt think of that, brilliant!

Revision history for this message
AlexB (alexander-b) wrote :

I'm not sure what's going on. I used
    Count=10
    Slot10.DisplayColor=128,64,64
    Slot10.ColorScheme=Yellow
    Slot10.Tooltip=NOSTR:Dark brown test.
and all settings have the desired effect.

Do you have a color scheme called "Brown"? If not, I would expect a fallback to neutral grey-ish color in-game. Which Ares version are you using?

Revision history for this message
Jai (junior8805) wrote :

Sorry for the delay.

I forgot to mention, this was before i knew about the "NOSTR:" command. "NOSTR:" fixed it perfectly.

Thanks!

Revision history for this message
Jai (junior8805) wrote :

The colour was brown, always was, it was jus tthe tooltip. It is also version 1.0

Revision history for this message
AlexB (alexander-b) wrote :

Okay, then I'll close this.

Changed in ares:
assignee: nobody → AlexB (alexander-b)
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.