PlaneShift

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bug Report
  • Category Engine
  • Assigned To No-one
  • Operating System
  • Severity Critical
  • Priority
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 1
  • Private
Attached to Project: PlaneShift
Opened by Minks - 14.02.2010
Last edited by RlyDontKnow - 18.02.2010

FS#4098 - Permanent exhaustion/business while digging/fishing

When during /dig or /fish the physical stamina bar reaches 0 (”you are too
exhausted to move”), you stay frozen to the spot forever. Stamina grows back
normally.

Turning, walking, /sit is not possible as if you are still exhausted.

/dig or /fish get the message “You cannot xx because you are already busy”.

Client version 0.5.1.1, tested on Vista 32 bit and Linux 32 bit

Closed by  RlyDontKnow
18.02.2010 15:00
Reason for closing:  
Additional comments about closing:  

fixed on trunk

Franta commented on 14.02.2010 20:44

It's also happening when running alone or with mount and the stamina is very low while the running/walking button is released and stamina drops to 0 after releasing the button. It looks like client doesn't update stamina status on server when there is not any action and stamina drops down. It never happens when the run/walk button (or autorun) is active while the message "You are too exhausted to move" appears on the screen. Possibly automatic stamina update between client and server at given interval, say 10 seconds, could help.

aurelynt commented on 15.02.2010 20:54

Confirmed with running on trunk.
Steps to reproduce:

- Start running with by pressing the forward key.
- Release the forward key when your stamina is about to reach 0 (don't wait for "you are too exhausted to move" to release the key)
- Do nothing while waiting for the message "you are too exhausted to move".
- Try moving again: impossible! You need to relog. Yet your stamina is recovering.

Maui commented on 15.02.2010 22:55

same happening when crafting

RlyDontKnow commented on 16.02.2010 23:24

could be fixed by this patch, though this would shorten the time you're exhausted to the time you're actually below the minimum to move.
the issue seems to be that due to some race condition no DR update is issued after setting the regeneration rate which results in no further check whether you should be set back to normal or not.
therefore the patch performs this check on each StatDRUpdate while being exhausted to make sure you're actually unlocked.

in order to keep the current behaviour of being locked for a while, the reason due to which the check isn't issued at all under that condition would have to be researched and changed accordingly, though I couldn't find out where that check is issued.

Sarva Ghars commented on 17.02.2010 17:31

Note having a GM freeze you then thaw you will allow you to move again.

RlyDontKnow commented on 17.02.2010 21:03

a fix commited by weltall, should be fixed on trunk

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing