ติดตั้ง 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.