安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
I think RIMMSqol's buttons are also a little miss aligned in general.
Negligible and can be ignored completely outside of Dev mode messing with the research tree.
The research window is scroll-able both Up/Down and Left/Right but that does affect the button positions.
I am unsure why and how to go about fixing.
and advice?
And about the patch operation, it should throw a red error when the def is not found (That's why I added the OperationFindMod operation to the patch generated by the mod).
On that topic though - I would be curious what (if any) further plans are to this project. Like; having a way to set the pre-requisites ingame as well would clearly make this close to an all-in-one solution. As well as one question about the custom patchOp - without me having to look into the code (which I'm not good with in the first place) - is your custom patchOp a 'safe-patch' just checking if a researchDef exists and if not failing silently, or does the 'success always' hint a 'regular' vanilla patchOp?
@WhiteJao Kinda? If that mod overwrites the vanilla research windows, then you won't see the new buttons. But you can always disable that mod, do the changes you want, save them, and enable that mod again.
Does it work regardless of tech introduced by other mods?