Since this is a 13 year old bug I doubt it's fixable. The solution was always to move, on your screen, to where you should be.Sorry i thought it was pretty well known
When you dash you can sometimes get stuck, on your screen you will move positions and the mobs will appear to be moving to a position where you are suppose to be. You cannot move and the only way to get unstuck is to dash again
---------- Post Merged at 11:58 AM ---------- Previous Post was at 11:55 AM ----------
http://www.lomcn.org/forum/showthread.php?84861-Shoulder-Dash-Bug koriban explains it better here
Since this is a 13 year old bug I doubt it's fixable. The solution was always to move, on your screen, to where you should be.
So you dash 4 steps NorthWest but appear at your initial location on your screen. You have to walk 4 steps SouthEast from your server-side location (the real one) to your client-side location. You can then move freely.
You can, any time you get stuck. Walk (don't run) and retrace the steps you took (but did not see).The only solution i have is to re-dash, i cannot walk anywhere after the bug kicks in
Either can get stuck.Anything is fixable...
Who gets stuck? the ShoulderDasher or the ShoulderDashee?
Sam
Anything is fixable...
Who gets stuck? the ShoulderDasher or the ShoulderDashee?
Sam
You can, any time you get stuck. Walk (don't run) and retrace the steps you took (but did not see).
Always worked, both when dashing and being repulsed/running while dismounting/whatever. Easiest to figure out if you have another person seeing you on their screen, as they can tell you exactly where you are and how to retrace your steps. Tricky to do from memory.
Either can get stuck.
So this usually happens when the server and client fall out of sync, ie on the server you are 3 steps away from where your client believes you to be...
I am guessing that after a dash the server is sometimes not updating the client, the real question is why :P
Sam
Because 13 yr old poorly optimized code is my guess.So this usually happens when the server and client fall out of sync, ie on the server you are 3 steps away from where your client believes you to be...
I am guessing that after a dash the server is sometimes not updating the client, the real question is why :P
Sam
So this usually happens when the server and client fall out of sync, ie on the server you are 3 steps away from where your client believes you to be...
I am guessing that after a dash the server is sometimes not updating the client, the real question is why :P
Sam
Dude what happened to P69!It happens to both the dasher and the dashee. You need to prevent the client from sending run requests within so many ms of SM_RUSH or SM_PUSH I think I did 500. It is because the client sends a CM_RUN to out of date XY so the player actually runs backwards from the dash
What if you're one of the 4 classes with no ShoulderDash >.<When this happens, you can dash again to sync backup..
Sent from my GT-I9300 using Tapatalk
haha tough then.. though this happens more often to the dasher than the dasheeWhat if you're one of the 4 classes with no ShoulderDash >.<
I think everyone who's played Mir for more than a few months has had the bug :PDid scorpions reply help sam ? Do you need a screenshot of the bug happening ? Would be nice to get this in for the weekend reboot :k
