-
-
Notifications
You must be signed in to change notification settings - Fork 881
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
Minecraft freezes when 'saving world' on 1.20.4 vanilla offline mode #5374
Comments
I saw the discussion on that last issue suggesting that this is purely a game bug. However, I should add that there are definitely launchers out there that don't have this problem (namely TLauncher) so it might be deeper than that. On the matter of TLauncher I noticed it runs the game with |
Try using Java 17, since that's what is officially supported. |
I know one possible cause. Not having enough disk space on the drive the Minecraft install is in. Because there is no space on the disk, it can't save and gets stuck. |
This issue is also present with 1.20.6 but I am NOT in offline mode. I am launching Minecraft the normal way and I have waited 30 minutes for my world to save. Just like OP, it is a cloned instance. |
Since there is a difference and we need to see the log, it might be a good idea to create your own thread (if you haven't already). |
to answer this, there is no change in behavior with java 17 |
definitely not the case
|
right before pressing 'save world': It's definitely doing something (although how the hell did we get to region -20,0 in a world that was just created is anyone's guess):
|
Is the Intel graphics the best you have? |
Operating System
Linux
Description of bug
Expected:
Actual:
Additional info:
Logs.
Does not happen when using normal online launch with the same profile.
Related? #3620 Facing the same on fabric but created a new instance without any kind of mods to be sure.
java --version
output:Platform: Linux Ubuntu 22.04.4 LTS kernel 6.5.0-26-generic
Steps to reproduce
Suspected cause
No response
This issue is unique
The text was updated successfully, but these errors were encountered: