Chaosforge Forum

  • August 13, 2020, 04:46
  • Welcome, Guest
Please login or register.



Login with username, password and session length
Pages: [1]

Author Topic: [Fixed][0.9.9.6G] Mouse-run ending early prevents "You see a ____ here" messages  (Read 1275 times)

shark20061

  • Programmer
  • Elder Chaos Guard
  • Captain
  • *
  • *
  • Offline Offline
  • Posts: 266
    • View Profile

If command for mouse running stops because a monster comes into the field of view, messages for items on the ground stop showing up until a mouse move (>= 2 spaces) is completed successfully (that is, without seeing a monster).
« Last Edit: April 20, 2012, 00:03 by tehtmi »
Logged
Hell Knight Warrant Officer (0.9.9.4)  [26!/8/3/1/0]

Mancubus 2nd Lieutenant (0.9.9.6)  [22/12/3/0/0]
M:16 S:43 (126) A:17

Kornel Kisielewicz

  • God Hand
  • Apostle
  • *
  • *
  • Offline Offline
  • Posts: 4544
    • View Profile
    • http://chaosforge.org/

It's a feature. Using the mouse to run turns off item messages completely, so you don't get your message area spammed with several item descriptions when running over several piles of items.
Logged
at your service,
Kornel Kisielewicz

The DoomRLguy

  • First Sergeant
  • *
  • Offline Offline
  • Posts: 107
    • View Profile

It's a feature. Using the mouse to run turns off item messages completely, so you don't get your message area spammed with several item descriptions when running over several piles of items.
I believe the issue is that if a mouse-run is interrupoted by a monster, NO form of movement will display "there is a ____ here" message afterwards. You have to successfully perform a mouserun to get them back again.
Logged
Unexpectedness is always a surprise.
Arch-vile General
[26|23|21|13|6|1]

tehtmi

  • Programmer
  • Local Inquisitor
  • Lieutenant Colonel
  • *
  • *
  • Offline Offline
  • Posts: 451
    • View Profile

I believe the issue is that if a mouse-run is interrupoted by a monster, NO form of movement will display "there is a ____ here" message afterwards. You have to successfully perform a mouserun to get them back again.

This was indeed the case.  This is now fixed in the repository.
Logged
Pages: [1]