[MC-2368] Accidental joining of game causes world to not save for the session Created: 06/Nov/12  Updated: 19/Apr/17  Resolved: 23/Jul/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2, Minecraft 1.4.4
Fix Version/s: None

Type: Bug
Reporter: Andrew Plumridge Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: LAN, multiplayer, save, singleplayer, world
Environment:

Java 1.6.0_34 Win7 64, Quad core 3.6GHz, 8GB DDR3 RAM


Issue Links:
Relates
relates to MC-697 Default singleplayer player data is a... Reopened
Confirmation Status: Unconfirmed
Game Mode: Survival

 Description   

An improper method of joining a LAN server can cause the world to be "read only" and not save any progress. This is not immediately apparent as all nearby loaded chunks are editable and seems normal. Only when all players leave an area and return will they realise that progress is not being saved.

Steps to reproduce:

1) Start singleplayer minecraft game
2) Open to LAN
3) Run a 2nd Minecraft window and log in with unregistered name
4) In 2nd MC window start the same singleplayer game (by accident)
5) Realise error and exit SP in 2nd MC window and join Multiplayer LAN server as I had originally intended

Because the world has been opened elsewhere is seems to be read only, although nearby loaded chunks appear fine until you wander off and chunk is unloaded. This was most notable in the Nether. Player inventory does save.

The reason for running the 2nd MC window was to have a dude standing by a zombie spawner, accumulating zombies for the players to kill and gain XP.

This is an unusual scenario that most people won't encounter, but for those foolish and unfortunate enough to accidentally start SP instead of join LAN it's annoying losing hours of progress.



 Comments   
Comment by Kumasasa [ 23/Jul/13 ]

No answer, assuming no longer an issue.

Comment by Tails [ 28/Mar/13 ]

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by Andrew Plumridge [ 11/Nov/12 ]

Can confirm that it still happens in 1.4.4 pre-release.

In a new world, changes made near the origin of the world remained during the session, I ran 800 blocks away and modified a distinct landmark, and died. Upon respawning I could see my changes near origin, but when I returned to the landmark 800 blocks away it was untouched. I ran back to world origin and I could still see my changes at origin. I closed Minecraft and loaded the world again and only then did the area near Origin appear untouched.

Comment by TnT (Trinitro Toluene) [ 10/Nov/12 ]

Is this still a concern on Minecraft 1.4.4 Pre-Release? If so, please update the affected versions.

Generated at Sun Jan 12 11:57:37 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.