Issue reported by ars3niy: an arrow trap covered by more than one stack of arrows was described by farlook as "unexplored area". Later simplified to any object pile with plain arrows on top; the trap turned out to be irrelevant aside from producing a pile of arrow stacks. This problem turns out to be due to an off by 1 error introduced into the xxx_is_piletop() macros when generic objects were added in mid-January of last year, and plain arrow is the first real object so suffered from the bug. Misclassifying the glyph at a specific location also confused the #terrain command but it's the same bug. Knowing what was wrong (map glyph was UNEXPLORED when it should have been ARROW) wasn't sufficient to figure out the problem. Without the simplified way of reproducing the problem, I would never have managed to use 'git bisect' to find the offending commit because that would have been too time consuming. Fixes #1289
46 KiB
46 KiB