You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on a max-Tox-stacks run. I happened to have the map screen set to Exit to World, probably from my play before Autotrimps. Each time a map was cleared the script pointlessly killed the active army and had to sit there repopulating. Switching to Exit to Maps mode fixed the problem.
This issue was wasting approximately 5 minutes per zone. Ouch!
The text was updated successfully, but these errors were encountered:
don't do this. Would you rather Autotrimps removed those buttons ? If there was a user manual, "dont press those buttons" would be in it. But i don't think disabling or removing them is a good idea.
I didn't say the buttons should be removed. I was suggesting that autotrimps should be smart enough to click the button itself when auto-running maps, to avoid pointlessly killing thousands of armies and wasting over 8 hours on a single run. (About 5 minutes per zone, for about a hundred zones in my case.)
Currently testing this code in the genbtc branch:
With this installed, this means the only button you can use other than the default red ones is "repeat to 10".
//Control in-map right-side-buttons for people who can't control themselves. If you wish to use these buttons manually, turn off autoMaps temporarily.
if(game.options.menu.repeatUntil.enabled == 2) toggleSetting('repeatUntil');
if(game.options.menu.exitTo.enabled != 0) toggleSetting('exitTo');
if(game.options.menu.repeatVoids.enabled != 0) toggleSetting('repeatVoids');
I'm on a max-Tox-stacks run. I happened to have the map screen set to Exit to World, probably from my play before Autotrimps. Each time a map was cleared the script pointlessly killed the active army and had to sit there repopulating. Switching to Exit to Maps mode fixed the problem.
This issue was wasting approximately 5 minutes per zone. Ouch!
The text was updated successfully, but these errors were encountered: