mojira.dev

Piper

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

MC-152604 Hardcore LAN Worlds Have Buggy Spectator Mode Duplicate

Comments

Still happening in 15w44b

The title is wrong. It still affects nether portals.

This still happens in 15w42a

...yes...what is this duplicating? There are two issues listed as related, but neither of them describe this issue at all.

Duplicate of MC-2791

I made a video showing the bug in 15w41b: https://youtu.be/r-5-ToPwDUM

This still happens in 15w41b.
It's a bigger deal now because the new Elytra is only found in an item frame in a ship which is often above void. If you don't build a massive safety net under the ship, there's no way to stop the Elytra sometimes flying through the wall, off the ship, and into the void.

Still present in 1.8.3

This issue still exists in release 1.8

Still present in 1.8-pre1, but I think this is intended. All similar blocks such as flowers and tall grass cause the same effect.

Still present in 1.8-pre1

Agreed this is not a duplicate of MC-29518.
As of 14w31a, stat.damageTaken (MC-49590) is now tracked correctly, but stat.damageDealt still ignores any armor, enchantments, etc. that the other entities have. So, if you hit another player with a wooden sword, it will count as dealing 5 hp of damage even if they had full enchanted diamond armor and received no visible damage on their screen.

This issue is no longer present in 14w31a.

Thank you, Skylinerw. I know I tried that, but I must have had a typo somewhere that stopped it from working, which was my mistake.

@Jeff I'm pretty sure you didn't read the entire bug report. How do OwnerName or OwnerUUID have anything to do with creepers? The horse thing was just one example and perhaps one that is no longer relevant.

Thanks for updating it 🙂

This issue still exists in 14w28a.

This issue still exists in 14w28a.

This issue still exists in 14w28a. Any mods around? I'm pretty sure Mojang isn't going to fix this if they don't know about it and I can't update the list of affected versions unless I am mistaken. I can't open a new report since it would immediately (and rightly) get marked as a duplicate of this one. But this report seems to be well and truly dead.

This issue still exists in 14w27b.