A Bug Has Been Killing LEGO Worlds Save Files For Nearly Two Months

While neither console version of LEGO Worlds has been performing particularly well since the game’s launch, Xbox One players have been dealing with a particularly nasty bug that’s been irreparably damaging save files since mid-March.

LEGO Worlds is basically Minecraft with LEGO bricks. Players explore randomly generated worlds, scanning in LEGO buildings, objects and characters to ultimately use in their own creations. Dedicated players have already sunk hundreds of hours into the game between the early access on Steam and the official launch in early March.

[referenced url=”https://www.kotaku.com.au/2017/03/getting-started-in-lego-worlds/” thumb=”https://i.kinja-img.com/gawker-media/image/upload/t_ku-large/hhzavomd21jpsv9soxrp.jpg” title=”Getting Started In LEGO Worlds” excerpt=”Before you start building your own worlds in LEGO’s answer to Minecraft, you have to learn the roles and earn some gold bricks. Let’s take a look at the opening moments of LEGO Worlds.”]

Reader Scott tipped us off about the Xbox situation last week. He first pointed us towards the LEGO Worlds sub-Reddit, which is peppered with posts like this one from user Stormdude:

This is the second time this has happened on my XBox One and despite reaching out to Warner Brothers Game Support and reading numerous other cases on the Internet, I haven’t found a working solution. For whatever reason, Lego Worlds glitches out starts giving me the message: “Could Not create save data!”. This appears when you try to load your existing game and any new games you create. Anything that triggers a save brings up the error window, which means it basically appears during any kind of meaningful interaction with the game.

Ultimately Stormdude had to delete the game from both his console and Xbox Live, starting over completely. Then it happened again.

Unfortunately I’ve had this problem occur a second time, around when I unlocked the “Huge Worlds” at 80 bricks and ~700 discoveries.

Scott also pointed us to the LEGO Worlds Twitter account, where every single tweet is accompanied by a host of replies from angry Xbox One players.

@LEGOWorldsGame 72 gold bricks for Notting you say? pic.twitter.com/m4TGVXNNo8

— DMC (@BoB2oo9) April 17, 2017

The save data corruption issue originally affected both the PlayStation 4 and Xbox One versions of the game. The PlayStation 4 version was patched on March 17. Around April 6 the LEGO Worlds Twitter account indicated that the issue may have been resolved.

@Pseudonaja11 We believe this has now been resolved. Can you please restart console and sync save data with cloud. Let me know if that helps

— LEGO Worlds (@LEGOWorldsGame) April 6, 2017

But that was not the case, and the save corruption still continues.

We reached out to Traveller’s Tales’ LEGO Worlds team, who didn’t have anything to say about the situation aside from the same response they have been handing out in their Twitter threads:

“The team is currently working hard on a patch to solve the save data loss issue. We appreciate everyone’s patience.”