安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
but its generating removing hyperlynes and giving you those messages that its doing it.
I have like 20-50 hours in this one save game, I was not planning on starting a new game
I really feel sorry for the AI, they don't know what hits them, all the time.
I really want to help them out a bit, to sometimes having to change systems where you build a star base to bottleneck etc. is better than nothing, why I like this mod
I see, yes I forgot this, you did say this
I did something similar in a interview assignment for finding shortest route from point A to point B and it builds up a "memory" first and re-uses it.
I did see something in modding wiki, mean_time_to_happen
now just an idea (only dabbled with modding this game):
you can use mean_time_to_happen instead of the monthly or yearly pulses, make it like a few days after or so before or after or something or when you know the game is least likely to process other events etc. which "spreads" out the processing maybe and this could maybe, maybe I am not sure, reduce lag.
mean_time_to_happen = { months = 5 } or mean_time_to_happen = { days = 15 }
basically specify a alternative interval
If you want to change it have a look at the events called by on_actions as they determine creation / removal.