I was trying to reproduce the reported "no monster to remove" warning from remove_monster() when a mounted hero was knocked off jabberwocky steed but so far haven't been able to. While trying, I came across a more minor bug. The hero got knocked off a flying steed and got feedback of "you fly off" rather than "you fall off". Flying capability came from the steed and dismount feedback is aware of that but calls u_locomotion() which isn't. This commit fixes that. This adds some groundwork (DISMOUNT_KNOCKED) for better dismount control. With a map fragment of |.... |.Du. |.... I got knocked off my steed by the attacking dragon and ended up with |..@. |.Du. |.... It would be better to prefer spot 1, then the 2s, then 3s, then 4s (not sure about farther spots if none of those are available) |.432 |.D@1 |.432 when forced to dismount by knockback. This does _not_ implement that.
34 KiB
34 KiB