mrfloris

Staying inactive in the chat for over 2 minutes will reproduce this, i stand in front of smoke and after two minutes when i type you can clearly see the freeze up. 

I tried 1.18.0 and 1.18.1 with the 1.18.1 vanilla client, no mods, default profile.  no mods. 

same on spigot and paper - here's a recording of it on spigot 1.18.0 with 1.18.1 client. 

https://www.youtube.com/watch?v=XJGAgzWS8fY

We've had players on SMP report back that they have named them and everything and that they disappeared, I've kept an eye on it. They die from cacti, berries, dehydration. Some designs of rivers, fishing docks etc - if there's not a full block involved they tend to get stuck on them or something and instead of getting onto land and going back into the water, they run into the dangerous stuff, or get stuff under a fence gate or on a lillypad that's next to a fence post. stuff like that. 

```

Named entity Axolotl['Buck'/136092, uuid='3feb1242-a6ba-4ea3-9c27-22d80b1f4654', l='ServerLevel[oneblock]', x=-7971.54, y=80.00, z=-6406.88, cpos=[-499, -401], tl=1809514, v=true, rR=null] died: Buck died from dehydration

```

I usually find a reason in console as to why they've disappeared. 

I was secretly hoping this would be resolved in 1.17.1 but it seems to still be the case in 1.17.0 and 1.17.1pre1.

Going back to 1.12 for example on 1.17 server and using this scrolling feels so much better. I really hope that Mojang reconsiders finding a resolve for this. It works perfectly find in 1.12 with no OS side-effects, and when you hang over the edge of something with death below you, having to completely stop what you're doing to stand 'safe' and then scroll and then continue .. it interferes with gameplay to be honest. 

Being underwater in 1.17 + datapack and future 1.18 with the new caves and heigh updates, i really don't want the unfair advantage that other operating systems have for being able to properly use the wheelmouse/hotbar combo vs me risking my death. 

Thank you Mojang for hopefully reconsidering. 

I saw the 50 minute slicedlime video on youtube, it says that goats drop exp, not items. 

Without --forceUpgrade in 1.16.2 this still occurs, without logging into the server. 

From 1.15.2 upgraded maps as well as 1.16.1 freshly created maps 

https://pastebin.com/jbPZ46GT

Converted over 125 worlds so far, and almost every 6th world has this come up. It's a consistent issue.

[15:03:46] [Server thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[15:03:47] [Server thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:spawner
[15:03:47] [Server thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:spawner
[15:03:47] [Server thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:spawner
[15:03:47] [Server thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:bee_nest
[15:03:47] [Server thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[15:03:47] [Server thread/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:spawner

Starting a server still spams the console with these messages in 1.15.2

Useless argument to be honest to say that because they didn't fix it, it's not a bug. They're free to fix this in 1.15.2 if they choose to do so. They fixed the glitchy boat on sand to go even faster than zero tick, they can fix this as well. 

Converting from 1.13.2 to 1.15.1, i get various mentions of this (nobody is logged in on the server)

```

[16:57:45] [Server thread/INFO]: 77% completed (33475785 / 43377684 chunks)...
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [pool-11-thread-15/WARN]: Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
[16:57:46] [Server thread/INFO]: 77% completed (33476499 / 43377684 chunks)...
[16:57:47] [Server thread/INFO]: 77% completed (33476985 / 43377684 chunks)...
[16:57:48] [Server thread/INFO]: 77% completed (33477521 / 43377684 chunks)...

```

The same for minecraft:spawner

Getting the spawner as well in upgrading 1.13.2 to 1.15.0 worlds using --forceUpgrade. 

Additionally there's light_gray_banner listed as well.

(25gb world file, it shows up about every 10% of the progress)

Still exists in 1.15.0 using `--forceUpgrade`
Unable to resolve BlockEntity for ItemStack: minecraft:light_gray_banner
Unable to resolve BlockEntity for ItemStack: minecraft:spawner

We noticed we're not getting this achievement in the latest 1.13.2 server jar and client available. 

I just got the 1.13.2 jar and a new client as well, and run it. used the /minecraft:give mrfloris minecraft:diamond_hoe{Damage:1560} to get the hoe and tilled grass_block and it changed to farmland, broke the hoe and it doesn't give the achievement. 

Sorry, I looked through the list for version numbers and it wasn't there, I assumed this meant I was supposed to select the last version. As it was an beta you had to specifically turn on. 

1.14.3 pre 2 doesn't address this by the way. 

I still get 1.12.2 and 1.13.2 running without hitting 25% during stress, and fans dont even kick in. 

1.14.3 pre 2 on macbook pro 2016 and imac 2017 and two older linux boxes, and it is 55% and up, rpm of fans blow to 3500 and things are only climbing, activity monitor showing other clients running at 12% 10% 19% 22% .. and 1.14.3 pre 2 at 492% 

It's a clear difference. 

I rather not have the fans on 24/7 for just running a singleplayer session or a server for a friend, or whatever i do in 1.13.2 without any stress to the system. 

iMac 2017 model, AMD 580 GPU 8gb ram, .. Apple has had 3.3 openGL since 2007, .. this is clearly a bug. 

Every 1.14 build has been at 50% and up, never below, during idle of the client, as well as in-game. On MacBook / MacBook Pro / iMac.

Just tested it yet again in 1.14.3 pre-1, and it's no different. 

Linux users are also reporting this, it's not limited to Mac. 

The fans on the system go mental, just trying to run the game for an hour. Unlike any mc version before. 

https://imgur.com/a/ndhHAAp

We can reproduce this on linux distros, macOS and Windows OS. It prevents us from --forceUpgrade and pre-generating chunks and upgrading. 

Hopefully 1.14.1 will address this 

I can reproduce this; https://youtu.be/U4lx0Sa1vao