Player selectors fail finding player/Player is not correctly moved from the End to the Nether

Your attached screenshot is barely of use for those not speaking your language. Please attach it in english. Please also further explain the issue and provide detailed steps to reproduce it.

Sorry I'm turkish in real.

But I changed screenshot to the english one.

I can't reproduce the issue based on your description. Please provide a video of this happening and/or steps to reproduce.

A video? I can't make a video! Maybe with phone but maybe my mom don't accept it.

But it's being just sometimes. I think if I make a video, it not happens.

Might relate to

• MC-88490

• MC-88565

• MC-88575

I had something similar too, I was not able to break blocks and could not take damage after I walked into a cactus

Is this still an issue in 15w45a? If so, please explain the issue in detail and provide steps to reproduce it. Please also update the list of affected versions.

Confirmed for

• 15w49b

Relates to:

• MC-89928

• MC-59723 (probably the same bug)

How to reproduce

1. Go to the end: /setblock ~ ~ ~ end_portal

2. Go from the end to the nether: /setblock ~ ~ ~ portal

3. Try to use player selectors
   Entities in the overworld are unable to find you as well so I assume the game thinks you as entity are still in the end (maybe)
   However the NBT data of the player is correct and he can still target himself with his name

Could you please change the title to something like "Player selectors fail finding player" or "Player is not correctly moved to other dimension" (I would prefer that one as it seems to affect also spawning)

confirmed for 15w51b, sometimes after switching dimensions/jumping large distances with commands my effect commands fail

Confirmed for 16w04a (I think).

16w04a is outdated, 16w06a is the newest version

Ah yes, that again. I'm just not updating after 16w05a since after that NoAI no longer ignores the Motion tag, which is a problem in my map, and I got it by accident while updating it.

Confirmed for

• 16w06a

Please link to this comment in the description

The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.

This report might be invalid because you normally are not able to leave the end without using an end portal (or dying). However, this can be achieved pretty easily and has a rather huge effect.

The reason why this happens is because the method net.minecraft.server.management.PlayerList.transferEntityToWorld(Entity, int, WorldServer, WorldServer) only calls the net.minecraft.world.WorldServer.spawnEntityInWorld(Entity) method which updates the loaded players if the player is not coming from the end. This is done because the player gets respawned as soon as it sends a net.minecraft.network.play.client.CPacketClientStatus with the value PERFORM_RESPAWN, which is sent when the client stops watching the credits.
The problem is that if the player leaves the end using a Nether portal, he will not respawn and the loaded entities lists will not be updated.

Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.

This is an automated comment on any open or reopened issue with out-of-date affected versions.

I see this is still in issue at version 1.12. And this one had been shown off to the public now, by AntVenom. I had reported this before, but i found this is a duplicate bug that i doesn't know before.

@unknown, please say the exact version you confirmed the issue. And don't say "the latest", because the latest snapshot changes every week.

From what I know, this bug works all the way until snapshot 18w10d. It has been coined the phantom nether. i have tried it and it works. i do not know when it first started however. i guess as long as you could place portal blocks inside the end.

Oddly enough, if I use /execute as @s in minecraft:the_nether run teleport ~ ~ ~, this bug didn’t happen!

this still works in 18w50a

Confirmed in 19w02a

Confirmed on 19w08a and 19w08b

Confirmed on 19w11a

Confirmed on 1.14 Pre-Release 2

Confirmed on 1.14 Pre-Release 5

Confirmed for 1.14.1

 Confirmed in 1.14.2 Pre-Release 2.

I tested and this seems to be fixed at 20w21a.