This setting only affected cache duration (which was capped to 5 minutes and performed effectively as 3), not auto-commit.
Fixed commands not functioning when no worlds were configured.
Fixed /regionerator reload not enabling and disabling all configured features as expected
Note that as of 2.0.0 reloading does not interrupt or restart active cycles; they continue on their merry way where they left off.
Fixed /regionerator pause not pausing active cycles
Moved config.yml's delete-this-to-reset-plugin to data.yml's next-cycle
QoL: when a world is removed from Regionerator, you no longer need to manually remove its next cycle to prevent re-adding it later starting deletion earlier than intended.
Removed a couple unused methods
Ordinarily I'd deprecate and wait for a major bump for removals, but frankly this is such a niche plugin that I don't think anyone's writing their own hooks or using the API. If you do happen to know of anyone who does, feel free to yell at me so I'm more careful in the future. The only thing I see possibly affecting anyone is Regionerator#getProtectionHooks' return type changing from a List to a Set.