Инсталирайте 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)
Украински (Українська)
Докладване на проблем с превода
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