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
Also those console commands are for vanilla, you mod might work weird with them.
I was wondering if anyone had experienced the same, if I could fix it with a console command or if its a bug from the mod.
Name and source of mod would go a long way to help here.
I think changing a setting in the mod's CFG file will solve the issue if I am right in my assumption.
Its Europa Barbarorum 2 and im 500 turns deep in my campaign when the AI is halted by the script i assume, but it never gets re-launched unless i write it into console. I've tried waiting for 40 min, the game is literally just paused with no AI.
You can have scripts were battles are forced, eg after two armies have been spawned near each other. but that only ever works for that one battle.
Having said all that (AI settings have no way of forcing automatic auto resolve to start with) I am starting to think that it might be a memory (leak) issue. 500 turns is an extremely long campaign and with it comes increased memory load, like every character ever create din the game gets retained in memory and stuff like that.
And EBII already starts of with a good number of characters.
Can you run the save for a while without issues after restarting\reloading?
After 2 turns the ai is halted everytime.
I have a 700 turn campaign saved as Swebos with no problems.
Edit: Yup, there is one, must have been after my time..
Found a single one (line 75468) that stops the AI for the purpose of faction re-emergence processing. and then restarts it (line 78436) when the process is finished.
Now if the restart failed then simply issuing the run_ai command as you did should get everything back to normal. And it certainly shouldn't perpetuate auto resolve, certainly not for random\manually started battles.
I'll drop a note at the dev forum to have a look into it.
Yes the source of the bug is related to Pergamon re-emerging and instantly turning to rebels. Also some those stacks are standing in a river and cant be attacked.
https://i.imgur.com/DSrJvVN.png
I guess i'll start a new campaign with patch 2.4a and hope they fixed this.