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
If you just have to write events to handle the other mods behavior, you can write new events that can only be triggered by a specific mod (by putting some of it's content in the trigger) and keep them in the main mod.
But if both mods contain the same file there is no way around a separate compatibility mod, as far as I know.
Or is it better to do a compability mod that eddits your main mod?
But the main work would be to compare all files at the same relative path for "objects" with the same name. Objects could be events, components, etc.
You would then need to compare all similar objects to their vanilla version and merge the differences into new files which you then put into a local mod that will load first, so name should be something like 000_mergedMods.
This doesn't mean it's a lot of work in general, but I've no experience handling compressed files.
The only issue I have is that it's quite hard to gather info on this when you really start from nothing. Do you think what I say above makes sense?
Thank you in advance
The Stellaris Launcher don't has that feature.