While fiddling with the latest weekly update (12w34b), client crashed and now the world I was on shows Internal Server Error while trying to load it. The client crashed while changing the buff granted by the beacon block.
I've reverted back to the most recent release of the client. I've used MCEdit to remove the offending blocks and it still gives the error.
lol next patch won't be in couple of months , you can try using another version the 1.3.2
I switched back to 1.3.2, which completely removes the blocks and should remove all associated data with them. No joy on that either. Right now my largest world is inaccessable, but I'm not going to go on a tirade about breaking it while playing with a beta version.
Really not sure what else to try.
12w36a also doesn't fix it.
Removing the chunk(s) that contained the beacon blocks also doesn't work. Deleting all the chunks in the entire game world also doesn't work. This is using MCEdit.
Had the error come up a couple times on a world with version 12w39b. Happened twice last night, but the world is still accessible. The old world still isn't. So, no clue. Incidentally it did not generate a crash report.
Crash report from when it gave a server error while I was fiddling with a couple texture mods:
---- Minecraft Crash Report ----
// Hey, that tickles! Hehehe!
Time: 9/29/12 7:21 PM
Description: Exception in server tick loop
java.lang.RuntimeException: Already decorating!!
at wr.a(SourceFile:21)
at wn.a(SourceFile:217)
at yq.a(SourceFile:460)
at gx.a(SourceFile:152)
at xo.a(SourceFile:650)
at gx.c(SourceFile:90)
at gx.d(SourceFile:100)
at vs.e(SourceFile:258)
at vs.b(SourceFile:210)
at vs.a(SourceFile:199)
at vs.a(SourceFile:2503)
at vs.a(SourceFile:1749)
at vs.a(SourceFile:1851)
at vs.a(SourceFile:1905)
at vs.b(SourceFile:1765)
at vs.w(SourceFile:1716)
at vs.x(SourceFile:1728)
at xo.m(SourceFile:820)
at gx.a(SourceFile:151)
at xo.a(SourceFile:656)
at gx.c(SourceFile:90)
at gx.d(SourceFile:100)
at vs.e(SourceFile:258)
at vs.b(SourceFile:210)
at vs.a(SourceFile:199)
at vs.a(SourceFile:2503)
at vs.a(SourceFile:1749)
at vs.a(SourceFile:1851)
at vs.a(SourceFile:1905)
at vs.b(SourceFile:1765)
at vs.w(SourceFile:1716)
at vs.d(SourceFile:1928)
at vs.b(SourceFile:1521)
at gy.b(SourceFile:95)
at net.minecraft.server.MinecraftServer.r(SourceFile:458)
at net.minecraft.server.MinecraftServer.q(SourceFile:402)
at baj.q(SourceFile:117)
at net.minecraft.server.MinecraftServer.run(SourceFile:336)
at et.run(SourceFile:562)
Relevant Details:
- Minecraft Version: 12w39b
- Operating System: Windows 7 (x86) version 6.1
- Java Version: 1.6.0_35, Sun Microsystems Inc.
- Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Sun Microsystems Inc.
- Memory: 511547944 bytes (487 MB) / 1037959168 bytes (989 MB) up to 1037959168 bytes (989 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- Is Modded: Very likely
- Profiler Position: N/A (disabled)
- Player Count: 0 / 8; []
- World Pyramid2 Entities: 0 total; []
- World Pyramid2 Players: 0 total; []
- World Pyramid2 Chunk Stats: ServerChunkCache: 0 Drop: 0
- Type: Integrated Server
I've reverted back to the most recent release of the client. I've used MCEdit to remove the offending blocks and it still gives the error.
-
View User Profile
-
View Posts
-
Send Message
Retired Staffbackup your world first , if you don't want to lose anything
Tried it, no luck, on either world I've managed to screw up. Next patch may fix it.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffI switched back to 1.3.2, which completely removes the blocks and should remove all associated data with them. No joy on that either. Right now my largest world is inaccessable, but I'm not going to go on a tirade about breaking it while playing with a beta version.
Really not sure what else to try.
12w36a also doesn't fix it.
Removing the chunk(s) that contained the beacon blocks also doesn't work. Deleting all the chunks in the entire game world also doesn't work. This is using MCEdit.
Crash report from when it gave a server error while I was fiddling with a couple texture mods: