When trying to sprint (Either by Double Tapping "W" and or Holding "CTRL"+"W") it sprints for a Millisecond-15 Seconds then stops to a walk.
I have seen other posts saying it was "Resolved" but after running in to it in the current state of the game its obvious IT IS NOT!
Would send video of example, but the Limit is 10 Mb and have not found a way to compress it that much, and still have good enough quality to see whats going on.
Linked issues
Comments 7
Since I sprint while dig-building, I've noticed this too. I ask myself, if I'm sprinting, why am I digging at a near walking pace?
https://youtu.be/li7WRYph7gE
EDIT: Happens in tunnels, above ground and any time I play (Online/Offline).
This doesn't just happen in the where I was in the video is what I am trying to say.
From the description of https://www.youtube.com/watch?v=DECKDy8gu1Y:
In 1.13.2, collidedHorizontally is randomly set to true due to floating point inaccuracies when your position is very close to a integer or half integer. This makes sprinting stop. Thanks mojang. So we can't walk at exactly +0.50000 on blocks, we need to randomize a bit. I found that 2° of range (±1°) randomly applied every tick is good enough. In this video it was 1° of range (aka ±0.5°) which is why it stopped sprinting for a tick a handful of times. You can see in the video that when I set randomlooking to 0, the Z coordinate quickly settles on 0.500, then sprinting stops. When it goes back to 1, the Z coordinate moves around 0.500, which lets sprinting continue. Also it's less detectable overall tbh. (randomlooking 10 was an exaggeration dont ever do that lol)
In short: In Minecraft 1.13.2, you can't sprint while being exactly in the middle or on the edge of a block for more than a few ticks due to some floating-point errors. This is despite not actually colliding with any non-floor blocks.
Which ticket are you talking about?