[MCPE-122780] Dying/taking fall damage while teleporting

Summary:
I die/take fall damage when I teleported.

Steps to Reproduce:
1. Teleport yourself to coordinates

Observed Results:
I die or take fall damage when I teleported.

Expected Results:
I would not die or take fall damage when I teleported.

Notes: This is a partial repost of MCPE-105490. None of the linked reports there were helpful.

This does work with both command blocks and direct /tp command.

Comments

migrated 2021-04-02T02:26:51Z

Can confirm this happened to me when teleporting using command blocks.

migrated 2021-04-02T14:07:06Z

I also continue to experience death from fall damage when teleporting. This has happened both from direct tp command and via use of command block.

The only exception that I've found so far is when teleporting to coordinates 1, 1, 1.

jigarbov 2021-04-06T02:50:31Z

This occurs in Marketplace content as well. This causes problems with game logic and player control. Happens more often in multiplayer than single player, but can occur in single player too. Seems to happen when there is a player isn't in perfect sync with the local server.

Can confirm this also occurs on Win10

migrated 2021-04-07T02:30:30Z

Please verify if this still occurs in the latest update, 1.16.220.

migrated 2021-04-07T04:29:26Z

Its behavior is like ender pearls, but i think its a glitch because it happened in me too

osfanbuff63 2021-04-07T11:32:11Z

Ramon Bong Fernandez was this in 1.16.220? I was unable to reproduce it then.

migrated 2021-04-15T14:23:12Z

I have no repro for this issue. Every time I got any damage it was either from a fall or from suffocation. Or some mob started attacking. Or I landed in lava.
Are you sure it's not the above that cause your damage when teleporting?

migrated 2021-04-16T06:51:20Z

This may have been indirectly fixed as a result of the "movement prediction improvements" in 1.16.220.50 beta.
That may have also reduced fall damage in MCPE-112621, and fixed MCPE-109937.
However, MCPE-120140 and MCPE-120277 are not fixed.

osfanbuff63 2021-04-16T23:14:16Z

I think this has been fixed in 1.16.220/1.16.220.50 beta, since I was unable to reproduce it and (as Skaijie noted above) the changelog noted something that could have fixed this bug.

Please resolve this as "Fixed" with the fix version(s) being 1.16.220 and/or 1.16.220.50 beta.