Strider movement speed was increased in 20w14a, but there now appears to be a problem with how they interact with normal blocks.
Whenever you find a Strider, it's spawned with its legs sunken slightly in the lava. This allows them to have their lava-walking speed. However, when you lead them over normal blocks such as Netherrack or magma blocks, their speed decreases dramatically. This part is intentional, of course, but what isn't intentional (to my knowledge) is that when you then lead them over lava once more after walking over the ground, their speed remains the same as if they were still on the ground, and their legs do not sink back into the lava.
I've tested this using the fungus-on-a-stick item as well, using it as a boost both before and after leading the Strider onto the ground. The boost the fungus-on-a-stick gives does not give the Strider it's normal lava speed back, even after being led onto the lava again from the normal ground.
I've included a picture showing the difference between a freshly-spawned Strider (the one without the saddle), and the one I've tested this behavior with (the one I'm sitting on). As you can see, the legs of the Strider my avatar has mounted is now standing above the lava, rather than in it.
Attachments
Comments 6
Actually, this is still a thing. I was about to make another bug report about the same issue of Striders forever losing their maximum speed after leaving lava and going back in. Good thing I searched "Striders lose" at the last moment instead of just "Striders speed".
What I noticed:
When riding a (natural) Strider for the first time, they go at very fast speeds, more so when right-clicking with a Warped Fungus on a Stick. When I ride it out of the lava, they become cold, start shivering, and slow down significantly, as expected. But when I ride the Strider back into the lava, even though he does stop shivering and move faster when it's back in, it doesn't go remotely as fast as when I first rode it. Even after getting off, it never picks up the same pace as it did before going onto land. And right-clicking with a Warped Fungus on a Stick does nothing at all to affect its speed. I used F3 + I on both a Strider that has been affected by this and another who hasn't been on land yet and still retains its speed. The both have their "Generic Moving Speed" at the same value:
{Base: 0.15000000596046448d, Name: "minecraft:generic.movement_speed"}
even though one is going much faster than the other when being rode on.
I hope this can be fixed.
this happened to me in 20w16a. What was REALLY strange though, was how I mounted another strider (who remained fast), but he refused to climb on blocks. I dismounted him near the "shore" and was thrown directly into the lava 😞
Hello there! I have done some testing again in the latest snapshot (20w21a), and the issue seems to be fixed. I first found a naturally-spawned Strider and tested its movement speed on land and on the lava without the speed boost from the fungi-on-a-stick item, and then again with the speed boost. I also tested a Strider spawned with an egg just to be sure, and finally, I did both tests in both creative and survival.
All four tests yielded the same result, as far as I could tell: the movement speed bug appears to be fixed now, and the visual glitch that came with it (the Strider floating a little higher in the lava than it normally should after leaving the land). They not only retained their normal speed once they got back into the lava, but they also retained the speed boost as well if they had eaten from the fungi before walking onto land.
Thank you so much for fixing this bug. 🙂
UPDATE:
I have tested this on 20w15a again, and somehow the issue was fixed, at least based on my tests (same setup, same method of testing, different results). I'm not sure if the fix was a result of some other bug being fixed or if it was an intentional fix for the original behavior, but Striders now get their regular lava speed back even after they walk over normal blocks.
If any moderator, helper, or Mojang employee sees this, would this be grounds to mark this bug as "resolved", or is further testing required, just to be sure? This is my first bug report so I'm not sure how to contact anyone important.