Opened 13 years ago

Closed 13 years ago

Last modified 11 years ago

#306 closed bug (duplicate)

run isn't working

Reported by: ChodTheWacko Owned by:
Milestone: Keywords: detection


using the run command aka . <direction> should always move you at least one spot.
In the attached save, you can't run straight up.

Attachments (1) (18.3 KB) - added by anonymous 13 years ago.

Download all attachments as: .zip

Change History (4)

Changed 13 years ago by anonymous

comment:1 Changed 13 years ago by anonymous

This is build 7-29.

comment:2 Changed 13 years ago by ctate

  • Resolution set to duplicate
  • Status changed from new to closed

'Run' as currently implemented will not cross the boundary from trap-detected to not-trap-detected floor tiles. That's what's happening here -- you're standing on the border, and the space immediately 'up' has not been trap-detected, so 'Run' up refuses to move. If you take one walking step 'up', you'll be in non-trap-detected territory, and then 'Run' will do its usual thing (on the assumption that you're paying attention are willing to risk hitting undetected traps).

It's definitely a bug that there's no good UI for this; I'm subsuming this ticket under the already-filed #222.

comment:3 Changed 11 years ago by magnate

  • Keywords detection added
  • Milestone 3.2.0 deleted
Note: See TracTickets for help on using tickets.