Feature Request (or bug?): Autoexplore without rest above rest_wait_percent

Back Room Technical Support
1

I was attempting to debug what I thought was an issue with my rcfile, where I set my rest_wait_percent to 20 (with explore_auto_rest = true) conditionally using Lua, but autoexplore was still waiting up to 100%. After failing to track down the issue (including removing the Lua and just setting to 20 by default) I finally realized it may technically be behavior as intended: I believe pressing “o” to autoexplore when you are above rest_wait_percent is being treated like pressing “5” to rest when above your rest_wait_percent, which I suppose technically makes sense, but…

This means there’s effectively no way to activate autoexplore without resting to 100% if you’re already above your rest_wait_percent (besides, I suppose, creating a Lua function that checks if you’re above it, disables explore_auto_rest, sends key for autoexplore, then reactivates explore_auto_rest at the next ready.)

I also think this makes the options_guide.txt statement for explore_auto_rest If true, auto-explore waits until your HP and MP are both at rest_wait_percent before moving misleading, because, in fact, it only demonstrates that behavior if you’re below rest_wait_percent—otherwise, auto-explore always waits until you’re at 100%!

At the very least, I think options_guide.txt for explore_auto_rest should read more like:

explore_auto_rest = true
        If true, auto-explore waits until your HP and MP are both at
        rest_wait_percent before moving. If you are at or above your
        rest_wait_percent when you activate auto-explore, it will rest up to 100%.

But what I’d really love would be an option to change this behavior. I’m not sure how hard that option would be, but my hope would be a simple conditional and not too hard. The desired behavior for this new option would be something like:

explore_auto_rest_above_wait_percent = true
        If false, auto-explore will skip resting and immediately begin moving
        if you are above your rest_wait_percent when you activate auto-explore.
        If the explore_auto_rest option is set to false, this option is effectively ignored.
1 Thank
2

For me the intuitive behaviour would be that if you are above your rest_wait_percent, going into autoexplore will never wait for you to reach full hp. I don’t see why that would even need to be an available option.

3

While I agree that this would be more intuitive, if that was set as the default behavior, it would be a massive change to existing behavior—suddenly every player with rest_wait_percent < 100 that expects hit “o” and feel safe exploring might start exploring at a low health until they read the changelog in detail, so I imagined an option might be a better transition if this if was implemented.

1 Thank
4

Realistically, if I set my rest_wait_percent = 40, I expect to only be auto exploring with hp > 40%. I would not under such circumstances complain to anyone “my character started auto-exploring with 51% hp instead of waiting for full hp, and then I died :sob: :sob:”.
And more than that, I can’t currently imagine a scenario where I would sympathise with someone who does complain like that.

There’s much worse changes that are pushed through Trunk without warning, like the opportunity attack changes.

The only cases where people are almost certainly aware of and (ab)using the current behaviour is if they set rest_wait_percent = 0 or -1. Since they could have just set the rest_wait_percent to 100 instead, I don’t think it is worth developer time to save them. And besides, they’ll notice extremely quickly.

5

I think there’s a significant difference between a change to game mechanics - good or bad, the new design can’t be implemented without changing things - and a change to how options behave where the old behaviour could remain the default.

That said, as someone who has always had it set at 100, I would not have guessed for one minute that autoexplore didn’t respect lower settings.

1 Thank