After a trap has been set, its damage range is not fully shown

[aeoo]

I notice that after I set a trap using for example a dagger, the game only shows me a few red 'x' squares of its damage range (and sometimes none at all), but all I have to do is hit the targeting key '*' to see the full range. It seems obvious that the player is meant to instantly know the range of their own traps, which is even displayed when you're targeting them during the setting of the same trap, but the game will only display this range correctly after the player hits '*' to enter targeting mode.

[DGoldDragon28]

Could not reproduce. May be reopened if more information on the circumstances of occurrence is given.

[aeoo]

OK, I'll try to document every step as I take it.

1. Unzip the windows distribution into a fresh directory.

2. Run it for the first time:

3. Adjust the font to the largest possible:

4. File/New/Desktop/Played Unangband before/Male/Man of Rohan/Rogue/Bows/Spellstealing:

5. Spend points:

6. Accept the default name, enter to continue, space to dismiss the initial "Here your adventure begins..." note.

7. Drop/from equipment/rapier and find where it landed in the grass:

8. Jam/floor/a/*/p/3 squares to the East

9. t to Target!

No range is shown now, and this is a bug.

But:

10. Hit '*':

And here we see the range is correctly marked with the red 'x'es simply for entering a targeting mode.

Also, I have a sneaking suspicion that moving the mouse will reveal the target range too, which is probably why you couldn't duplicate the bug, because likely you held or moved the mouse with the mouse tracking enabled right after you targeted your trap. I'll test this assumption right now on my end.

OK, so even after I moved the mouse around the range still didn't show post-targeting (and successfully loading the trap, so I had to try arming the trap a few times to succeed in this case).

So I'm not sure why you can't dupe it. I used all the defaults including the original keyset for this duplication of the bug. Please let me know if I can be of any further assistance.

[DGoldDragon28]

I believe the x marks show once you have refreshed the map, i.e., done basically anything. If the issue is only on the first turn, where movement reveals the range, it is not worth fixing.

[aeoo]

I respect your decision whether you decide to fix it or not, but for me the movement doesn't always reveal everything. At least I know that I can just hit '*' and instantly fix it, so it's not a huge deal even for me, but for new players this may be confusing. Accurate and instant feedback is much more important for someone just learning the game than for someone who is already familiar with its quirks.

[DGoldDragon28]

I'll look into it in that case, but low priority compared to other bugs you've reported.

With as many bugs as you've reported, have you any experience with C (i.e., are you able to maybe help me do these fixes faster)?