Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
"menuTag":"damsel", // name of category/title in build menu
"menuButton":"livestock", // which build menu to appear under
These are assigned on the objects themselves which ensures all the mods play nicely with each other.
However, for what you're creating, which sounds like more of a UI total conversion I think it's safe to edit the variable in gui.data. If you create a file with the following in:
Here the order that the categories appear under each subheading ("tanks", "equipment", "staffObjects", "livestock", "scenery" and "facilities") determines the order they appear in the menu.
You can add as many categories to these lists as you like. Thankfully, if no objects of a category are detected in the game, it will be omitted.
Warning: If two mods try to overwrite the gui.data variables though, the one higher in the list will take priority. This is why you should only use this for a global UI mods and not for individual animal mods.
You should add a note declaring this in the notes on the workshop, so players know to only install one UI mod at a time (there may only be one at the moment, but there may be more in the future).
Hope that makes sense. :)