Proposal: Better behavior after "It hits you".

[Hurkyl]

Proposal: take the logic that automatically turns autopickup off and on, and have it set/clear a flag. Modify autoexplore (and similar functions) so that if this flag is set, they prompt you (Y/n) before actually running. If you pick Y, the flag gets cleared.

Rationale: It is an extremely nice ease of use feature of crawl that things like autoexplore or automove don't run in the presence of monsters. This lets you do some number of mindless out-of-combat things mindlessly, rather than having to be constantly hyper-aware of your surroundings to tell if a monster has entered your LOS.

(in fact, sometimes I use autoexplore rather than manual movement, even when I'd prefer the latter, precisely to take advantage of this feature)

The fact that, except for autopickup toggling, this doesn't work with invisible monsters is a design oversight. The current situation of having autoexplore stop when you are hit by an invisible monster does cover many of the problematic situations. However, it fails to account for the situation where one is encountering frequent interruptions (e.g. dungeon features and items coming into view), and is inclined to continue auto-exploring, rather than having to pause and pay careful attention to the discovery every single time it happens. Another situation that is missed is when an orc wizard turns invisible just as you nuke it, giving the illusion it has been killed, at which point a person would generally start autoexploring again.

_____________

If the above feature cannot be implemented, I suggest the following:

Simpler hack: change the default config file to force a more message when an invisible monster is detected, e.g. by an "It hits you" message.

Yes, I know I could do it myself. I can (and will) probably even figure out how -- although it will probably take a few annoying iterations before I cover all the possible text messages. My point is that I think this should probably be the default, rather than something somebody has to put up with until they get the idea that it might be possible to customize the game to deal with it, and the motivation to figure out just how to do that.

[Sandman25]

force_more_message += ^It hits you
force_more_message += ^It.*misses you

Yes, I agree, default settings are almost unplayable, no one is going to take a break after every action to carefully read every new message in log.

[Hurkyl]

force_more_message += ^It hits you
force_more_message += ^It.*misses you

Yes, I agree, default settings are almost unplayable, no one is going to take a break after every action to carefully read every new message in log.

I think this misses "You block its attack." (what about if it casts a spell?). Of course, one of those are likely to be surrounded by those other messages.

[Sandman25]

Yes, I could miss some messages.

[Wahaha]

Adding a force_more for "It hits you" makes the game more unplayable.

[Sandman25]

Adding a force_more for "It hits you" makes the game more unplayable.

If you mean Prince Rabbit and Quasit, notice "^" in the beginning.

[duvessa]

I think that is probably not what he meant.

[nordetsa]

I think it would be really good if the game behaves same way as it does for submerged monsters nearby: if there's an invisible monster hitting you/drain your mp, you get the message 'There's something unseen in the distance. Continue Moving? (Y/N)'. It's gonna be tedious fighting orc mages, but at least players will know better if there's an invisible monster that they haven't noticed.

[dck]

shit accidental thanks
force_mores for something like that would be pretty horrible to deal with

[Hurkyl]

I think it would be really good if the game behaves same way as it does for submerged monsters nearby: if there's an invisible monster hitting you/drain your mp, you get the message 'There's something unseen in the distance. Continue Moving? (Y/N)'. It's gonna be tedious fighting orc mages, but at least players will know better if there's an invisible monster that they haven't noticed.

Normally you're not automoving or autoexploring when fighting orc mages -- making it take an active confirmation to do so is exactly what I'm looking for!

But I suppose you mean normal movement (I don't think submerged monsters interfere with normal movement). It would be annoying to take extra effort to move when you are aware of the problem, but it's also annoying to moving when you're not aware of it. My proposal does not consider normal movement.

[Sandman25]

shit accidental thanks
force_mores for something like that would be pretty horrible to deal with

Yes, I was surprised too
I have been using it for a long time and it actually saves time (for me) and prevents stupid deaths (for everyone).

[XuaXua]

Force more is how I've been handling it for some time. The carat fixes my RibbIT/quasIT problem.

I think having allies who can't sense invisible (use case for CANINE COMPANION) react properly as well would also be an improvement.