Certain custom biome settings cause game to spam "Received invalid biome id: -1" in the console, causing major lag or freeze
The bug
When teleporting to a dimension with custom biomes the client sometimes freezes or experiences major lag, with warnings in the output log "Received invalid biome id: -1". In some cases the chunks eventually load, but then some chunks appear to have the ID "null" while other chunks appear to have the ID "minecraft:ocean". At this point crossing chunk borders will cause more chunks in the distance to generate and more warnings to be spamming in the log.
How to reproduce
- Download the attached data pack MC-197616.zip
and add it to a newly created world - After spawning in, fly up a bit and teleport to the mc:197616 custom dimension
/execute in mc:197616 run tp @s ~ ~ ~
- The chunks load correctly with the correct biome in F3
- Teleport back to the overworld
/execute in minecraft:overworld run tp @s ~ ~ ~
- Move away a few chunks and then teleport back to the mc:197616 dimension
/execute in mc:197616 run tp @s ~ ~ ~
- The client freezes and lots of warnings appear in the output log (more than 1000 per second)
- If this doesn't happen (the world loads correctly) repeat steps 4 and 5. This seems to be related to render distance and world generation speed.
Linked Issues
is duplicated by26
MC-201141Client side log spam "Received invalid biome id: -1" causing lag spikes and computer crashesDuplicateMC-216833Invalid biome id causes in-game lag and log floodingDuplicateMC-220010null biome in custom world useing normal biomeDuplicateMC-220141Creating a custom biome world crashes the gameDuplicateMC-220973Recieved invalid biome id: -1DuplicateMC-221729Re-entering custom dimension fails to load custom biome when structures presentDuplicateMC-223104For some reason, modifying plains biome file can cause world crashDuplicateMC-223197it crashed when loading a world with the official caves and cliffs preview datapackDuplicateMC-223220Received invalid biome id: -1 - looped warning message causing game to freezeDuplicateMC-223355Incorrect Biome in 1.17DuplicateMC-223846Data packs are sometimes not checked when a custom world is loaded for the second timeDuplicateMC-223855Biome:null and patrols spawing inside vilagesDuplicateMC-223943Game crashes everytime i come to overworld from netherDuplicateMC-223944Game crashes everytime i come to overworld from the endDuplicateMC-224013Logfile flooded when reloading worldDuplicateMC-224067world gen pausing every few secondsDuplicateMC-224149Snapshot world corruption when leaving the netherDuplicateMC-224426Worlds created with the Official C&C Preview Datapack Can Cause Biomes With the ID null to generateDuplicateMC-224441Error: java.lang.IllegalStateException: Missing: ResourceKey[minecraft:worldgen/biome / minecraft:plains]Exit Code: -1DuplicateMC-224442Biome type says nullDuplicateMC-224461Entering a Chunk Causes Lag Spike in the Caves and Cliffs DataPackDuplicateMC-224495Lag spikes when crossing chunk bordersDuplicateMC-224624FPS drop in 21w17a with datapackDuplicateMC-224707Single Player Lag Spikes & Biomes changing in generated chunksDuplicateMC-224708Null Biome When in/near Aquifer DuplicateMC-224767Performance unacceptableDuplicate
NormalAttachments11
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
![[Mojang] Gnembon](../../../data/avatars/users/93709.png){kind=small}
ImportantCreated Issue:
useing buffet worlds dont save biome and lag a ton it makes the land from the biome but says a diffrent biome
I cant load a test biome in a buffet world and its lags a ton
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
useing buffet worlds dont save biome and lag a ton it makes the land from the biome but says a diffrent biomeCertain custom biome settings cause game to spam "Received invalid biome id: -1" in the console, causing major lag or freeze
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Helper] Jack McKalling](../../../data/avatars/users/92859.png){kind=small}
is duplicated by
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
unknown-1.png![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
is duplicated by
I cant load a test biome in a buffet world and its lags a ton
The bug
When teleporting to a dimension with custom biomes the client sometimes freezes or experiences major lag, with warnings in the output log "Received invalid biome id: -1". In some cases the chunks eventually load, but then some chunks appear to have the ID "null" while other chunks appear to have the ID "minecraft:ocean" . At this point crossing chunk borders will cause more chunks in the distance to generate and more warnings to be spamming in the log.
How to reproduce
- Download the attached data pack MC-197616.zip
- After spawning in, fly up a bit and teleport to the mc:197616 custom dimension
/execute in mc:197616 run tp @s ~ ~ ~- The chunks load correctly with the correct biome in F3
- Teleport back to the overworld
/execute in minecraft:overworld run tp @s ~ ~ ~- Move away a few chunks and then teleport back to the mc:197616 dimension
/execute in mc:197616 run tp @s ~ ~ ~- The client freezes and lots of warnings appear in the output log (more than 1000 per second)
- If this doesn't happen (the world loads correctly) repeat steps 4 and 5. This seems to be related to render distance and world generation speed.
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
is duplicated by
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
The issue for the attached datapack here is caused by `"biome_source": {"biome_source": { "type": "minecraft:fixed",`. The Fixed biome source is broken for json biomes and will not send the correct biome instance to the client. This is different than how multi_noise biome source works which saves the registry name of the biome and gets the correct biome instance.
is duplicated by
@Kyle Devir would be nice, but wouldn't fix the core cause of this issue.
![[Helper] gaspoweredpick](../../../data/avatars/users/80904.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
MC-224492
is duplicated by
is duplicated by
is duplicated by
is duplicated by
The main cause of this is now fixed.
THANK YOU SLICEDLIME!!!!!!!
is duplicated by
is duplicated by
is duplicated by
This is not fixed, I'm getting the same issue with my custom biome.
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-197616, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Duplicate of MC-197616
Probably caused by MC-197616
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Duplicate of MC-197616
Yeah, this is a duplicate of MC-197616
Duplicate of MC-197616
Duplicate of MC-197616
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
Please do not mark issues as private, unless your bug report is an exploit or contains information about your username or server.
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-197616
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
This bug is related to: MC-197616
When the above bug is 'active', a side-effect is that certain advancements are unobtainable.
Steps to reproduce:
- Get into a world with `Caves&Cliffs.zip` enabled. And activate the bug mentioned above. (you can verify this is active by crossing chunk borders in certain biomes which cause huge lag spikes and spam of `invalid biome id: -1` in the client logs)
- Try to obtain one of these advancements:
- Country Lode Take me Home
- Two Birds, One Arrow.
- Bullseye
- Very Very Frightening
_What happens: _ You should fulfill the requirements for them, but you won't obtain the advancement.
What should happen: You should get the advancement.
It doesn't seem to affect (at least when I tried it):
- Ol' Betsy
- Sniper Duel
Some notes: I experienced these bugs with this Environment, however, it could be that the advancements are bugged out in other scenarios too. Besides, it's very unreliable, as I restarted the server and then I could obtain one of the advancements, however, trying to obtain another advancement didn't work, even though the chunk borders glitch wasn't active. Feel free to expand this post with more findings.
Duplicate of MC-197616
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
Duplicate of MC-197616
Most likely a duplicate of MC-197616
It might be a different issue then, I also came across this when I tried to use a custom biome as a buffet world but I thought it was MC-197616.
Duplicate of MC-197616
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Would MC-197616, happen to describe your issue?
Duplicate of MC-197616
I don't think it's a duplicate of MC-197616 because we don't get spammed with "Received invalid biome id: -1". Also we did not use any custom biomes unless the CavesAndCliffsPreview creates custom biomes. I can't see anything in the logs, so I also don't think it is something like the disk i/o lag when writing logfiles as described in the comments there.
This could possibly by a side-effect of MC-197616 but more people would have to test it out
Be aware that any datapack with biome changes corrupts worlds ( MC-197616 , 1.16.1 was the earliest it was reported,). Just a warning since you mentioned using the CavesAndCliffsPreview datapack.
Which week's datapack did you use? The CavesAndCliffsPreview.zip file updates every week (even though the name doesn't).
Also be aware of the bug MC-197616 , which can be summed up as "since 1.16.1 datapacks that change biomes in any way corrupt the world and eventually write errors to the logger so fast it crashes your computer". Because of this catastrophic bug NO version of CavesAndCliffsPreview.zip is safe to use. Having said that it's probably safe for creating a new world and testing stuff for 5-15 minutes before discarding the world.
Duplicate of MC-197616
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Still waiting on the 1.17+ release on the related bug that was mentioned by Snow (MC-197616) - showing it was fixed. As soon as it's out, I would test this issue again and see if it's resolved, it very much appears to be related (fingers crossed 
).
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Duplicate of MC-197616, which has been fixed for a future version of Minecraft. 
Duplicate of MC-197616, which has been fixed for a future version of Minecraft.
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Thank you for your report!
We're tracking this issue in MC-197616, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Please provide a screenshot of your game with the F3 debug screen enabled, please also provide the datapack in question.
world is in zip
if it loads lol
You can do this on any world not just the buffet world (Provide the screenshot with F3)
its called den I made it as a test
sorry my files are the same name
Would like to mention that loading a superflat world with no mods and no datapacks on version 1.16.2 still causes the console to be spammed with invalid biome -1
I can also reproduce this on a server that I play on.
This issue happens on a server I manage. All players are spammed with `Received invalid biome id: -1` in their clientside log; the serverside log does not contain any errors.
The world is default vanilla, not custom. It was generated in Minecraft version 1.16.1, and updated to 1.16.2 when the version was released.
Whilst ingame, it seems that certain biomes (not sure which exactly) will cause this spam. If you log out during the spam, or get kicked due to your client locking up, attempting to log back into the server will cause your clientside log to be spammed with this error and prevent you from logging in. I'll attach an example video, showcasing the spam happening during a server login attempt.
Minecraft_14-08-2020_20-15.mp4
I can also reprduce this issue and it lags forever for some players on my creative server.
The lag comes from the logger logging this warning. As the logger do synchronized disk io and notifying the launcher log, it lags a lot.
I can confirm this is still an issue in 1.16.4's final release.
can confirm for 21w11a, this happens even if the base biomes have any little change to them, via color change or addition of already existing generations.
note, this isn't even from updating worlds to the latest snapshot, it can already exist if the world has any form of biome generation or customization in the existing datapack.
This appears to have gotten worse in 21w11a. It's reliability reproducible by having a biome with a custom configured structure feature.
In 21w11a game crashes before even entering the world.
a renamed biome to a new one causes that as well - don't need to have a configured structure feature.
With this one / attached happens almost immediately and spams render thread:
Attached dimp2n14.zip datapack with renamed biome with one configured feature to replicate.
Can confirm 21w13a
can confirm for 21w14a, the world has been doing fine until a certain amount of time while flying through the world caused the log to get spammed once more.
From my testing and debugging, this appears to be specifically caused by the json biome having any structures added to it and the user loads up an already generated chunk with that biome. The instructions about exiting and re-entering the dimension is not needed. Just fly forward in the dimension for a few seconds, turn around, and fly back and the issue will present itself.
I was helping someone with their mod and they were using json biomes/json dimensions for their mod and they got this issue because their biome has structures in it. When I ran the debugger, their biome source was using the correct dynamic registry instance and was returning the correct biome instance. But within SChunkDataPacket class, it had the exact same dynamic registry so that was good. But the biome being returned from the chunk is a completely new biome instance that is not present in the dynamic registry at all. And that is what causes the massive lag spike as the game starts writing the error to the log like crazy. So as far as I can tell, the biome source is not the issue here. The chunk receives the correct biome as well as it doesn't error upon first generation. Rather, the issue seem to lie in how the chunk either saves the biome to memory or retrieves the biome from memory. But only when structures are present in the biome.
Very odd situation but hopefully this digging I did helps
I've checked with someone who has such a case in a modded environment. Simply we loaded the world, then put a breakpoint on the Biome class' constructor and replicated it like telepathic grunt did above.
What I noticed looking through the debugger is that when structures are loaded, what yarn calls `RegistryOps` will attempt to load the biome from json and decode the biome. This occurs somewhere in the call site of `RegistryOps.of(...)`. This occurs in the constructor of `PoolStructurePiece` which occurs as a result of loading structure starts.
Yarn names of course, cannot recall what mojang's official names call these.
Can confirm for 21w15a, with THE CAVES & CLIFFS PROTOTYPE DATA PACK being used.
Seems to be happning on 21w15a world as well.
only without this datapack, and it seems to be triggereing when traveling from the nether to the overworld. but it does use the Caves & cliffs preview datapack.
this is exactly what happens when I fly around with the new 21w15a world gen datapack.
Can reproduce here in my world too with the Caves & Cliffs preview datapack, hope this will be fixed soon!
Can also reproduce here with 21w15a with the Caves and Cliffs datapack.
I suppose that there's no stopgap workarounds for this... :|
I don't think it's intended to spam 1 million (without exaggeration) lines of LOG messages in 25 seconds time, basically freezing the client in place.
I ran this on a server, there is a huge spike when I teleported to world spawn. This happened twice and both times it was about 1 million messages like these:
Once from timestamp 22:07:57 til 22:10:25 and once from 22:21:49 til 22:22:14.
These log messages were sent to the client, the server logs seem to not contain any of these messages (since it's a renderer log message)
It would be nice if Mojang gave us options for tuning the verbosity of Minecraft's logging output, including being able to disable it entirely.
Note: it seems that it is most notable at spawn chunks. The lag seems to be a lot better once you go further from spawn, but it's still there as far as I know.
Same issue using this datapack. Is there any way I can help ?
I loaded the datapack and went into my custom dismension. Then I traveled throw it to check the generation and the error occuerend when I U-turned to kill a ghast (yeah I know poor creature ...). Now if I load the save it directly crashes like nothing can be loaded anymore.
debugDP.zip
Ran into this exact issue on 21w16a, using the co-current official Cliffs & Caves preview datapack. (Not a custom datapack.)
Seed: -5012719132029526681
X: 2327 Y:1245 (Dim: Overworld)
Going further west crashes the game (when a desert biome is loading.)
Unfortunately its hard to give a example to show because putting the exact seed and place doesn't give the same outcome. I've tried every time its crashed to get the seed and go back so I can give a example but for some reason this problem is completely random. it happens a lot though but usually when flying around in creative. Just tested the 21w16a datapack same bug occurs.
After testing this issue in several scenarios, can confirm in 21w16a. However it is rather inconsistent as @Willber mentioned...
Some points worth mentioning:
Really hope this info helps the devs
- this problem is very bad for an SSD with so many writes, and makes the current datapack somewhat unusable 
All tests done on varying seeds with no obvious pattern (except for the points above) as to when the log file "lockup" would happen and when it wouldn't.
It happen to me as well. Latest snapshot, official Cliffs & Caves preview datapack. It happen after some time of playing (1h+). World starts lagging a lot and was unplayable. Restart does not help. So I delete the region folder and re-generated all chunks. Again. No issue, but after another hour world starts lagging again.
I can provide save if needed.
Set the file latest.log to "Read only" to solve this problem perfectly
No it doesn't, wayne, you're not helping.
Even if it reduces the lag when crossing chunk borders (which I did not find to be the case, at least not any more significantly than just exploring with the output log closed instead of open), the biomes still become null in-game.
So I've created a new world (random seed). Played for about three hours - no issue. Then I've logged, jumped to water, big lag that ended by my drowning
And this is how it started:
I just went to "Edit" and hit "Optimize World," and it helped a little bit. Although the glitch still occurs (sadly), it can temporarily help if you're stuck in a crash loop when loading up the world.
Since this now effects the Caves & Cliffs datapack (V1 and V2), I'd consider it a major bug that needs top prioritization.
I posted a bug report about this with the caves and cliffs datapack, when leaving the nether from teleporting/dying it turns the entire spawn region or more into ocean, it makes it completely unplayable with the lag/corruption and I hope this gets fixed soon!
can confirm for 21w17a
Does anyone know how to disable logging to preserve SSD health? And perhaps where to edit a Biome Id?
This makes the game unplayable in 21w16a and 21w17a.
Yes, 21w17a, latest Caves&Cliffs datapack. I've created a brand new world, played it about 1 hour, then exited the game. After new start I've created a backup as game suggested and opend the World. I didn't move, only open a furnance GUI. Then game lags again and world is corrupted
I can confirm it is possible to edit the attributes to read only. This will stop the log from being used but the lag will still happen. It doesn't appear to be related to the log or to Disk IO.
I don't know if "Important" is the highest priority but I really advice you to make this issue the biggest possible.
Now the problem event show when youtubers want to show snapshot updates that is stragically a bad thing for Mojang
Ii.e with Aypierre here : https://youtu.be/MPcfoHC6DCI?t=517
I agree with increasing the priority of the task, however not for Candelaresi's reasons. Sorry, but this is a snapshot release, no one cares (in a way that would damage Mojang's reputation) if it is not working perfectly, it is not the mainstream stable release, teething is to be expected in snapshot releases - especially datapacks like this one, because of the primary purposes of improving development and looking after the health of the Mojang team.
Having said that - and without insinuating there should be more pressure on the team - the last two releases are actually unusable, sort of defeating the purpose of releasing more snapshots if you can't even test them and provide feedback ... so it does make it high priority in the sense of a "broken snapshot" that can't be properly used or tested.
I imagine a great deal of players don't have SSD's or copious amounts of RAM, so this isn't going to take an hour or two to crash, my own machine with SSD and 16G RAM (intermittently) will crash within 5-10 minutes of spectator mode with the latest datapack ... this means testing isn't really feasible, and is (at least slightly) damaging to SSD's as well with the writes, so this (IMO) should take higher priority to be fixed.
Agree with@Kai , I prefer mojang to spend several weeks on fixing it. We can wait for a more stable snapshot so that we can test it and feedback.
I think that the other commenters are correct, as well; at the very least, we need a way to disable this specific error from spamming the log. I really want to play on this datapack, but I don't want my motherboard's SSD to end up getting damaged by doing so. We really need a 21w17b datapack that doesn't crash the game or literally damage players' hardware...
Caves&Cliffs(NoBiomeFix).zip
This edited Caves&Cliffs preview pack should fix the issue! : )
It removes the custom biomes that cause the bug, although that means the updated 1.18 ore distribution won't happen. However, the dripstone clusters, caves, geodes, etc. work just fine! I hope this is good enough until the datapack biome bug gets fixed!
(Note: The ores still generate below Y leve 0, which is a good plus for this datapack! Also means deepslate coal is common with it)
Update: The bug still occurs, although much more tamed. Thankfully it avoids the null biome bug.
Thanks @Lunade Lunade! I see you deleted the Biomes folder- I suppose that means the Lush Caves are gone? Does Mojang take on volunteer bug hunters? If so, I'd be down to sign an NDA and spend a few days digging through the codebase to squash this one.
I believe adding a custom dimension bypass this bug at least on one biome
note it doe not work
better fix it soon i hope snapshots are a pain with it like this
Someone mentioned, that this is connected to structures. So I've created a new world without structures and I'm not able to reproduce the invalid biome issue. But no villages, mine shafts…
I can also confirm that my dimension stopped experiencing null biome errors after I removed my custom structures from the biome "starts" field. I cannot, however, offer any explanation as to why.
i think the lag only happens when its in a datapack so the thing to do would be bypass the datapack system
My noise cave nether datapack works fine must be a height based thing
Here’s my planet minecraft link as I can’t link it right now to try my pack https://www.planetminecraft.com/data-pack/noise-cave-nether/
I ended up living in the nether to avoid it
Ticket
MC-224767was "resolved" (by a bot) as a duplicate of this ticket.MC-224767has absolutely nothing to do with this ticket. Please re-openMC-224767.Jim Gersetich this is not the place to request re-opens please go to the Mojira subreddit for request like these, not other peoples reports.
You don't handle your own tickets? What kind of "support" is this?
Just forget it. It's clear bug reporting isn't important to the development of new features at Mojang. I'll just wait until a future snapshot comes out and try again.
@Jim Also this bug is actually the cause of that one you requested to be reopened, maybe pay a little attention and do some actual troubleshooting to determine where the two add up.
And you know that how?
@dan hop, your datapack doesn't modify or create any biomes. That's why it works fine.
@Jim Because your description of the problem, how it presents and steps to recreate match with the troubleshooting that's been done by myself and others in pursuit of understanding this bug. You just didn't think hard enough and look far enough before deciding to complain that Mojang was being "unacceptable."
Custom biome? Invalid biome id? Custom dimension? Those are symptoms prominently mentioned in this ticket, yet I never listed (nor have I seen). I'm in a vanilla world, and I see the problem (sometimes) VERY early in the game (like, within the first 2 minutes). Other times, it takes hours.
A technical support team should look at the logs to find out if this is indeed the same problem. From your comments, it's plausible, but certainly not at the top of the list. Valid tech support verifies the problem rather than just guessing (as you have done, as well) that the problem is the same.
Sorry Jim, you are still on the wrong track. Claiming its vanilla, and installing the Data Pack for 21w17a.... Means you're missing an important point (one that is described when you load the data pack by the way)... You are running a custom world! Hence read more carefully from start to finish, this whole case, and you will hopefully see where you misunderstood. You'll be happy to know your problem of freezing/lagging, etc will be looked at when they fix this bug.
As a side note, this case was originally opened only for custom worlds, but when the data pack was released - because it was installing custom biomes - it became linked to this case.
@Jim Gersetich, that datapack modifies all biomes in overworld to fit new height.
The main cause of this is now fixed. There may be other issues remaining that cause the same error message - if so please post new specific issues identifying the settings that still cause the error.
much better still jumpy but the custom worlds dont crash
Does this mean Mojang's CavesAndCliffsPreview.zip is finally safe to use? Or at least the week 18 one?
It still jumpy but you can use it
Do we need to download a new copy of the datapack to test this fix?
It appears you all may be correct: I haven't experienced the slowdown in an hour or so of playing.
Kai: The message mentions nothing about custom biomes or dimensions. It merely says "experimental", which might be interpreted that way, IF one knew that it was even possible.
I contend that the Description field should have been updated at the time you say they discovered it applied to the datapack they are trying to get us to test.
Good to hear it's working for you @Jim, working for me too
.
Yeup, in this case, the data pack makes/modifies biomes (thus becoming custom biomes) which don't exist in vanilla (like noise or lush caves, etc), therefore falling into experimental.
More often than not, because it's extremely time consuming for moderators to explain their actions in detail, and update fields constantly to match new findings ... the easier thing is to read the tasks. I truly understand it can be a pain, as this task had A LOT of content to read, but it frees up moderators to handle cases as quickly as possible and they're working for us at the end of the day. Then viola, it gets fixed
Hope you enjoy!
Kai:
It shouldn't be a moderator that makes such a change. It should be a developer, or perhaps a moderator operating under development instructions.
I know NOW that experimental = custom, and it makes sense. But, this is a bug report mechanism, and nobody (official) should ever assume that posters know what certain constructions mean. Above all things, a bug reporting mechanism must be fully understandable to EVERYBODY who uses it. No prior knowledge should be expected.
This is because it is primarily the newbies who are going to find the problems. By definition, they don't know what should and should not be issues or why. The mechanism by which they report issues should be almost bulletproof to them.
Experts can chime in to explain things, but the descriptive text of anchor tickets (tickets under which duplicates are held in stasis) needs to properly reflect the bulk of the information needed to figure out whether a new ticket fits or not. Perhaps a new section near the top should exist, titled "Moderator Notes" or "Development Notes" or something like that.
I searched for tickets using all the keywords I could think of that would apply. And, I even came across this ticket in those searches. But, the description was so far from what my experience was that I couldn't envision it being the same problem.
Two things could have been added that would have helped. First, the description could have mentioned the word performance or lockup or something similar. This would have indicated to me that the ticket could be a match.
Second, the description (or another proper field, but always near the top) should mention HOW one can check the logs to find out if this problem is indeed what they are experiencing. Even a link to a wiki page would be acceptable for this purpose.
Finally, I still don't actually know how to look at the logs. I know they must exist, but even now, knowing the problem was my problem, I don't know experientially how to tell for certain that this was true. I found a Crash Report page on the wiki, but the game wasn't crashing, only hanging for periods of time. So, if a similar problem happened again, I would be at a loss to figure out whether something was being spammed into the log file.
Bro, can you shut up @Jim? You misunderstood the cause of your bug, the moderation team's quite intentional and reasonable manner of response to it, the purpose and intent of this bug, and the actual state of experimental custom world features. But that's okay, no one was holding it against you until now. Quit while you're behind and move on with everyone's lives.
Please remember the bug tracker is not a discussion forum and any discussion about a bug should take place outside of the bug tracker, such as on our reddit and/or our discord server.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I'm experiencing a similar bug in 21w19a even without the datapack, every chunk border causes lag
I don't know if I should report it or not because I don't understand the causes/technical things behind it, but just wanted to get it out there.
You using any datapack that makes the chunk height bigger
if so check out
MC-225178Actually I found out my problem, it's a weird solution but someone talked about it before.
I gave it 4GB of RAM, and I guess since it takes longer to clear, it caused lag. Once I gave it only 2GB of RAM, it was fine.
I don't know why I didn't think of that earlier
Once, I Tried To Make An End Noise Nether. So, There Is A Nether Waste Cutting The Crimson Forest And Warped Forest. The Game Lag, Then Crash. When I Reload The World, The Nether Waste, A Bit Of Crimson Forest, And A Bit Of Warped Forest Turn Into Ocean Biome. Such A Weird Bug.