Jeremy Jameson

Also, here's the crash report for the most recent.

Here's the latest world I played on (non-customized; just enabled cheats and used creative mode to accelerate my way to a nether fortress) which crashed after a while of battling a bunch of blazes.

I just got the same problem in a third world (this time non-customized - so default dungeon count) - but it didn't crash right away. The blazes shot several fireballs before the game eventually crashed.

Marcono1234, Walter van den Berg:

While I appreciate your suggestions to use third-party tools as workarounds to get the worlds to launch again, I don't much see the point in doing it. It's not that I can't stand to let go of those worlds and start a new one (I already have). It's that I'm not sure what good going into the nether for blaze rods will do anymore if every time I encounter blazes it corrupts the world so it no longer launches.

Kumasasa, it was a customized world but the only parameter I changed from defaults was increasing the dungeon counter to 100. The seed was random (left blank). Unfortunately, I did not note coordinates as I was busily exploring the fortress with the debug info turned off and have no way of getting back onto the world to check (because it never loads).

Marcono1234, I can't seem to compress the folder down to the 10 MB max file attachment size for this forum.

I created a new world with same parameters as before, worked my way through the game to the nether again, and again the world crashed when I started going after the blazes at a fortress. There must be something about the fortresses (blazes?) fouling it up each time.