A yet-unsolved bug is currently wreaking havoc in the Xbox One version of Lego Worlds, destroying entire save files and causing players to lose dozens to hundreds of hours of progress in the creative open world game. In some instances of the glitch, an error message pops up any time the game attempts to make a new save as well, halting progress every time the game tries to make a new autosave and rendering the game effectively unplayable.
Lego Worlds came out in March of this year on PlayStation 4, Xbox One, and PC, seeing less-than-stellar sales figures. However, as a creative sandbox “Minecraft-style” game, Lego Worlds still has a dedicated fanbase, with some users spending hundreds of hours building and creating within the world since the game’s release, making the loss of save data that much more potentially painful.
The save game glitch popped up early in the game’s lifespan, affecting both PlayStation 4 and Xbox One users; players would be confronted with a sudden error pop-up reading “Could not create save data!” any time they tried to load up their old save, start up a new file, or make a new save on an existing save-game they already had. The glitch was patched for PlayStation 4 on March 17, and on April 6 the official Lego Worlds twitter responded to a glitch complaint from an Xbox One user with the following:
However, it seems that this was an erroneous statement, as players are still reporting en masse that the glitch persists. Social tweets from the game’s twitter see angry replies from users unable to access their saves, and on the official Lego Worlds subreddit, players continue to report in angrily as recently as yesterday, reporting the save error bug, calling the game “buggy POS”, and some even asking for refund.
The response from Lego Worlds is currently the following, shared across a number of their public sites: “The team is currently working hard on a patch to solve the save data loss issue. We appreciate everyone’s patience.”
Lego Worlds support can be reached at lego.com/worlds/support.