nethack-gwaa-kiwi/nethack
1
0
Fork 0
Code Pull Requests Activity

fix github issue #608 - #untrap vs web

Browse Source 
Reported by Vivit-R, the chance of freeing a monster from being
trapped in a web was very small and failure resulted in creation of
a new web at the hero's spot, eventually making it impossible to
attempt to #untrap the monster (if hero escaped the new web and moved
to another spot adjacent to trapped monster, eventually surrounding
it with webs).  [That's actually misleading.  Escaping the new web
but staying at the same spot lets the player try again; repeat as
needed....  But chance of failure still seemed way too high.]

This reduces the chance of failure from 29/30 to 6/7 and makes the
chance of spreading the web after failure be 1/3 instead of 100%.  It
also supplies missing feedback about the monster still being trapped
if the attempt to make a new web fails.

Closes #608
This commit is contained in:
PatR
2021-11-18 18:30:19 -08:00
parent 937eef4b9b
commit d26537c4c9
2 changed files with 28 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/fixes37.0
View File

@@ -679,6 +679,11 @@ prevent normal monster activity from picking up the mines' luckstone or the
and/or engraved Elbereth wasn't sufficient to guard the Sokoban prize
proceed a little further into dochat() if hero is deaf
stacks of 1 to 49 gold pieces weighed 0
the chance for #untrap to free a monster stuck in a web was very unlikely
unless was poly'd into spider form; make it less hard
if #untrap monst-from-web failure happened while hero was standing on a spot
where a new web couldn't be created (furniture, grave, magic portal),
the expected "<monst> remains entangled" feedback wasn't delivered
Fixes to 3.7.0-x Problems that Were Exposed Via git Repository