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