安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
"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. :)