You can't bankrupt an AI clan/family/country to the point that they "lose" or go rebel. In Rome: Barbarian Invasions i actually lost the campaign because i was so bankrupt and in the red (destroyed a bunch of outlying towns and moved all the armies so instead of being spread out i was more together.didn't work out for me). In Shogun 2 i've killed Daimyo's in the lone region a clan has left, then put the town under siege and ended turn.only to have a brand new Daimyo pop up in the town. I think Creative Assembly figured out this trick because you can't do it anymore. In Rome 1 you could assassinate every, we'll say Gaul, general and then the faction would "die" and become rebel and then you'd have an easier time taking regions because rebels rarely leave. Also, as has been pointed out to me by far smarter people here, some of the AI "cheating" is written that way so as to adjust to playing against a human. Hope this helps anyone playing this old gem of a game.I wouldn't say "cheat" so much as the AI plays by different rules. Then when you need to enable/activate the features again, just follow the same steps. So, an easy fix or to get around this, you should use whatever features you're gonna use, for whatever you're gonna use it for, and disable all, if not most, activated/enabled features within the table/trainer before you end your turn or end battle(once you win or lose). Shogun 2 has been known to use internal methods that detect game altering programs such as trainers and cheat engine programs.įor example, usually, it runs a background scan or checks for altered data whenever you end your turn or before enter or after you exit a battle. I believe this has been discussed before, but, I'll mention it again.
Rather that be on the campaign map or in battle. Even after them being activated for long periods of time. That's my modded setup at the moment and I can activate/enable most, if not all, features within the table without any crashes. Which, basically consist of 3 basic mods that don't really alter much. I can confirm as of August 03, 2020, that this table still works completely without crashes.
0 kommentar(er)
