Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
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