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
Regarding Better Perks... It has been supported since v3.14 but I did mark everything as incompatible while I was working on v4.0. Maybe that is why?
I suggest using Better Perks for the biggest buffs across all APs. My mod will detect it and add those changes automatically.
BTW, has Better Perks been supported before? I swear I've seen it as not-supported, but you've marked it as OK now.
Thank you for your patience:
@Seneschul
@kahvipensas
@AdamMarkIV
@Atlantispy
@Tigertycoon
@Lan
@thorman123456789
@everyone
For anyone that wants to rollback, you can use the legacy 3.14 data in the auxiliary folder. (This is for @waning crescent moon and @everyone still in 3.14)
Legacy folder if one must.
What do y'all think? Should I leave it in 3.14 for a bit more or should I push the 4.0 update?
Easiest way to fix that is to simply name a file ~z_machine_age.txt (something that starts with ~ or z), then add it to the ascension_perks folder within a local mod, copy and paste vanilla machine age AP script into that txt file and done. That fix does not account for other mods changes to machine age (if any, from your mod list) but it will show up and work like in vanilla at the very least.
I hope that helps you out a bit.
Now, with 4.0 version, your mod seems to not work currently, and I understand that you need some time to update it, but I wanted to ask: what in that mod could cause that? And is there a workaround without your mod that I can use to fix it for now? (Btw love your mod, great work!)
Thanks for your attention!
@Charly_Maxx Thanks!
Looking forward to your stuff!
Any patch with “~”at the beginning of its name. (e.g. ~ Ariphaos Patch)
Your other mods including modded perks and traditions.
*
*
*
! Sartek Ascension Perk Merger
! Sartek Economy District Merger Add-on
Any fix with “!”at the beginning of its name (e.g. ! Merger of Rules)
@ArutamSartek Added a script trigger called acot_cosmogenesis_alpha_condition_check for Cosmo AP.
Said update is also live now. incase you just missed it.
if = {
limit = { has_global_flag = acot_activated }
sartek_acot_cosmogenesis_potential = yes
}
But, alas it didn't work (trigger is overflowing) in the potential block, I can't do a placeholder for a whole event chain or technologies due to DUPL (Stellaris engine and how it reads technology scripts) issues.
[CN]突击队队员 Thanks for the report it should be fixed now.
For anyone else using ACOT, don't worry AP Cosmogenesis is still there and you can use it, is just less restrictive now and I have to talk with the authors so we can make it work as intended.
ACOT may have this flag enable at gamestart event.