AceMcCrank

From what I can gather, this looks like a separate error. Launcher logs show no lines referring to “entitlement” warnings.

Yes, the same error appears in terminal, but it does so four times in a row instead of once, and the launcher does actually launch every time - it just doesn’t continue after initial additional login window has gone through successfully, until the launcher’s process has been terminated, at which time it will be successful during the second attempt.

So far, not for our server.  Instead it's been replaced with "Watching Server" when we updated.

One of our servers just can with this error, but not 100% sure if it is related. A torch had taken the properties of a hopper, and a white concrete block below it had taken the properties of a trapped chest. Because this was on server, it was rejecting everyone's connections. It would load in singleplayer, but I had replaced the blocks with air blocks from console, this did not fix the issue and still go the same errors.

The corruption had gone well past this however, as you can see from this screenshot.

Several chunks were reset on a custom map, and existing chunks were shifted and in wrong places. The diagonal line of concrete shows the blocks that were replaced by air blocks by command in console to try and fix it.

This happened again on our server. The world file is 9.32 GB, so I think it may be an error that occurs in large worlds?

As far as we are able to figure out on our server, this seems to also be the mob farm that is causing MC-158466 as both only occur while the same chunk or chunks are loaded, but we are unable to fully confirm.

Still affecting 1.15.1

We had three of these crashes today.

We can't seem to pin it down to any specific player or object. We are running the vanilla 1.14.4 JAR, 16 GB on a hosted dedicated server.

Even if the outpost spawns above Y=63, the Pillagers still will not spawn.

After extensive testing I can confirm: Wandering Traders also do not spawn in the world.

Edit: Figures, after 2 months of not seeing a single one, one finally shows up for all of about 2 minutes before yeeting himself off a cliff into the void.

To add to this (I feel a change should be made to this ticket to reflect all of these):

Guardians do not spawn in the Monuments.
Witches do not spawn in Witch Huts (Except for the initial witch)
Pillager Outposts will not spawn any Pillagers
No Village stray cats will spawn. The only way to obtain a cat is the first cat spawn in a witch hut. I also attempted to get them to spawn in The End and Nether. Nothing.

So, we have a TON of farms broken with Buffet mode.

This is affecting our server. I'm going to have to look at alternative options for the sake of getting drops from Guardians, as well as Witches and Pillagers. They are all related.

I came across the same error, unsure if related.

And yes, the server is vanilla. downloaded straight from the launcher.

Well, I submitted the help ticket to the helpdesk for Technical Support as was recommended on June 18 (And this Report was edited to reflect that one should do this, but now has been changed again). I was informed by "Fredrik" that there is no Technical Support Team. This was 2 days ago. It took a month and a half to get that answer, which I guess prompted the change on this ticket.

Oh, View Distance is 14.

So... I didn't get a jump up to 2k but there are still periods where it will spike up.
1600 rx

down to 320 rx

up to 1000 rx

up to 1600 rx again

Mind you, this is just loading the world and just sitting there doing nothing. Imagine if I had a house, a farm, maybe some redstone. If this were a server somewhere, there would be the possibility of bufferbloat from these random spikes in data, causing the data to stop transferring. This could be at the server, at the client, or at one of the possibly thousands of nodes in between. And then you have this data multiplied by the number of players on the server. Often it will feel like I'm not playing Minecraft; instead I'm playing Connect To A Minecraft Server.

Yes, it was a brand new world. Seed: 853413651320

I'll keep things updated when I get a chance later tonight to see if it happens with 1.14.4 and see if I can't run the debug.

1.14.4 Pre-7 is even worse now. Loaded world, waited a few minutes, and over 2K rx?

I literally did nothing but stand there. Started around 700, jumped around a bit. This is really bad for people on metered connections, server owners and hosting companies that share connections with other servers, anyone with a slow connection (read: the entirety of the rural US) or even moderate connections. This is the primary reason for issues like MC-38565, because this high amount of data can cause bufferbloat issues at either end.

If that is the case, then the bug would be in Windows 10 Edition, as it reacts the way I expected - causing multiple Villager Types in villages that cross biomes (You can see this in ibxtoycat's recent Seed Sunday video). Also, all references I've been able to find in the announcements imply that the Villagers are supposed to be biome-dependent, not Village-origin-dependent.

But see, this is why I think there is a possibility that this may be related to MC-140926. In Java, Villages were spawning with only the default Plains skin instead of the biome. I'm curious if, because of the fix, the Villagers may have been hardcoded to the Village generation. Just a guess, without actually having access to or at least knowing how to access the code. Bedrock never had this issue, so Villagers, when generated, will always be of the Biome they spawned in when playing on Bedrock.

I've noticed that if I keep my F3 screen up, I can actually watch as the server just stops sending information to the client. I could be chatting on Discord at the same time, no difference in quality, I could be listening to music or have a video going on with no issue, or sometimes not doing anything else at all on my PC. I've tested my connection, I have 120+Mbps down, 100+Mbps down, no dropped packets, decent ping. Our server, which is vanilla, will just randomly stop sending information to players. The rx will drop down, from anywhere down to 2-0, before getting the error. And this is much more frequent with 1.14+, but it started becoming a real issue in 1.13 for us.

Merging books is done with the anvil. The grindstone is for repairing two tools together or disenchanting.

Confirmed for 1.14.2.

What I noticed about the behavior was that the zombie pigman that aggro'd toward the skeleton did NOT aggro toward me, but rather any other surrounding pigmen did. The initial pigmen struck would not engage until I as a player struck another pigman.