When any client goes to one specific area of the world, the server crashes with an exception (see crash report). No idea what block causes this, but the exception is the exact same as the one I reported for chests in client (and I have since replaced all chests with air using mIDas so there are no chests in the world anymore).
Description: Exception ticking world
java.lang.IllegalArgumentException: Cannot set property ayj{name=facing, clazz=class dt, values=[north, south, west, east]} to down, it is not an allowed value
at axy.a(SourceFile:131)
at aqs.a(SourceFile:232)
at ou.h(SourceFile:342)
at ou.c(SourceFile:179)
at net.minecraft.server.MinecraftServer.w(SourceFile:570)
at nt.w(SourceFile:284)
at net.minecraft.server.MinecraftServer.v(SourceFile:506)
at net.minecraft.server.MinecraftServer.run(SourceFile:422)
at java.lang.Thread.run(Thread.java:744)Linked issues
is duplicated by 18
MC-57369
Chests make client crash in multiplayer
Resolved
MC-57862
When walking around on my old map the game suddenly crash.
Resolved
MC-58009
Crash when loading chests
Resolved
MC-58035
Crash when openning world
Resolved
MC-58075
Custom maps using the old invisible ladders will crash
Resolved
relates to 6
MC-56893
Crash When Placing Log
Resolved
MC-56982
Rendering bug with pistons
Resolved
MC-57876
Furnaces don't get placed correctly when a village is generated on server.
Resolved
MC-58300
Crash when blowing extended pistons up with TNT
Resolved
MC-58437
Piston pushing blocks with damage values 6, 7, 14, and 15 causes a crash
Resolved
Attachments
Comments 24
You're right.
Description: Exception ticking world
java.lang.IllegalArgumentException: Cannot set property ayj{name=facing, clazz=class dt, values=[north, south, west, east]} to down, it is not an allowed value
at axy.a(SourceFile:131)
at aqs.a(SourceFile:232)
at ou.h(SourceFile:342)
at ou.c(SourceFile:179)
at net.minecraft.server.MinecraftServer.w(SourceFile:570)
at nt.w(SourceFile:284)
at net.minecraft.server.MinecraftServer.v(SourceFile:506)
at net.minecraft.server.MinecraftServer.run(SourceFile:422)
at java.lang.Thread.run(Thread.java:744)Please check after the rollout of 14w25b if this issue is co-fixed with MC-56893
I tracked the issue down to unexpected data values. For example, chests edited into the world with data value 0 which the game assumes to mean the block is facing down (which is obviously impossible for a chest).
The crash went away after I removed all such blocks from the world, but I'm going to test 14w25b on the pre-fix world to see if the crash is still there.
Though I still think the game should react more graciously to unexpected data values (setting the values to default in such a case wouldn't be a bad idea).
Also, no block-adding/modifying mods were ever used on the world, only vanilla Minecraft, and the invalid blocks are mostly ones edited into the world by less-experienced players. I am going to make it a server rule now to pay attention to only use valid block values so such issues are avoided in the future.
I am still getting this bug in 14w25b. So it is NOT FIXED on my system.
---- Minecraft Crash Report ----
// Who set us up the TNT?
Time: 6/19/14 9:14 AM
Description: Getting block state
java.lang.IllegalArgumentException: Cannot set property ayl{name=facing, clazz=class dt, values=[north, south, west, east]} to down on block minecraft:chest, it is not an allowed value
at aya.a(SourceFile:131)
at aow.a(SourceFile:425)
at ayv.h(SourceFile:446)
at alu.q(SourceFile:699)
at alu.a(SourceFile:989)
at ub.d(SourceFile:475)
at uv.g(SourceFile:1187)
at uv.f(SourceFile:1430)
at uw.f(SourceFile:315)
at ty.f(SourceFile:120)
at yo.f(SourceFile:35)
at uv.j(SourceFile:1270)
at uw.j(SourceFile:194)
at alu.a(SourceFile:1425)
at ou.a(SourceFile:549)
at alu.g(SourceFile:1403)
at alu.i(SourceFile:1308)
at ou.i(SourceFile:422)
at net.minecraft.server.MinecraftServer.w(SourceFile:578)
at nt.w(SourceFile:284)
at net.minecraft.server.MinecraftServer.v(SourceFile:506)
at net.minecraft.server.MinecraftServer.run(SourceFile:422)
at java.lang.Thread.run(Thread.java:722)
================
-- System Details --
Details:
Minecraft Version: 14w25b
Operating System: Mac OS X (x86_64) version 10.9.3
Java Version: 1.7.0_11, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 3977959768 bytes (3793 MB) / 4151836672 bytes (3959 MB) up to 4151836672 bytes (3959 MB)
JVM Flags: 2 total; -Xmx4G -Xms4G
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Player Count: 0 / 4; []
Is Modded: Unknown (can't tell)
Type: Dedicated Server (map_server.txt)My single player world is crashing shortly after loading with a similar error. This started happening with the latest snapshot 14w27a. With previous version the world loaded normally.
Description: Rendering entity in world
java.lang.IllegalArgumentException: Cannot set property azi{name=facing, clazz=class dw, values=[north, south, west, east]} to down on block minecraft:chest, it is not an allowed value
at ayx.a(SourceFile:132)
at apr.b(SourceFile:425)
at cfb.a(SourceFile:85)
at cfb.a(SourceFile:113)
at cjg.a(SourceFile:116)
at cjg.a(SourceFile:95)
at cjg.a(SourceFile:15)
at cic.a(SourceFile:272)
at cic.a(SourceFile:237)
at cic.a(SourceFile:204)
at cei.a(SourceFile:501)
at cdo.a(SourceFile:1194)
at cdo.a(SourceFile:1121)
at cdo.b(SourceFile:971)
at bmi.ap(SourceFile:886)
at bmi.a(SourceFile:303)
at net.minecraft.client.main.Main.main(SourceFile:120)
How is it a duplicate of that? The log-placing crash issue throws an exception regarding ayi saying it doesn't exist. This throws one regarding ayj saying value "down" is not valid.