filtered geodes sometimes cause crashes
Open
Vei27 messagesstarted Sep 26, 2026, 9:38 AM
Vei27 messagesstarted Sep 26, 2026, 9:38 AMgameplayother
VeiOP3 weeks ago(edited)2
Background PinguApp3 weeks ago(edited)
veiivy
1 Issue Found:
Mod draftout seems to be causing this crash.Page 1/1 • Modrinth App 26.1.1 Fabric 67f5c6c9 crash-report
violetneidon3 weeks ago
just adding to this what i figurd out
the issue seems to be caused by draftout filtering for guaranteed fully grown cluster by modyfing block data in the geode directly, in this instance the geode is both outside render distance and outside spawn chunks so the actual chunk its in doesnt exist
the issue seems to be caused by draftout filtering for guaranteed fully grown cluster by modyfing block data in the geode directly, in this instance the geode is both outside render distance and outside spawn chunks so the actual chunk its in doesnt exist
noura 🜛3 weeks ago
did this happen during a match?
violetneidon3 weeks ago
https://discord.com/channels/1493030345048719483/1507390946910928916/1553337593863868489 according to them yes, possibly before match start even
violetneidon3 weeks ago
no clue how opp didnt crash, possibly lower rd
violetneidon3 weeks ago
@Vei would probably be helpful if you can provide match id
VeiOP3 weeks ago(edited)
im pretty sure its this: 547625 (im basing this fully on the fact that I had to reconnect and my goal pick timed out that match, I really don't remember which one it was otherwise)
VeiOP3 weeks ago
interestingly when I try to open the world this pops up
VeiOP3 weeks ago
actually its prob just because of the crash
VeiOP3 weeks ago
nvm lol
pancelor3 weeks ago
I just crashed when opening a replay, the stack trace looks like it's the same issue (guaranteeFullGrownCluster)
[23:01:24] [Render thread/ERROR]: Reported exception thrown!
net.minecraft.ReportedException: Exception generating new chunk
at knot//net.minecraft.util.thread.BlockableEventLoop.throwDelayedException(BlockableEventLoop.java:203)
at knot//net.minecraft.util.thread.BlockableEventLoop.pollTask(BlockableEventLoop.java:137)
at knot//net.minecraft.util.thread.BlockableEventLoop.runAllTasks(BlockableEventLoop.java:127)
at knot//net.minecraft.client.Minecraft.runTick(Minecraft.java:1345)
at knot//net.minecraft.client.Minecraft.run(Minecraft.java:991)
at knot//net.minecraft.client.main.Main.main(Main.java:248)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:514)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:72)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
at org.prismlauncher.launcher.impl.StandardLauncher.launch(StandardLauncher.java:115)
at org.prismlauncher.EntryPoint.listen(EntryPoint.java:129)
at org.prismlauncher.EntryPoint.main(EntryPoint.java:70)
Caused by: java.lang.IllegalStateException: Requested chunk unavailable during world generation
at knot//net.minecraft.server.level.WorldGenRegion.getChunk(WorldGenRegion.java:128)
at knot//net.minecraft.world.level.LevelReader.getChunk(LevelReader.java:146)
at knot//net.minecraft.server.level.WorldGenRegion.getChunk(WorldGenRegion.java:109)
at knot//net.minecraft.server.level.WorldGenRegion.getBlockState(WorldGenRegion.java:149)
at knot//net.minecraft.world.level.levelgen.feature.GeodeFeature.handler$zzi000$draftout$guaranteeFullGrownCluster(GeodeFeature.java:572)
at knot//net.minecraft.world.level.levelgen.feature.GeodeFeature.place(GeodeFeature.java:173)pancelor3 weeks ago(edited)
Background PinguApp3 weeks ago(edited)
pancelor
4 Issues Found:
You sent a latest.log, which often lacks critical information. Please send the full Prism log from Edit > Minecraft Log instead. Mod draftout 1.16.1 seems to be causing this crash.
Your log has your PC username in it. You might want to delete it.
You can press the Re-Upload Log button so the bot will re-upload the log with the PC username censored. You sent your log as a file. Please press the Re-Upload Log button so the log will be re-uploaded to mclo.gs so people can see it without having to download it.Page 1/1 • Linux Prism 26.1.1 Draftout latest.log 67f5c6c9 crash
pancelor3 weeks ago(edited)
Background PinguApp3 weeks ago(edited)
pancelor
3 Issues Found:
Mod draftout-1.16.1.jar seems to be causing this crash.
You don't have enough free RAM on your PC for this instance, at the time of launching the instance. This isn't critical, and is just likely to cause performance issues. Either free up some memory by closing apps, or ignore it.
You are using 3 outdated mods. Download the latest legal versions here: Hermes, Lithium, StandardSettings.You can get the latest versions of all mods from this website.Page 1/1 • Linux Prism 26.1.1 Draftout 67f5c6c9 crash
VeiOP3 weeks ago
ya thats the same thing I'm pretty sure
violetneidon3 weeks ago
question, was your RD 26 or lower
pancelor3 weeks ago(edited)
I'm pretty sure I had RD=32, since that's what it always defaults to when I load a replay (it probably gets set to 32 by StandardSettings)
I never saw the replay, I just pressed "view replay" in the menu, tabbed out for a bit, then noticed minecraft had crashed
I never saw the replay, I just pressed "view replay" in the menu, tabbed out for a bit, then noticed minecraft had crashed
pancelor3 weeks ago
weirddd I just loaded that same replay and it works fine now
pancelor3 weeks ago
(and I tested and confirmed that StandardSettings always sets RD=32, even if it was set to something else in the previous world)
pancelor3 weeks ago
SD=10 if that matters, doubt it tho
violetneidon3 weeks ago
it does seem to be the same crash error but i was wrong in my original assumption, the chunk reported (-4, 0) is within spawn chunks so idk
pancelor3 weeks ago
I tried reproing exactly how I crashed it (go to replays menu, choose replay, click "view", alt-tab) and it didn't crash. it probably didn't crash the first time (when I downloaded the replay) either, tho maaaybe my memory is bad and the initial crash was right after downloading
pancelor3 weeks ago(edited)
also to be clear it didnt crash during the match, it just crashed the one time when loading the replay
violetneidon3 weeks ago
shrug
violetneidon3 weeks ago
someone with actual development tools should try to replicate this to get a better look at whats actually happening