melting ice timeout issues
Reported directly to devteam by entrez via email: > > I noticed some potential issues with (melting) ice: > > * Digging down into ice, or setting a land mine on the ice and > triggering it, doesn't remove the melt_ice timeout, so it can result > in a sequence like dig down -> pit fills with water -> freeze water > -> freezing water tries to set melt_ice timeout -> duplicate timeout > impossible. Or if you don't freeze the water again, melt_ice will > run on a non-ice surface, which might at least produce strange > messages. > > * Setting a land mine on ice: melting ice doesn't do anything with > the trap, so there is still a land mine which you can trigger by > flying over the water (the land mine's trigger is also still > described as being 'in a pile of soil', despite being underwater at > this point). Similar thing happens with bear traps. > > * Not really related to _melting_ ice, but an exploding land mine > doesn't reset the typ from ICE to FLOOR (like normal digging does), > so it will result in a square with a pit that is also an ice square, > where the ice can melt under the pit and produce a combination > pit/moat. If you then freeze the moat, the pit reappears on top of > the ice.
This commit is contained in:
@@ -897,6 +897,7 @@ extern int max_capacity(void);
|
||||
extern boolean check_capacity(const char *);
|
||||
extern int inv_cnt(boolean);
|
||||
extern long money_cnt(struct obj *);
|
||||
extern void spot_checks(xchar, xchar, schar);
|
||||
|
||||
/* ### hacklib.c ### */
|
||||
|
||||
@@ -2685,6 +2686,7 @@ extern void sink_into_lava(void);
|
||||
extern void sokoban_guilt(void);
|
||||
extern const char * trapname(int, boolean);
|
||||
extern void ignite_items(struct obj *);
|
||||
extern void trap_ice_effects(xchar x, xchar y, boolean ice_is_melting);
|
||||
|
||||
/* ### u_init.c ### */
|
||||
|
||||
|
||||
Reference in New Issue
Block a user