E

This isn't caused strictly by allays. Flying entities like bees, allays, swimming mobs and modded armor stands can cause your game to crash because of pathfinding problems. See MC-250321

Same here. Happened first on an Aternos server with some armor stand. When I exported the world back into single player, it blamed it on allays. I'm not sure if armor stands have pathfinding, but fix this ASAP anyways, I've put too much effort into that world for it to go to waste.

IMPORTANT

—

Issue has been persistent since 17w43a, the first Snapshot after 1.12.2 (First Snapshot of 1.13). This is the version LWJGL has been updated from 2.9.4-nightly to V3.1.2, which has most likely caused the issue. Probably not in Mojangs hands sadly.

Example Video: https://youtu.be/tbFobTxc-lk

also it happends on all versions

I'd also like to note that the same problem affects Armorers; it isn't unique to Butchers.

I haven't noticed it to be one. But MC-153732 seems to have taken its place, as it does all sorts of wacky things to villagers' daily schedules.

Also, the top face is backwards, and the looms that were previously in my world were turned backward.

Sorry, I searched for a glitch like this and I didn't find one. Ok then.

If you look closely, there are MC-139749 air blocks surrounding the pond in the middle. It looks like the pond overrides the outpost structure.

Confirmed for 19w11b

Yeah, it's intended to be them "sweating" when a raid is approaching. Make sure that you don't have a "Bad Omen" condition of any sort, or that there isn't an army of Pillagers nearby.

Yeah, this is a new feature, not a bug. It makes TNT a much more effective mining tool, given that it drops items for all blocks destroyed--- making sure that you don't accidentally blow up gold or diamonds with no reward.

This issue also occurs on Windows when the computer has multiple active network interfaces. Minecraft chooses the interface with the highest priority (a.k.a. lowest metric). There are tools to change interface priorities, but the game should offer a list of interfaces to bind to. Non-technical users are stuck and must use "direct connect" which is not as easy as discovery.

I also just discovered that all my achievements had been reset....? Nani?

If it means anything, I changed my skin just now before logging on. I doubt it has anything to do with it, though. I have not relogged to test if it stays messed-up.

Also, I measured it, and yes it is 16x16. Confirmed one chunk. I have absolutely no clue how or why this happened--- it wasn't there before.

VIPRE. Yes. Here's the scan report for one of them. (Apparently there are more than I thought.)

On Jul 26, 2014, at 7:00 PM, [Mod] Kumasasa (JIRA) <[email protected]> wrote:

>
> [Mod] Kumasasa resolved an issue as Incomplete
>
> Incomplete without a crash report from (minecraft/crash-reports/crash-<DATE>-client.txt). Please attach it so that we can diagnose your issue.
> Minecraft / MC-63910
> Snapshot
> Change By: [Mod] Kumasasa
> Resolution: Incomplete
> Status: Open Resolved
>
> Add Comment
>
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
>

I don't understand how this is marked as invalid. There is an nbt tag built into falling sand entities to allow it to morph into any block id when it reaches the ground. There is a bug causing falling sand with its nbt tags set to tile id 36 to crash upon reaching the ground. You cannot argue that using mcedit invalidates this issue because of the fact that it is a vanilla feature that you can access with an nbt editor. Not only that, but with the release of the 13w36a /summon command, you are able to replicate this issue without needing any external editors. Just by typing the command: /summon FallingSand ~ ~5 ~ {Tile:36,Time:60}