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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
The random feature both researches dangerous techs, techs you cannot use AND there's no way to stop tech being researched. So the obvious example is researching synths as a spiritualist who has AI not allowed. The Unbidden can arrive earlier than end game + 50 if Jump Drives is researched, which can be very challenging if your alloys were just sunk into mega construction projects.
Researching droids can disrupt your workforce if you've deliberately used worker bots without happiness and had 100% bio pops as specialists.
There's no opportunity for bee lining, avoiding uncessary research of unused techs or gearing up for war and catching up in times of peace.
I kinda want to rewrite some code to have a UI a bit better (UI modding is annoying and not flexible, but it should still be better than the current one) and investigate the slowdowns some users have reported.
But I'm kinda busy at the moment (IR and 2 other big mods I'm working on), so noooooo update date (it might be a separate mod/upload btw)
However that may risk "dangerous tech" and it doesn't permit min-maxing by excluding categories you don't need. At times preparing for war, I excluding all the economy repeatables, then as war was ending switched back to cheapest as the battle was won.
For most the 3.0 auto button does the job, however the author's full featured implementation means the work is still useful. I am adding to my "Test 3.0" mod list, so far just 1 mod has caused me trouble and that may have started due to a bad gfx driver update.