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
No I havent yet it's basically all on a masssive list of feedback across my mods that I'll be getting to down the line, but I have some other big YT projects happening at the moment unrelated to Stellaris which have meant I'm stalled for now. Sorry about that but I will be back to it!
I haven't coded Stellaris before but looking at the scripts I'm thinking is there any way we can change the default district_set in eg wp_nw_planet_classes_wet.txt for one of the planet sub-classes and see what happens? Maybe make a unique district_set that has eg 3 mining and 3 farming districts, apply it to a specific sub-class, and see if the new sub-class planets have those districts when we choose that sub-class as our homeworld?
Or, more promisingly, maybe we can add a script in wp_nw_scripted_effects.txt to ensure any additional planets with the same sub-class as the homeworld have the default number of mining/farming districts? I think really the solution would be in this file.
Interesting! Thanks for the looking and if you have any code advice please I'd love to hear it!