Malibu Stacey
Active member
No idea if this is a bug or just user error but my feeling is a bug.
With the following properties set
hpAutoRecovery = -0.05
hpAutoRecoveryTarget = -0.05
mpAutoRecovery = -0.05
mpAutoRecoveryTarget = -0.05
manaBurningTrigger = -0.05
manaBurningThreshold = -0.05
autoAbortThreshold = -0.05
So effectively, everything should be disabled according to the UI.
The following still happens
(had to copy that out of the session log as the CLI had scrolled past it by the time I thought to report this as I'd restarted autoscend and the session log doesn't log the "Insufficient health to continue message" that the CLI showed at that point when it aborted).
Basically, ending up on 0 HP during a call to adv1() causes a hard stop to automation such that the afterAdventureScript doesn't run. Which is an issue when you're relying on your afterAdventureScript to do things like heal you after combat.
With the following properties set
hpAutoRecovery = -0.05
hpAutoRecoveryTarget = -0.05
mpAutoRecovery = -0.05
mpAutoRecoveryTarget = -0.05
manaBurningTrigger = -0.05
manaBurningThreshold = -0.05
autoAbortThreshold = -0.05
So effectively, everything should be disabled according to the UI.
The following still happens
Code:
[709] Sonofa Beach
Preference lastEncounter changed from The Walking-Stick Rebellion to Zerg Rush
Encounter: Zerg Rush
You lose 107 hit points
Stack trace:
(had to copy that out of the session log as the CLI had scrolled past it by the time I thought to report this as I'd restarted autoscend and the session log doesn't log the "Insufficient health to continue message" that the CLI showed at that point when it aborted).
Basically, ending up on 0 HP during a call to adv1() causes a hard stop to automation such that the afterAdventureScript doesn't run. Which is an issue when you're relying on your afterAdventureScript to do things like heal you after combat.