Currently you see if a square is a moat or pool of water. You can quite
safely step on every square with an object. Changing this as you propose
would certainly introduce another point of nastiness. The behaviour of
this single item on water would be unique and will break the consistency
of game behaviour in this respect. Don't think I would like that change.
Janis
Yes, but what if wooden items, some corpses etc floated too? (Maybe
not elven weapons -- I assume they are made from some nasty heavy
hardwood.)
> Don't think I would like that change.
Maybe you should be able to see the ground under small objects in
general, e.g. traps under food rations. I don't see how that could
be implemented in monochrome terminal mode, though :-(
/Jorgen
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
DCSS uses reverse video for "there''s more stuff!" People without the
option set can use farlook the way they do now for color.
That's actually not hard to implement in NetHack either (I left out
the farlook stuff):
http://bhaak.dyndns.org/nethack/nh343-inverse-multiple-items.diff
I just don't know if I really like it.
Is it really visual appealing or is the additional info worth the
uglification of the map?
Should "2 apples" (if they are alone on the floor) also be
highlighted?
Should this feature depend on the setting of use_inverse?
Bye
Patric
--
NetHack-De: NetHack auf Deutsch - http://nethack-de.sf.net/
NetHack for AROS: http://sf.net/projects/nethack-aros/
UnNetHack: http://apps.sf.net/trac/unnethack/
I might use it when I feel like messing with it to use use_inverse.
> I just don't know if I really like it.
Eh, I don't. It was just a possibility.
> Is it really visual appealing or is the additional info worth the
> uglification of the map?
Options.
> Should "2 apples" (if they are alone on the floor) also be
> highlighted?
It isn't already, so probably not. Though I would; it can't be that
hard to see how many there are. Possibly combined with L's innumeracy
patch.
> Should this feature depend on the setting of use_inverse?
Either that, or a new option. I'd roll it into use_inverse, because I
really can't think of anything else that uses that option.