[DiscordArchive] <@!325050332021522433> isnt it a core thing too?
[DiscordArchive] <@!325050332021522433> isnt it a core thing too?
Archived author: lazra • Posted: 2022-04-05T03:40:24.910000+00:00
Original source
<@!325050332021522433> isnt it a core thing too?
Archived author: AngryPenguinStudio • Posted: 2022-04-05T03:43:39.824000+00:00
Original source
yes, core is setup, tho, it maybe the format of the DBC. When i remove all of the "extra" races from the ChrRaces.dbc, the UI works fine. The problem is, it removed all the textures from the non-playables. So, for example, most people have 12 playable, but, maybe 16 in the actual core. Random example, but, it fits the question. So they would define 12 max playable, make 12 buttons, and, it all is fine. I have seen one that has 50+ in dbc, but, only 18 MAX_RACE, and, buttons set accordingly, and, works fine. I am wondering why I struggle with the dbc and the UI not allowing me to say "max_races=INT" and then making that many buttons and calling it a day. What if i had 100 playable? Cant i set to "10" in the UI and then make 10 buttons and not have it complain? For some reason, i can't.
Archived author: AngryPenguinStudio • Posted: 2022-04-05T03:46:48.915000+00:00
Original source
so the next question is .... lets say my dbc goes to 29. After 17 isnt playable, they are just the NPCs and such .... wouldnt I set MAX_RACES to 17 and make 17 buttons? Or does it have to be an even number? Say 18, or 16 ? Do the Alliance and Horde need even numbers between them? If i have 9 on Alliance, do i need 9 on horde? So many questions lol. For example, my UI has 9 on Alliance, but, its pushing 2 Alliance races on top of orc (orc being button 10) .... I dont understand where those are coming from. So its doing 9 playable Alliance with +2 non-playable. So strange.