fix #H7385 - double trap activation when jumping
Jumping performs the placement of the last step after using hurtle() to move to the destination, so if hurtle() triggered a trap then it would happen twice. Report was for a Sokoban pit but it would happen for fire traps too. Other traps would yield "you pass over <trap>" while hurtling and then trigger the trap when landing. Have hurtle_step() ignore a trap for the last step of a jump, leaving it to the jump's landing to handle. Also, give feedback when hurtling over water or lava, similar to what happens when passing over a previously seen trap which doesn't activate.
This commit is contained in:
@@ -114,7 +114,7 @@ add window port status_update() value BL_RESET to use as a flag to
|
||||
for hilite_status of string status fields (title, dungeon-level, alignment),
|
||||
the types value-goes-up and -down aren't meaningful; treat them as
|
||||
value-changed if from config file and don't offer as choices with 'O'
|
||||
spiders will occasionally spin webs when moving around
|
||||
jumping into or over a Sokoban pit, or over a fire trap, triggers trap twice
|
||||
|
||||
|
||||
Fixes to Post-3.6.1 Problems that Were Exposed Via git Repository
|
||||
@@ -182,6 +182,7 @@ make it clear when a leprechaun dodges your attack
|
||||
wizard mode #wizidentify can now select individual items for permanent
|
||||
identification and don't display the selection to permanently
|
||||
identify everything if everything is already fully identified
|
||||
spiders will occasionally spin webs when moving around
|
||||
|
||||
|
||||
Code Cleanup and Reorganization
|
||||
|
||||
Reference in New Issue
Block a user