I am not much of a scripter, but I see a lot of monitors in the reform scripts that apparently has to be monitored at all times.For complex bits of code, I would probably recommend that people skip it.;; Check Kabalaka for >= gov3, if true increase counter 1.
monitor_event SettlementTurnStart SettlementName Kabalaka
and I_LocalFaction romans_scipii
and SettlementIsLocal
and SettlementBuildingExists >= gov3
and I_CompareCounter Caucasus_ReformA = 0
Certain complex reforms are not ameliorable to such. Other reforms such as the Celt's or the Sweboz's, are. In the end, the user will have to make a choice concerning whether they want the seleucid empire to have reforms while they sit and wait for turns to process. Or whether sacrificing an AI's reform abilities, one way or another, is worthwhile for the player.That is why reforms has to be in background script and not in run-only-once one.
When your editing the EBBS script for yourself, you usually shouldn't delete your own faction's reforms. For some people, running EB on a 6.7 meg background script is still too slow for their preferences. I don't support such modifications, because it would vary depending on how much speed and which faction a specific individual is playing with, but I do provide it as an option and idea for people to get started on if they so choose.
Bookmarks