MCPE-56765Mobs don’t drop XP at their kill location
Mobs do not drop XP at the location where they are killed and instead do it at their death location after the animation has concluded.
This can make getting XP from mobs more difficult espiccialy with Knockback. Often in servers it leaves XP orbs lingering on the ground due to a player killing a mob and not chasing it to pick it up too which is annoying and also can potentially cause lag issues.
Steps to reproduce:
- Spawn in any mob that drops XP upon death by a player.
- Kill the mob in survival
- Observe that it’s items drop where it is killed yet the XP is dropped only after it’s animation and at where it dies.
Linked Issues
Attachments1
Created Issue:
Mobs don’t drop XP at their kill location
Mobs do not drop XP at the location where they are killed and instead do it at their death location after the animation has concluded.
This can make getting XP from mobs more difficult espiccialy with Knockback often in servers leaving XP lingering on the ground due to a player killing a mob and not chasing it to pick it up.
Steps to reproduce:
- Spawn in any mob that drops XP upon death by a player.
- Kill the mob in survival
- Observe that it’s items drop where it is killed yet the XP is dropped only after it’s animation and at where it dies.
- Unresolved
- Open
- Unconfirmed
- iOS
- iPadOS 13.3
- 1.13.1
Mobs do not drop XP at the location where they are killed and instead do it at their death location after the animation has concluded.
This can make getting XP from mobs more difficult espiccialy with Knockback
often in servers leaving XPlingering on the ground due to a player killing a mob and not chasing it to pick it up.Steps to reproduce:
- Spawn in any mob that drops XP upon death by a player.
- Kill the mob in survival
- Observe that it’s items drop where it is killed yet the XP is dropped only after it’s animation and at where it dies.
Mobs do not drop XP at the location where they are killed and instead do it at their death location after the animation has concluded.
This can make getting XP from mobs more difficult espiccialy with Knockback. Often in servers it leaves XP orbs lingering on the ground due to a player killing a mob and not chasing it to pick it up too which is annoying and also can potentially cause lag issues.
Steps to reproduce:
- Spawn in any mob that drops XP upon death by a player.
- Kill the mob in survival
- Observe that it’s items drop where it is killed yet the XP is dropped only after it’s animation and at where it dies.
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
is cloned by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
This is a duplicate of MCPE-56765 but apparently duplicate reports are allowed on the MCPE tracker now.
Due to this being posted later and being a duplicate, that does mean it is missing a bunch of versions that need to be added for posterity. Such as 1.14.20 Hotfix, 1.13.3, 1.13.2, 1.13.1, 1.14.1 Hotfix, 1.14.0, and 1.14.30 Hotfix.
For more information, (including proof from over 6 MONTHS ago, proving this was a bug which the moderators here refused to acknowledge,) please visit the original report made in November of 2019. MCPE-56765
MCPE-56765was closed as WAI, so the comments about "duplicate reports being allowed" are somewhat confusing.We have no visibility into why the devs chose to close it as WAI, maybe there was a disconnect between the Java and Bedrock developers at the time but its important to note that a difference in behaviour did not qualify a report as valid (at the time). At best it would have been closed as a parity request needing to go on the feedback site.
This bug was specifically raised after a change in the rules around parity differences. The rules around parity issues being tracked here were changed on the 29th of April, more information on that change and the rules around it can be found here. Under those new rules this now qualifies as a bug regardless of the closure of
MCPE-56765.Once again please be reminded to remain respectful when using the tracker. Being disrespectful does nothing for your cause and the volunteers that pour their free time into keeping this tracker running do not deserve your scorn. Even if you think a mistake has been made.
Thank you for your report!
However, this issue has been closed as Working as Intended.
(See
MC-87634) If you need help or have a suggestion you might like to follow a link below.Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
https://youtu.be/bVQx599EtII
2:17
https://www.minecraft.net/en-us/article/minecraft-snapshot-19w46a
@slicedlime#0742 @Mega_Spud#7168
https://bugs.mojang.com/browse/MCPE-56765
https://bugs.mojang.com/browse/MC-87634
This is direct conflicting information regarding an explicitly stated feature. This is falsely closed in Java and has now been confirmed as being a permanent feature within Bedrock according to the bug tracker?
Explanation on why this is like this is needed.
i have added the response from Sliced Lime regarding the discrepancy. Taking his word first this issue should either be reopened or postponed. Either way I will not stop updating it with information including version numbers and any other stuff I come across. Hopefully the Mod team here can agree with the devs on this and rectify the ticket and eventually... lord knows when.... fix it.
This is still an issue, the video @Amphy2k showed shows how the xp drops as soon as the mob is killed, compared to old Java versions where the xp would drop only when the entity disappears, which is the same as Bedrock.
This issue is now being tracked at MCPE-74963.
Amphy2k: You were warned back in March that disparagement of Mojang, its employees, or the bug tracker staff is not acceptable here and can result in you being banned. You have made many helpful contributions here and I don't want to ban you, but these critical comments must stop or I will be forced to. Not only are these comments insulting, which naturally tends to disincline people from cooperating with you, but your analysis is sometimes shortsighted or flat wrong (as in this case) because you imagine you understand the bug tracker workflows better than you actually do. If you are open to having a discussion about why we've done something differently than you expected, that is possible, but not here: Such discussions; belong on the Mojira subreddit or the Mojira Discord. Please note that we are supervised and instructed by Mojang, so we aren't going to argue with you about how we perform our duties.
Have a look at the Resolution and the comments to see why this ticket has been resolved. If you think this ticket has been resolved erroneously you can contact the Mojira staff on Discord or Reddit.
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Updated from missing latest version.
Have a look at the Resolution and the comments to see why this ticket has been resolved. If you think this ticket has been resolved erroneously you can contact the Mojira staff on Discord or Reddit.
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Oh wait I see that it says it was cloned by. That must be new! Good to see that it was at least acknowledged that it was cloned. No need to keep this updated then so I will unwatch it. My bad.
Have a look at the Resolution and the comments to see why this ticket has been resolved. If you think this ticket has been resolved erroneously you can contact the Mojira staff on Discord or Reddit.
– I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit