Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
For certain big mods, there are also compatibility patches/merges, but their quality also varies.
At the end of the day, the important variable is you as the person using the mods. If you understand how the game structure works, you should understand what mods will likely work with each other, and can solve a lot of issues yourself. And also see what mods are going to be causing trouble with other mods simply by what they do. If you don't, then creating a heavily modded game is always going to be hit-or-miss.
I've discovered that you can copy the installation folder to a new directory, and it will only draw on the local folders for game information (though saves and custom empire data will be stored in a pooled space).
So I've got a "Stellaris Mods" folder with a few different subfolders, each containing a different modded copy of the game. To make that work with other people's mods, you'd probably want to subscribe with your "central install" then migrate the definition files associated with the mod into the sub-install you want to tie it to.