digactualhole() bit

I'm pretty sure this check at_u should be included since x,y
can be passed to digactualhole().  The lack of any related
bug reports suggest that at_u is currently always
true for any code that calls digactualhole().
This commit is contained in:
nethack.allison
2006-03-19 23:13:11 +00:00
parent 710c3dbe89
commit 3299e318ca
2 changed files with 2 additions and 1 deletions

View File

@@ -201,6 +201,7 @@ use "your kraken" instead of "a kraken" when searching reveals a tame
Magicbane should not produce "<something> are confused" message
handle antholes more sensibly when ants aren't available
cancelled nurses shouldn't say "Relax, this won't hurt a bit"
check for hero location in digactualhole() before clearing u.utrap
Platform- and/or Interface-Specific Fixes

View File

@@ -488,7 +488,7 @@ int ttyp;
boolean at_u = (x == u.ux) && (y == u.uy);
boolean wont_fall = Levitation || Flying;
if (u.utrap) {
if (at_u && u.utrap) {
if (u.utraptype == TT_BURIEDBALL) buried_ball_to_punishment();
else if (u.utraptype == TT_INFLOOR) u.utrap = 0;
}