-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IllegalArgumentException: Chunk is not loaded at class_4076{x=20, y=0, z=-3} #705
Comments
This is a known issue. Despite the version bump, Sodium has not yet been released for 1.17, and it is not ready for production use. Testing and development of 1.17 is ongoing, see pinned issue #674 for more.
|
Reporting issues for staging branches isn't an issue. I prefer it over Discord. We just need to make sure they're labeled correctly. |
Hi, I experienced the same crash - completely understandable given that I was using the Thanks for your continued efforts to make Minecraft playable on older PCs. 🙂 |
I have a similar crash on the same build. Happens when going into unloaded chunks between the overworld and nether on a server. Seems to not happen when the chunks are already loaded. Can't reproduce when teleporting within the same dimensions into unloaded chunks. I can't really reproduce it in single player. Could be because of rendering distance differences or I'm just not replicating the situation well. I doubt its the datapacks on the server though. Client has these other mods: |
Closed by c0135a6 |
Version
Minecraft: 1.17
Fabric loader: 0.11.6
Sodium: mc1.17-0.3.0+build.428
Reproduction Steps
None. I was just playing when the game randomly crashed
Crash Report File
https://paste.gg/p/anonymous/539761e737924fd886a4d23b6cecc2d9
Additional Information
This happened during normal gameplay on a dedicated Fabric 1.17 server running Lithium, Starlight, Krypton and LazyDFU
Client mod list is:
Dark Loading Screen 1.6.5
LazyDFU 0.1.2
Lithium 1.17-0.7.2
Sodium 1.17-0.3.0+build.428
Starlight 1.0.0-RC2 1.17.x
The text was updated successfully, but these errors were encountered: