mojira.dev
MCPE-135273

Player name appears in wrong place after respawn

Whenever a player dies there is a chance that he will respawn with his name under his chest or legs, for some reason when this happens it also affects pvp, because it doesn't let you hit that player correctly, for example if his name appears under his legs and I try to hit him in his chest or head it doeasn't let me and I also have to be like really near him for some reason.

Steps to reproduce:
1 Have a decent amount of lag and play on Xbox one
2 Kill the player multiple times until his name doesn’t appear in the correct position

Observed results:
It doesn’t allow you to hit the player (with the bug) in the normal hitbox

Expected results:
It shouldn’t happen, when you kill a player this nametag displacement and the weird hitbox shouldn’t occure

In-game temporary solution:
1. Do the swimming animation in water (this will for some reason reestablish the hitbox and the name issue in-game, but can still happen after that player dies).
2. Sometimes by login out and login in this bug can be fixed temporarly.
3. If that player sleeps in a bed It will reestablish the gamertag once It gets out of the bed.
4. If that player glides with an elytra It will also reestablish the gamertag.

Methods that still affect players (that have the gamertag in incorrect position) in pvp:
1. You can still shoot players with any type of proyectile for some reason
2. You can still light them on fire
3. They can still be damaged by lava, tnt and mobs (and also players but you will have to aim at very weird and random spots to damage the other player)

Methods that DON'T affect players (that have the gamertag in incorrect position) in pvp:
1. If you try punching him, you will have to try to hit him in a certain angle/position so you can actually hit him for some reason (however this isn't the same case when you try hiting them with proyectiles)

This is an example of how it looks like:

Linked issues

Attachments

Comments 13

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Could you please provide more details or/and media files. As such we have no repro of this issue. Is this still an issue in the latest version (1.17.11)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).

Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

This issue still affecting 1.17.11

Probably the same underlying bug as MCPE-118539.

Maybe It's related in some way

Looking at this report again, it is probably the same issue as MCPE-109925.

3 more comments

Affects 1.18 and still very annoying

Can't this be your texture pack / resource pack problem? The problem will disappear if you disable them?
And the problem occurs in the ordinary world or on the server?

Hello!, This problem only occures in worlds, and NO, I'm not using any texture packs at all and It still happens but I must say that texture packs or certain addons may make this bug more frequent (also wifi connection)

Confirmed in 1.18.20.27 Beta.

Steps to Reproduce:

  1. Create a multiplayer world

  2. Have a second player join the world

  3. Kill Player 2

  4. Have Player 2 press the "Main Menu" button on the death screen

  5. Have Player 2 rejoin the world

Player 2's hitbox and name will now be displaced.

Video:

[media]

The video only shows the incorrect hitbox.

I didn't know this could be reproduced like this!, Thank you for helping me with this bug OcelotOnesie!

Vendetta

(Unassigned)

725003

Confirmed

Multiple

Xbox one

1.18.20.27 Beta, 1.17.10, 1.17.41 Hotfix, 1.18.0, 1.18.2 Hotfix, 1.18.12 Hotfix, 1.19.22 Hotfix

Retrieved