This is about the "Tint By Race" button option...again. I know exporting and externally tinting everything is an option in theory, but in practice it's a huge waste of time, especially if you might want to change the exact color later.
I've also found this thread, but the directions given don't seem to work for me. I've tried both the given UI editor and importing(+editing Game UI Data).
My actual goal is to add colors, not replace them, so there shouldn't be any errors with the "val=locked" statement in StandardConstants. Notably the UI editor approach does work for the minimap buttons by adding a layout file with just the constant definition (and standard wrappers):
<Constant name="ColorMinimapButtonIcon_RaceID" val="RGB color code"/>
With RaceID and RGB color code set to match the custom race and desired color, respectively. Doing the same with (what I hope is) the button color doesn't work (trying to override using a stock RaceID doesn't work either):
<Constant name="ColorGroupSelectionBorderNormal_RaceID" val="RGB"/> (for group selection boxes, which are also messed up)
I've copied every constant with a race identifier the UI editor search would spit out, so I'm confident I didn't just miss the right one. I definitely have all those listed in the linked thread. So, what is going on here? Do I need to set a fake filepath for these constants or something? Did Blizzard break this since the time the previous thread was solved?
I've tested how much we can alter to create a new race now, too.
In editor tests, the texts, styles and UI stuff are working. here
But the much bigger problem is: You can't select your added race in the bnet lobby (and hardcoding the selection of the new race doesn't work)...
(Selecting "Random" however has a chance to use your new race...)
-> It's not possible to properly add new races to the game.
This is about the "Tint By Race" button option...again. I know exporting and externally tinting everything is an option in theory, but in practice it's a huge waste of time, especially if you might want to change the exact color later.
I've also found this thread, but the directions given don't seem to work for me. I've tried both the given UI editor and importing(+editing Game UI Data).
My actual goal is to add colors, not replace them, so there shouldn't be any errors with the "val=locked" statement in StandardConstants. Notably the UI editor approach does work for the minimap buttons by adding a layout file with just the constant definition (and standard wrappers):
With RaceID and RGB color code set to match the custom race and desired color, respectively. Doing the same with (what I hope is) the button color doesn't work (trying to override using a stock RaceID doesn't work either):
I've copied every constant with a race identifier the UI editor search would spit out, so I'm confident I didn't just miss the right one. I definitely have all those listed in the linked thread. So, what is going on here? Do I need to set a fake filepath for these constants or something? Did Blizzard break this since the time the previous thread was solved?
Yes my old solution has long stopped working and I haven't been able to find any other, must be Blizz's fault. Help anyone?
I've tested how much we can alter to create a new race now, too.
In editor tests, the texts, styles and UI stuff are working. here
But the much bigger problem is: You can't select your added race in the bnet lobby (and hardcoding the selection of the new race doesn't work)...
(Selecting "Random" however has a chance to use your new race...)
-> It's not possible to properly add new races to the game.
edit:
I've made a post about this in Blizz's forums.
Also, it's not possible to add a new tech tree, it seems.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumi know this is a old thread and i don't know if any one is interested but i have manged to add a custom tech tree to the help panel
http://www.sc2mapster.com/forums/development/triggers/69256-dynamically-change-race-of-button-solved/