The bug
If you log off while you are mounted on a Strider that is currently in the lava (even though you are not) and log back on, you are lit on fire instantly while riding the strider. After 1-2 seconds, you start taking burning damage from the fire.
This happens in Survival, Creative, and Adventure, but the player is only on fire for a tick when logging in Creative, similarly to when a player dips in lava.
This bug also affects non-fire resistant entities riding on Striders.
Examples
Here are examples in videos:
Linked issues
is duplicated by 7
Attachments
Comments 10
Nice! That needs to be fixed before release 1.16, and it will be, I'm sure
2 hours later: 1.16 RC releases with no fix
😞
I believe the cause of this is, when a player logs on, they spawn at the exact same xyz coordinate as the strider (which is in the lava) for a very small tick before mounting the player on the strider. That's why the player is burning for 20 seconds as if they were in lava for a short time. I hope this insight helps.
Will you all please only comment if you have something new and helpful to say? Confirming it for the exact same MC version twice does not help. And 2 hours is an absolutely unreasonable time for a bug to fixed, especially since this was only noticed late yesterday.
How long does it burn for
20 seconds
how much health does it take
Depends on difficulty, status effects, ect.
Difficulty doesn't affect burning damage.
What happens is that you don't get any damage for a couple of seconds, which applies to all damage. You have always been able to exploit it to get no fire damage whatsoever. I've reported that (MC-160051), since I feel it is not intended you can avoid all fire damage in both singleplayer and multiplayer.
A workaround for this bug is therefore to keep re-logging until the fire stops. The reason this works is because the fire timer keeps playing, even when the join resistance is active.
It is concerning, though, if MC-98727 includes striders. That would mean re-joining while on a strider is more common.
Duplicate of MC-177275?
Nice! That needs to be fixed before release 1.16, and it will be, I'm sure