flashteens

I have created a new bug report with much simpler reproducing steps, which can lead to the same problem without involving any commands or datapacks.

Here's the link for the new bug report: https://bugs.mojang.com/browse/MC-176240

If the new bug is confirmed, please help me mark this old bug report as a "duplicate". Thanks. 🙂

Attached the debug report using the command "/debug report".

The source map for reproducing this bug is available on my Google Drive:
https://drive.google.com/open?id=1W3C3VppoR1WN-ksif-raRWqqu_TcBAch

Thanks for your demonstration. It's indeed the condition that I encountered as well. 🙂

I'm one of his coworkers on Minecraft map projects. Let me add some comments to the description:

1. The command he mentioned above should be revised as:
execute as @e[type=minecart,limit=1,sort=nearest] at @s positioned ~ ~ ~ run tp @s ~ ~ ~1
and he intended to run this command every tick (i.e. 20 times a second), so the minecart is expected to run at a speed of 20 m/s.

2. For some low-end computers, such scenario may easily cause chunk loader to work incorrectly, and it could also freeze the map and prevent the player from getting off the minecart. If the minecart were teleported even faster (say 5 block per tick, or 100 m/s), then most computers may have this issue as well.

3. This issue only occurs on version 1.14.x (including 1.14.4), while we didn't find the same scenario on 1.13.2 or earlier versions.

Thanks for the correction. I didn't know that the attribute was technically renamed. Sorry for that.