Minecraft Forums

Yet another "chunk apocalypse" at play. Apparently under 1.3 we don't just lose chunks (vast regions of wiped-out blocks) but now they get corrupted as if a giant nuclear bomb went off.

And of course they happen in constructed areas, wiping out big sections of hard work. Here's the latest: and entire half of a hotel structure randomly "blown up".


You can see it's not like the old chunk problems, where a clean "slice" of world is missing. Now it's just erasing some blocks in a chunk, and leaving others.

Some day I'd like to walk into the Mojang offices, erase a few months' work from their hard drives, and say "how does that feel? Sucks, doesn't it?"

Of course the worst part is that I'm paying THEM for the privilege of ruining my work, so they still get paid if they have to start over.

(Fortunately, because of the ongoing chunk problems, I am now in the habit of backing up structures so I can revive them with MCEdit after a Chunk Attack like this one.)

Mojang isn't deleting your work, Minecraft is not saving the chunks properly. If the chunk error is permanent, then it's kind of unfixable, as if the error is permanent, Minecraft is refusing to save the chunks. But if every block comes back, then it's just a chunk load error.

Quote from Syfaro

May I remind you that this is a game and that you paid willingly and knowing that there might be bugs?

I don't remember anywhere that stated that you were entitled to a bug free, perfect game.

Years of being fed crap code have left an entire generation unaware of how the whole consumer-manufacturer relationship works.

Your thinking would nullify any warranty, guarantee, consumer protection, fair trade and pretty much any other basic consumer expectation in the entire world. Thankfully, you're not in the majority, and most people recognize that when they pay for something, they have certain expectations.

But you go ahead and enjoy your gruel. And if there's a fly in it, well, enjoy the extra protein.

Quote from lightbulbwindows1000

Mojang isn't deleting your work, Minecraft is not saving the chunks properly. If the chunk error is permanent, then it's kind of unfixable, as if the error is permanent, Minecraft is refusing to save the chunks. But if every block comes back, then it's just a chunk load error.

Mojang writes the code that makes Minecraft destroy one's work, making the entire game sorta pointless. Who else do you think is responsible? Alien assonauts?

Chunk corruption is a known issue since the very first releases of MC. My point is that instead of working on improving massive problems like this, Mojang is adding features, licensing plush toys, giving speeches at conferences, and spending their millions on themselves, rather than concerning themselves with their customers. This is the MySpace model of how to doom your company: add bling to your product, spend your money like mad, and resist listening to your critics. We see how well that worked for MySpace.

If Words with Friends or Angry Birds had bad code that wiped out and entire game forever, there'd be a nuclear outrage. But Mojang toadies give them a free pass for something that, in any other context, is fairly egregious from the standpoint of people who buy their product.

I think this deserves its own thread because we're off topic now, but whatever.

Mojang created a game that is based on the idea of building amazing structures. Then the code erases everything you did, so you can't build. See the problem?

Imagine if Microsoft had released Flight Simulator, and the airplanes couldn't .. you know... FLY? Or if physical Lego sets dissolved after you built something? Or if Call of Duty had a bug that when you picked up a gun and pressed the trigger, you turned into a bunny and ate cupcakes while the terrorists shot you to death.

IT'S THE MOST BASIC EXPECTATION OF THE GAME. It's the reason it exists. It's in the effin' NAME of the game! ("Crafting.") That's why its important, and moreso than whether sideways logs are irritating, or whether textures are ugly. I

If you can't "craft" then it's just "mining," which is just digging holes. Yeah, that sounds fun.

I'm not interested in how "hard" it is. That's their BUSINESS, it's what they are supposed EXPERTS in. Sure, it's hard for me, and maybe for you. But we're not millionaire developers that have a gajillion dollars to throw at the problem.

And the fact that they are adding features instead of improving the code IS the problem. Adding NPC characters and witches and bats and pistons don't mean a thing IF THEY DISAPPEAR AFTER A CRASH.

I get that you like the game, but sometimes liking something means telling the creators what's wrong with it, so that it gets better. As a paying customer, you actually have that right. If you don't want to exercise it, fine, but don't diss those of us who do care where our money and time go.

(And I'm betting if your computer broke, you'd be on the line to tech support, rather than just go buy a new one and say "it's too hard for them to fix, so I won't bother them.")

To borrow from Syfaro, I don't remember anywhere it is stated that Mojang can't be criticized by the people who pay them.

Quote from Syfaro

But you can build in Minecraft.

You're telling me that you've never seen a game break a save?

I agree that they need to start fixing bugs rather than adding new features.

What's the point in spending hours, days or even weeks building something elaborate, if a chunk corruption erases it and you have to start over. And you seriously want anyone to believe you would NOT be frustrated by that, and want Mojang to fix it? Seriously? Are you Buddha?

No, games rarely "break saves." There was an outcry over the lack of save game POINTS in many games from the 90's and 00's, and because of consumer frustration and calls for improvement, developers altered their design approaches and now include more frequent save options. This actually led to the invention of the "autosave" concept.

But that's an entirely different discussion.

I really don't understand the argument AGAINST expecting Mojang to improve this. I have my theories, but won't go down that road.

Wacky.

It's not that anyone says that this is a bad idea. They'd just rather have mojang spend their time on something else.
I have NEVER had a game get corrupted, a save broken, by Minecraft. As such, it's a problem that doesn't need to be fixed (for me).

And I'm sure there are a lot of other people in the same boat.

On the other hand, fixing this is not necessarily easy. Since MC runs (primarily) on Windows, and windows makes atomic file operations impossible to do. So you have to develop a pseudo-works-like-atomic scheme that will probably have bugs in it, and it will slow the game down.

I work in an industry that puts rockets into space, so I really don't -- and CAN'T -- buy into the "it's too difficult" argument. Sorry. If Windows is sufficient enough to launch a rocket and dock with the ISS, it should be able to run a GAME.

Secondly, if chunk errors are known, and the problem CAN'T be fixed, then a rolling auto-save feature would be the easiest feature to implement. But, as you know, that isn't included in MC either.

Yes, I'm aware -- as I posted -- of third party mod resources. I use MCEdit to "fix" Minecraft's errors, and a third party app to backup the thing every 15 minutes. I have to then manually delete unneeded backups when they start chewing up too much disk space. None of this is ideal, because it basically concedes that (1) Minecraft's code is bad, so you have to (2) search, find and invoke various non-supported tools to get it to use it.

If you aren't a tech guy, and most of MC's users are not, than you'd never know about any of this, and just be stuck when a chunk error occurs, and wondering why they don't fix it.

But seriously, guys. All of you citing the "it's a complicated, imperfect world" mantra -- you NEVER complain when something breaks? The same argument can be made for your CAR -- a far more complicated machine -- so you're telling me that when your car breaks, you don't invoke the warranty? You just get it fixed and then continue to slather your undying loyalty on the manufacturer? You just chalk it up to "complexity"?

If so, why don't people drive Yugos?