When a thrown ender pearl is in the air, it disappears after relogging and you don't get teleported.

THANK YOU SEARGE <3 I Ruv you much ^^ I almost thought I'd have to give up on the most important project I've ever started, but you saved it. ;D

Does this fix affect MC-11659 also?

@@unknown: Most probably not, because MC-11659 is about the fact that eggs don't serialize.

This happens in 1.8.2?

This happens in 1.10 on multiplayer (Realms at least).
Video

Anybody else able to reproduce in 1.10?

Yes.
The code kills the ender pearl if its shooter is logged out.
I guess the bug would be that the chunks are not unloaded the instant the player logs out (which would be very hard to fix).

@unknown the method net.minecraft.entity.item.EntityEnderPearl.onUpdate() only kills the ender pearl if the player is dead and logging out does not set the player as dead, does it?

That dead flag meand entity is not in the world anymore,

Are you sure? For me the ender pearl was there after relogging, but I haven't tested it with throwing the ender pearl in unloaded chunks.

@@unknown See net.minecraft.server.management.PlayerList.playerLoggedOut(), which calls net.minecraft.world.World.removeEntity() (which marks the player as "dead"). This isn't an issue in singleplayer because the server is stopped immediately, preventing the ender pearl from being ticked again. I can confirm that it happens in chunks that remain loaded after the player logs out of a multiplayer server, as the pearl gets ticked again, and I cannot replicate it in chunks that are unloaded when the player logs out (i.e. the pearl remains).

also ender pears being thrown often kill em as a player.. 'hit the ground to hard' due to velocity of ender pearl .
should be a safe landing.. if a block under you or ender pearl is lost but spawns a slab under you if it hits the side of a wall ?

@unknown please submit suggestions to /r/MinecraftSuggestions. This bug tacker is for bugs only.

Confirmed for 17w06a.
Video

Here is a download link for a Structure Demonstration (load with entities on, multiplayer or LAN only).

Confirmed for 17w16b using the structure I created and linked in my previous comment.

Confirmed for 17w18a, using the structure I created and linked in my previous comment, relative to my previous comment.

Confirmed for 1.12-pre2, using the structure I created and linked in my previous comment, relative to my previous comment, relative to my previous comment.

Still happens on 1.12.
As md_5 pointed out, the net.minecraft.entity.item.EntityEnderPearl.onUpdate() method kills the entity if the thrower is "dead", meaning not in the world any more.
To fix this issue, I have removed said check, which makes the pearl stay, but renders it defunct if the player left the game.

In net.minecraft.entity.projectile.EntityThrowable, I have changed the meaning of throwerName to be the UUID of the player. The field is only used if the thrower is a player, anyway.
In getThrower(), I replaced the getEntityFromUuid logic, to get from player UUID instead.
In writeEntityToNBT and readEntityFromNBT, I made it default to the thrower's profile UUID if throwerName is null or empty.
Finally, I also made it put the thrower's UUIDS in throwerName in the constructor, so it should in theory always be available.

This seems to work quite well on our server, though I've only done some preliminary testing. Logging out when the pearl is loaded works fine, as well as when the pearl is in an unloaded chunk.
It also survived a server restart and the pearl was fully functional after each of these.

This is a fairly easy fix, so... this way or some other way, but can we get an official fix for this? Please?

(I decompiled MC with MCP 9.40 for MC 1.12)

This bug happens on 18w15a. If you wish to test it, you'll have to import the structure in a 1.12 world and move that world to the snapshot.

Affects 1.13-pre1.

Affects 1.13-pre2.

It appears the bug was recently closed as WAI and then reopened. While I don't want to disrespect the decision process, this gave me some motivation to list a reason here on the bug tracker that I had discussed with someone the other day about why I feel this bug really matters.

Presumably the only reason this bug exists is the fix of MC-50848. While that fix was welcome, even if arguably unnecessary for most scenarios, it introduces quite strange behavior when the life of the ender pearl is extended (which is very much a possibility even in Vanilla).

When an ender pearl is freshly thrown by a player with the intent of teleporting to where it hits in a few seconds, it can be regarded as a "temporary entity." If only viewed in this context, I could perhaps agree that it's undesirable for the pearl to work properly upon death. The cases that the pearl would be deleted from the world are fairly obvious. When the player dies in either singleplayer or multiplayer, the recently thrown pearl is deleted. Arguably, logging out qualifying as this is not the biggest issue either, assuming the "temporary entity" thing.

Before I move on, I wanted to introduce the possibility of comparing the ender pearl in this "temporary entity" context to other true temporary entities. Arrows, primed TNT, etc. do not get deleted upon death. I recognize that fireballs do, but that's a property of that subcategory as a whole. Though this is besides my primary point, perhaps the easiest fix would be to declare MC-50848 as WAI because the behavior of ender pearls described there actually fits in with the behavior of other temporary entities?--

Back to my main discussion: Extending the life of an ender pearl is fairly easy to do using redstone. And it's something Mojang appeared to support by fixing this bug in the past (before being reopened due to fix of MC-50848). If they wanted to, they could add a death timer to the ender pearl and drop support for ender pearl stasis chambers, but they did not.

So we have a case where ender pearl stasis is supported, yet logic upon death/logout is treated like a temporary entity. This logic has further negative implications. If the ender pearl is contained in an unloaded chunk, the ender pearl will be unaffected by the "temporary entity" logic, which was made with the assumption that the ender pearl would land before the chunk it was contained within was unloaded.

This causes the potential for strange inconsistencies in multiplayer. For example, normally a certain row of teleporters shared by a few players at the gate of their mansion is unloaded, as it's far enough from the mansion's living quarters. Normally, when a resident of the mansion logs out, the logic meant to kill the ender pearl does not happen. Even if the resident is killed, this logic does not occur! Only when a visitor is walking to the mansion or if one of the residents comes out of the teleporter might the logout or death event of another resident cause an ender pearl to disappear.

The reason this is so bad is because it exposes the effect of chunk loading and unloading to the user. Most of the systems in the game are made to avoid this. Mob spawners only work in close proximity of the player to avoid unreasonable expectations when the player goes far away. Mob spawning in general is centered in a spherical radius around the player, also to avoid unreasonable expectations. Even redstone tries to work fine across chunk boundaries. A line of redstone that goes through chunks is meant to work (if finished before autosave), therefore it loads chunks when needed.

This makes the disappearance of ender pearls whose lifetimes have been artificially extended by a player inconsistent with the behavior of so many other systems in the game with regard to chunks. I am not proposing to load chunks at every ender pearl in the world, rather I am simply proposing to somehow differentiate between a "temporary" ender pearl and a "permanent" ender pearl.

A fix could perhaps be done by adding a timer that counts down from the maximum time it would take an ender pearl to reach the ground with no special circumstances (and this timer would count down more slowly when the pearl is within water). I really don't think the fix needs to be too complex. In a normal PvP scenario described by MC-50848, a player does not have access to, for example, a TNT cannon or an ender pearl stasis chamber to artifically extend the lifetime of the pearl. Even if the player did, the way the ender pearl would end up landing would most likely be inconvenient for them. Therefore, the timer only needs to be short enough to weed out an "ordinary" and "temporary" ender pearl that potentially passes through water before marking it as "persistent."

An alternative fix: detect "combat" and spread this status to ender pearls thrown during combat, and use the current "temporary entity" logic to delete the ender pearls thrown in combat. This seems harder than using a timer, but may or may not be a cleaner fix.

Affects 1.13-pre4.

Seems to be fixed in 18w30b. Can anyone else confirm?

Just tested it on 18w30b, still broken for me