mojira.dev

Desko

Assigned

No issues.

Reported

MCPE-83955 Redstone dust does not have a dot state Confirmed MCPE-79808 Patrol and trader spawns that "succeed" in invalid biomes are delayed, rather than cancelled Fixed MCPE-78451 Villagers repeatedly spam doors open and shut Duplicate MCPE-76182 Coral uses stone sounds Confirmed MCPE-74963 Experience orbs don't drop instantly on death Confirmed MCPE-40651 Protection enchantment doesn't provide extra defense against magic attacks Fixed

Comments

Still affects all current versions.

Thanks for fixing that up Auldrick, I'll be sure to keep that in mind with any future reports I do. Hopefully I'll be able to actively maintain these again soon.

As for Josiah's remark, this is still valid for the issue tracker as it falls into the limited criteria for parity issues as established earlier this year as the parity break was introduced with the Buzzy Bees update.

Per MC-97106 and MC-10929, this isn't. Protection is intended to protect against all forms of damage except hunger and void damage, and that includes potion/magic effects as well as, surprisingly, drowning and suffocation damage. I believe the latter two work on Bedrock since it's saved me on a few occasions, but I'll have to check again since I could be experiencing the mandela effect.

Affects 1.16.1 and 1.16.2-pre1.

Also, slight correction. It was release 1.3, not Beta 1.3.

An easy, albeit imperfect fix for this is hilariously simple: in skeleton.entity.json, move line 58 ("skeleton_attack" in animation controllers) up above line 55 ("bow_and_arrow"). This fixes the bow aiming animation to match strays' without breaking the melee attack animation.

If you OPENED the treasure chest and didn't get a popup for the achievement, check in the menus just to make sure. You won't get a popup unless you have the Xbox app installed, as far as I'm aware.

Hi, I'm the host of the server. I've attempted to find a solution to the issue, and as stated before I initially had a theory that the issue was caused by or related to MCPE-44815, but this doesn't seem to be the case. To bullet point the issues out:

  • Nobody else has had problems connecting to the server.

  • This seems to affect him no matter what device he tries to use, and only on this server.

  • I have tried restarting the server software, the entire server itself as well as unplugging the cable, restarting the router its connected to, among other methods, to no avail.

  • Strangely, the server seems to detect his connection and disconnects and logs both, while the broadcasted chat only announces his disconnection, leading to every attempt printing the message "wayyykewlkidjmk has left the game" to all connected players.

Because of this, I'm starting to think the issues have to do with the save itself, but that still makes the issue incredibly baffling. The server hasn't had any sort of crashes or errors since his last successful connection just before the issues started (and I know exactly when that happened as I was one of the players there at the time), so if the save is the cause, it'd have to have been caused by some sort of auto-save issue.

Voted for this. It doesn't affect my laptop's CPU as heavily but it's worth voting for nonetheless as it's clear that this is a huge issue for players with Intel
and ARM-based CPUs where it seems to be hitting the hardest.

Keep in mind, if you are using an add-on such as a resource pack or behavior pack, or have used one on the world, that's most likely the cause. The game will fall back to the old pigmen models if the resource pack hasn't been updated to fully support 1.16. Try temporarily removing the pack to see if that fixes it.

Can you send a copy of the skin?

Due to another bug that's already been reported on the tracker, villagers can despawn when crossing chunk borders. The only way to prevent that is to block off any access to said borders, or they'll despawn.

In addition to being posted in the wrong project this is working as intended.

I don't know if they completely patched it, as duplication exploits are considered to be security issues and are required to be made private on the issue tracker, but all evidence points to it being completely patched. This seems to be due to under-the-hood reworking of piston mechanics to fix some of their more severe issues. It IS fixed, as the old behavior was the bug, and a severe one at that.

Can't reproduce on 1.16.0.

I've had this happen before on 1.14. Have you tried walking away from it from a little bit? You don't need to unload the chunk.

The issue here doesn't seem to be that the layer isn't generating at all, but rather, it's generating in the wrong place. Mine up to y=~125 and you'll see what I mean.

Sending a world will also work, since that can be more easily checked for dark spots.

Piglins aren't supposed to be afraid of warped mushrooms, that's the Hoglin's thing. What they ARE supposed to be afraid of are zombified piglins and soul fire.

AMD A12-9720P, with settings mostly maxed out on my PC CPU usage is 30%, which is mostly normal. Might just affect certain CPUs.