The video was too large to be uploaded. The link is below.
What I expected to happen was:
Jumping out of a boat would cause non glitching issues
What actually happened was:
Jumping out of a boat in natural and nonnatural water while it is still moving will cause you to glitch into the boat, if you jump back into the water and jump back onto boat a different boat in water, it will also bug you out as well. Quitting the game and reloading will still have the glitch.
Steps to Reproduce:
Place several boats on land.
Place several boats in water,
Get into one of the boats floating in water
Travel in the boat.
Jump out while it is still moving.
Move off the boat and stand onto another boat on water.
Jump off that one and jump onto a boat on land (nothing should happen).
Place a new boat in water or land and jump onto it (nothing should happen).
Notes:
1. The same thing will happen temporarily when moving in a boat on land when standing on the edge of the boat.
2. This affects all types of boat.
Environment
Java Edition in 1.14.4 in a flatland or naturally generated world.
Gamerules:
announceAdvancements=true
commandBlockOutput=true
disableElytraMovementCheck=false
disableRaids=false
doDaylightCycle=true
doEntityDrops=true
doFireTick=true
doLimitedCrafting=false
doMobLoot=true
doMobSpawning=true
doTileDrops=true
doWeatherCycle=true
keepInventory=false
logAdminCommands=true
maxCommandChainLength=65536
maxEntityCramming=24
mobGriefing=true
naturalRegeneration=true
randomTickSpeed=3
reducedDebugInfo=false
sendCommandFeedback=true
showDeathMessages=true
spawnRadius=10
spectatorsGenerateChunks=true
Linked issues
duplicates 1
Comments 2
Thank you for your report!
We're actually already tracking this issue in MC-156980, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
A previous version resolved this issue, however, has returned into the game (MC-154316).