Cài đặt Steam
đăng nhập
|
ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
This seems to work fine with A17. At least, myself and another player haven't found any issues with this and my Mid-Rage Drop Pods: MF. There's no error reports in the log, either.
Great stuff! I think this method has a lot of potential for making mods more compatible with each other and I hope more modders take a look at it.
I think more modders would use it if you had an actual readme or a "how to" guide. But it was simple enough to figure out from examining the simple .XML in your Ac-Quiet Weather as an example. I assumed that the "0" referred to the first {li}{/li} set, while "1" would refer to a second {li}{/li} set, and so on.
I used it for my Mid-Range Drop Pods: MF (mod-friendly version) as I was trying to maximize mod compatibility.
I also mentioned it in this forum thread [ludeon.com].
https://ludeon.com/forums/index.php?topic=27551
related article : https://ludeon.com/forums/index.php?topic=6648.0