Terrible Stutter Stepping [Alcor]

[Xvelocity]

I am using AlcorCombat and AlcorPlayerMovement. The common problem I seem to see for stutter stepping is having abilities bound to the mouse. I currently have nothing bound to the mouse except for default attack on mouse1. All movement and abilities are on the bottom row of five buttons all bound to regular keyboard keys. I am not using any movement ability (like Leap Slam, Whirling Blades) in my build.

My networking mode is set to Predictive. And my FPS stays above 40 with a ping constantly below 70. I did not have this issue until today. However for full information sake, I did switch to Kinetic Blast and had this problem start. Below is a small log snippet of what is being output during this stutter stepping.

[UseAt] Move 6 False {1557, 332} => None
[InjectKeyEvent] 176 ms sleep for 69.
[UseAt] Move 6 False {1560, 316} => None
[InjectKeyEvent] 182 ms sleep for 69.
[UseAt] Move 6 False {1554, 335} => None
[InjectKeyEvent] 173 ms sleep for 69.
[UseAt] Move 6 False {1556, 321} => None
[InjectKeyEvent] 188 ms sleep for 69.
[UseAt] Move 6 False {1552, 343} => None
[InjectKeyEvent] 169 ms sleep for 69.

Edit: I removed Kinetic Blast entirely and the problem persisted. I double checked my network connection through two speedtest sites and there seems to be no issue. I killed all other processes (not in VM or anything) on my PC. The issue persists.

 

[pushedx]

Using only 'UseAt' to move will result in stutter stepping as you cannot spam skills that way in this game without triggering a DC, which is why there are sleeps to prevent that in Input.

Instead, the logic you're using to move should be using BeginUseAt, and then move the cursor to keep the player going. This allows EB to make the client move as fast and smoothly as possible and avoids the DC issues 99% of the time (the 1% it doesn't is when bot gets stuck on terrain and the input actions end up spamming because of client issues)

OldPlayerMover, while it only uses the move skill, shows how this is done, but things have been this way for years now, so you're either using old code, or the movement skill logic for the skill you're using wasn't ever updated. There's no reason you'd start having issues now and not have them before really, nothing changed on EB's end.

Keep in mind that using skills to move, while certainly beneficial for clear speeds, can result in all sorts of side effects in this game. I don't know if you saw the leap slam crashes over empty floor, or the WB stuck in stairs and walls, but there are problems with the game itself to be aware of.