Shadow

I can confirm that this has happened multiple times; this would result in me having to manually fix these chunks with an NBTEditor and manual copy/paste from a previous backup.

This started when I noticed a lot of bad areas the first time I backed up my server world file and did some fixes in singleplayer; my base had many chunks at 20+mil InhabitedTime and one of my islands in particular were completely caked in these. I’d fix them (It would take like 30 minutes of my time be it manual so it was not fun) and I don’t worry about it. This was around late October.

Today I noticed when I had to do some repairs on my base (multiple areas were off by 1 block) that it would do these areas in a smaller square around the player. I have a copy of my world file when I was just at the beginning of fixing my base; I see one rectangle of 20mil+ InhabitedTime. Then I have a copy of the finished process with the fixes and I see multiple of these uber high InhabitedTime rectangles; one for each time I reloaded the world file it seemed. Some chunks had InhabitedTime so high that it causes an integer underflow (at 2147483647 the 32 bit limit) and rolls down to negative InhabitedTime. This could cause unintended behaviour through Local Difficulty if there is negative InhabitedTime chunks being used for calculation (though I haven’t tested this; it’s still bad).

I’m not sure if mods have had this fixed (be it intentional or not) but this does NOT happen in multiplayer servers as the server only loads once and the concept of spawn chunks no longer exist which probably confirms that nothing simulates when the server is just starting up at the general spawn area.

Given the fact that chunks InhabitedTime experience an integer overflow given enough reloads, I think this can be a serious issue down the line. I could test this more on my end later but I believe enough information is gathered at this point outside of examining the code itself.

Also would be nice to change its status.

Apologies, I kind of forgot about the bug report, don’t think my email works properly with push notifications but here is the Google Drive link to the June 2025 backup that is below (albeit barely) 5GB: https://drive.google.com/file/d/1wP4svpc93SZmGu4HAABtdSWQueNVpeXP/view?usp=sharing

Latest snapshot only improves performance by 15-30% instead of the 80-100% needed to match 1.21.4 when using shaders that use vertex/index buffer uploads. It helps sure, but I can’t say on my end its “fixed”, there’s more at play. And this is using the latest drivers on my GTX 1060, which can complicate things since these and older GPUs use a different driver than that of the RTX 20 series and above.

In my case, it does Verifying World! for like only 5-10 seconds before giving me the error. Also when I contacted Mojang support, they told me that they were aware but to close the ticket and reference the ticket number later in a new ticket.

My world file of choice (Present in 1.21.5 and 25w19a):

The test world file I generated (Fixed in 25w19a):

Datapack list (These uploaded fine in the past and disabling them did not help):

please fix the minecraft launcher because im sick and done with this

i paid alot of money to get minecraft yet it dosnet work nice one scammers

every time i open the minecraft launcher no matter what i do it always says a error has occurred and im sick of it so please try and fix the launcher since im done with having to try everything for nothing and i paid alot for bedrock and java but i cant even play the demo of java or normal java at all

Just ignore the word “hotfix” I didn't know what that meant, now I do, please don't be mad at me, this is my first time reporting a bug, I can't edit it, so I'm stuck with it saying “hotfix” when the report that I made just now, isn't a hotfix, I just saw that it had the game version I'm playing on and thought “this is how they'll know that I'm playing the now update” which thinking back on it, was stupid, of course they'll know I'm playing the current version of Minecraft right now because they just recently updated it and I updated my phone to this recently updated version so I thought it was weird that it said “hotfix” at the end but I didn't think anything of it but then after I posted this bug report a few minutes ago I went to Google to ask what a “hotfix” is, and I then realized I messed up! I am so sorry! Just pretend there isn't the word “hotfix” in it!!

So what we do

Is this one 1.7.9 or 16w42a?

If this is the former, then your version is outdated.
If this is the latter, then please provide more details, such as (but not limited to) crash logs.

Read the "Affects Versions" tab on the other bug:
/*
Affects Version/s:
Minecraft 1.10 Pre-Release 2, Minecraft 1.10, Minecraft 1.10.1, Minecraft 1.10.2
*/

This is just a duplicate.

If you haven't already, turn off VBOs and turn on VSync. Some people have also reported increasing MC's allocated RAM helps as well.
If that doesn't work, you need to either upgrade your graphics drivers, or, if upgrading them caused the issue, downgrade them to a safer version.

So, this is a problem with the launcher?

I'll assume you've bound your left-click to Use.

That's normal. Cats will sit on chests and prevent you from opening them. The only way to get them off the chest (trying to use them doesn't work) to either push them off or I believe lure them with fish, but the former definitely works.

Duplicate of MC-9974.