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
It is by design that star systems are destroyed when MCSS is completed.
Make sure you have colonized star systems in addition to your fortress systems.
My last and final question, because I am not sure if this is how it should be.
Is it normal or planned that all planets / Babel`s Spires are destroyed by the gigastructure/ship as soon as it is complete? (Game Over)
I fixed it with an external planet, one hyperlane away.
@6thStrikeUnit
The description regarding MCSS upgrade has been corrected.
Sorry if I'm bothering you with this, unfortunately I found something else... i think
(Always for machine species).
The same flag problem is now at Stage 2 God`s Heart -> Upgrade -> to God`s Brain.
The flag requires 50 pops on every rebooted planet*.
(I tryed 50 - 500 - 5k and 50K [yes i have no other hobbies])
Even with Console/debugtooltip it didnt worked to skip/set flag/instabuild.
*Or do they mean the Babel`s Spire? They are not colonizable for me.
I mainly tried the “fcss_mcss.5XX” [20-40] but without success.
Unfortunately I'm not a dev so I don't know much about it.
Thanks in advance. =)
The internal program has been modified.
(Theory: The resource option is accidentally linked to the slave flags?)
(I even bought slaves for the other options, but negative).
You couldn't even bypass the flags with comands. Unfortunately... =/
If you could fix that would be great, the modpack is really cool so far. =) @6thStrikeUnit
And also. Can i only use slave pops to deploy stasis graves? I'm currently on a playthrough with this origin. And I'm worried that once I reached the point where I'm able to mechanize my slave pops (so I can actually put them on the machine planet). It turns out that deploying stasis graves is completely bugged anyway.
I updated it to the version that added the variables.
It's a new technique that allows compatibility support with max performance.
How would I add this?
I already set a mod-specific global flag when the game starts.
Thanks!
As far as I can tell from my testing, I was able to find obstacles at both origins.
Could you tell me the mod configuration you are using?
Many of the events are tied to the removal of planetary obstacles, so there is no trigger that can launch the event on its own.
In what environment is this bug occurring?
In the case of origins other than for machine intelligence, there will be obstacles on the machine planet side that is not the home planet.
By removing terrain obstacles on the planet, events will occur one after another.
荒廃したエネルギーリングが見当たらない場合は以下のコマンドを実行してください。
effect add_deposit = planet_energy_ring_0
未探索の地下構造物が見当たらない場合は以下のコマンドを実行してください。
effect add_deposit = d_capital_underground_structure_1
effect add_deposit = d_capital_underground_structure_2
effect add_deposit = d_capital_underground_structure_3
effect add_deposit = d_capital_underground_structure_4
planet_class pc_awaken_ai
このコマンドは指定した惑星の種類を「古代の機械惑星」に変更します。
入植している惑星種類「機械惑星」の数が1を超えると建造段階2で詰む可能性があります。
1を超えている場合は別の惑星にテラフォーミングしてください。
惑星種類「古代の機械惑星」はジークフリートなど惑星を書き換える巨大建造物を建てると詰む可能性があります。
国是「最後の守護者」にはFCSS関連起源・国是以外の制約を設けていないので可能なはずです。
戦闘星系の稼働自体はどの起源でも可能です。
No AI is used.
It is incompatible with mods and vanilla elements, as many elements become unusable at the expense of making the nation itself immortal.
I will add an option that does not change the national structure.
The MCSS escort fleet will be neutralized by the attack, but the MCSS itself will not be sunk unless the central main ship is destroyed.
We have not yet implemented a means of building MCSS that is origin-independent. (to be implemented in the future)
The mobile combat system itself cannot be designed.
You can select the type of armament to deploy from the Mobile Combat System menu.
No particular crashes have occurred in this environment, but under what kind of environment is the crash occurring?
There are no particular changes, so I don't have any plans, but if there is an additional element, I will update it at that time.
なにか悪さしているのでしょうね。こちらで調べてみます。ご回答ありがとうございました。
属国形態のバグに関してはこちらでは確認できませんでした。(属国化の提案では普通に属国形態が選択でき、その後の属国化もできました)
機動戦闘星系の戦闘後挙動に関しては、戦闘形態の解除にある程度時間が掛かるためその間は移動速度を大幅に低下させています。
(戦闘形態のままで他星系に移動すると挙動がおかしくなるため)
長文で本当にすみません!
そして、 機動戦闘星系のテクスチャの作り込み、機動戦闘星系の戦い方、
ロマン度、ストーリーなどなど全部最高です!
MOD製作者様とこのコメントを読み切った勇者達に感謝を~。
そいつより恒星1、2個分ぐらい小さいんですよね。大きさで負けてる”機_の_”って、、
と落胆したので、製作者さん、よかったら大きくしただけ版をMCSS管理メニューの
MODオプションのと所とかに追加してくださいお願いします!
機動戦闘星系っていうからには笑う程バカでかいんだろうな~とおもっており、
機動戦闘星系の材料もバカ程大量だった上、機動戦闘”星系”とついているから星系の
半分ぐらいはあるんじゃないかと期待していたのですが完成したらブラックホール3、4個
程の大きさで”機_の_”とか”言われているのに戦闘は強くてかっけぇのに大きさが残念な
感じでした。似たようなものでギガストラクチャーMODのベヒモス衛星数個と
攻撃衛星十何個ぐらいでできる”機動恒星要塞艦”という艦があるのですが、