Feature Request: running around still monsters

[Donald Jonker]

When running towards a still monster, such as a jelly/mold/mushrooms or something that's asleep, the @ should stop one tile away instead of landing right next to it.

And yes, I know you shouldn't run around jellies. But I'd like to.

[Zikke]

I set my run to stop when a monster becomes visible, then I manually run around it. Is this off for you?

[Donald Jonker]

It's more of a problem in the early game up to 1000', when I'm playing excessively quickly, and there's a jelly/eye/whatever in a room, and I run past it towards a corridor, not realizing that I'm going to move directly adjacent to it along the way. Bam: stat drain/confusion/paralysis.

This happens in corridors too: my run gets disturbed when I see the monster, but then I stupidly run to close the distance, thinking I'll shoot when I get closer.

I suppose it's a personal problem. But maybe enough other people do it also to merit a change to the disturbance rules, especially since it isn't ever a good idea to melee these critters... and even when it's safe to do so, you don't need to *run* into them.

[PowerDiver]

I set my run to stop when a monster becomes visible, then I manually run around it. Is this off for you?

Not really. Sometimes you just don't notice, and start the run with the monster in sight.

This got mentioned in a thread I started a year ago on new disturb options.

http://groups.google.com/group/rec.games.roguelike.angband/browse_thread/thread/65097fc34be9c6f5?q=eddie+angband+disturb+see+monster#2569797e5a566411

where the glorious maintainer wrote

> Any other ideas for new disturb options?

Disturb before moving into a grid adjacent to a monster. (for molds,
etc.) Though maybe that should just be hardcoded into the running code.