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
thanks again!
ooh. Then don't mind it too much then. Since there's a workaround with rage mode, it's not really that big of an issue.
I see~ I'll try copying the block code from the main game folder and commenting the delete command.
thank you very much~
For the behemoths bombard, this is highly complex. I tried for a long time to have the behemoths bombard properly or actually use the 'eat planet' ability in the uncontrolled situation, but there were many things that were mutually exclusive. I can take another look at this, but it isn't trivial because of how bombardment and wars work.
You should be able to do this by editing the event that spawns the fleet - it likely sets a delayed event that is responsible for deleting the fleet. Removing this should stop the fleet expiration timer.
Is there a way to remove the 6 month expiration on the Class IV behemoth's spawn fleet ability?
as for the Chrysalis hatching.
It made me lose my mind a bit because "owner = { is_country_type = behemoth_apex_mind }" wasn't working properly for me so I used your country_flag instead, and I used "From" instead of owner.
possible = {
OR = {
hidden_trigger = {
From = { has_country_flag = behemoth_became_apex }
}
custom_tooltip = {
fail_text = behemoth_cocoon_tt
exists = owner
owner = {
has_menace_perk = menp_behemoth_hatchling_2
}
}
}
}
managed to make it work but it might have some unforeseen circumstances so I wanted to check in with you about it.
thanks again for taking time to help me!
I didn't modify the layable egg - its behaviour is still vanilla. It shouldn't be too hard to make the normal growth work though on your end - try editing the 'possible' block on both 'behemoth_chrysalis_hatch' and 'behemoth_chrysalis_big_hatch' (both need to be changed since CII and CIII chrysalises are different structures entirely) to the following:
possible = {
custom_tooltip = {
fail_text = behemoth_cocoon_tt
OR = {
owner = {
is_country_type = behemoth_apex_mind
}
AND = {
exists = owner
owner = {
has_menace_perk = menp_behemoth_hatchling_2
}
}
}
}
}
The Class IV behemoth can still lay eggs on any Gas Giant. And you can still somehow hatch said eggs manually.
But the Chrysalis is an issue. While I managed to let behemoths grow even outside borders by using "#".
The game is telling me I don't have the Menacing perk required to make the Behemoth evolve. So I tried giving the country_flag you made for the new country type as an OR condition with the normal menacing perk. And I know my empire has the flag, I checked with the console commands. But still no dice. Game doesn't recognize either my menace perk or the country flag. Can't hatch the Chrysalis.
How did you enable players to hatch the layable egg? If that's possible, hatching the Chrysalis should be possible too.