Doctornull wrote:
One annoying thing I noticed ... when my dude stops walking due to some silly triviality like "damaged by stepping on lava", or "ooo look it's blighted soil", he loses track of where he was headed, and I have to go back through the interface to re-select a landmark, often times twice (since he'll stop in front of a notable feature and then stop again on top of the feature).
Yeah, I ran into that in testing. That is kind of annoying.
Doctornull wrote:
Would it be possible to do something like...
- Landmark menu sets target tile in some persistent variable
- Hitting a key resumes auto-walk to target tile
- Landmark menu sets target tile in some persistent variable
- Hitting a key resumes auto-walk to target tile
Now, do you mean hitting any key, or hitting a particular key?
Doctornull wrote:
Ideally, it would integrate with the default auto-explore / auto-exit finder, making the 'z' key work like...
- Have target tile? Try to go there!
- At target tile when 'z' hit? Check if zone is fully explored!
--- Not yet: Auto-explore!
--- Zone all explored: Auto-set target tile to nearest exit (excluding current tile) and try to go there!
That would preserve current behavior and cleanly integrate landmark targeting, allowing me to resume progress to target landmark even if interrupted (by a monster or other landmark or suffocation or whatever).
- Have target tile? Try to go there!
- At target tile when 'z' hit? Check if zone is fully explored!
--- Not yet: Auto-explore!
--- Zone all explored: Auto-set target tile to nearest exit (excluding current tile) and try to go there!
That would preserve current behavior and cleanly integrate landmark targeting, allowing me to resume progress to target landmark even if interrupted (by a monster or other landmark or suffocation or whatever).
So, hitting the 'z' key, then. That would certainly be feasible in theory, though it would mean diving into the uncharted depths that is the auto-explore code...
Now, I wanted to be careful not to leave auto-explore in an invisibly hijacked state, continuing to go back to the same landmark when the player no longer wants it to, so I'm using a slightly dodgy hack, inspired by the Antimagic Disruption effect you get if you wear arcane-disrupting equipment while being arcane. In this new version, when you use the go-to-landmark function you are given a new temporary status effect Going to Landmark, which persists until you arrive at the landmark, leave the level or cancel it manually; as long as you have this effect, the auto-explore key will try to go to your most recent landmark instead of doing its usual auto-exploring. That seemed like a reasonably clean way of keeping the player informed of what's happening.