ice timeout (trunk only)
Zapping cold at an ice location which has a melt timer would set new timeout to a random value which could actually cause that ice to melt sooner. Make sure the new value is always at least as big as the old one. Also, MAX_ICE_TIMEOUT wasn't actually the maximum ice timeout; now it is--if the generated value is higher, omit the timer so that that ice is permanent. No fixes35.0 entries necessary; this is post-3.4.3 code.
This commit is contained in:
@@ -2628,7 +2628,7 @@ E struct monst *FDECL(boomhit, (struct obj *,int,int));
|
||||
E int FDECL(burn_floor_paper, (int,int,BOOLEAN_P,BOOLEAN_P));
|
||||
E void FDECL(buzz, (int,int,XCHAR_P,XCHAR_P,int,int));
|
||||
E void FDECL(melt_ice, (XCHAR_P,XCHAR_P,const char *));
|
||||
E void FDECL(start_melt_ice_timeout, (XCHAR_P,XCHAR_P));
|
||||
E void FDECL(start_melt_ice_timeout, (XCHAR_P,XCHAR_P,long));
|
||||
E void FDECL(melt_ice_away, (ANY_P *, long));
|
||||
E int FDECL(zap_over_floor, (XCHAR_P,XCHAR_P,int,boolean *,SHORT_P));
|
||||
E void FDECL(fracture_rock, (struct obj *));
|
||||
|
||||
Reference in New Issue
Block a user