Crash loading world containing blocks with removed data values: java.lang.IllegalArgumentException: Cannot set property
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)
Environment
Dedicated Server, Windows Server 2012 R2 Datacenter, 8 GB RAM, of which 4 GB assigned to Minecraft Server
Linked Issues
is duplicated by18
MC-57369Chests make client crash in multiplayerDuplicateMC-57862When walking around on my old map the game suddenly crash.DuplicateMC-58009Crash when loading chestsDuplicateMC-58035Crash when openning worldDuplicateMC-58075Custom maps using the old invisible ladders will crashDuplicateMC-58095Error when converting map to snapshot map. DuplicateMC-58159Game crashes when in certain places on an old world map DuplicateMC-58165Crash on world load when blocks with removed data values exist (melon_stem:15, cake:15)DuplicateMC-58221Upon logging into world from previous snapshots, game crashes.DuplicateMC-58417Crash - Likely duplicate (Ender Chest?)DuplicateMC-58473Exception ticking worldDuplicateMC-58531SMP map crashes when trying to update. DuplicateMC-58605Crasinh loading my map generated in this last snapshootDuplicateMC-58679Game crashed when trying to play in a world.DuplicateMC-58767Server Crash - Cannot set property ayl{name=facing, clazz=class dt, values=[north, south, west, east]} to down on block minecraft:wall_sign, it is not an allowed valueDuplicateMC-58794Crash on load of beta worldDuplicateMC-59942Breaking a chest in Debug World crashes the gameDuplicateMC-60412Crash with chest and Debug world type (with crash report)Duplicaterelates to6
MC-56893Crash When Placing LogFixedMC-56982Rendering bug with pistonsFixedMC-57876Furnaces don't get placed correctly when a village is generated on server.FixedMC-58300Crash when blowing extended pistons up with TNTIncompleteMC-58437Piston pushing blocks with damage values 6, 7, 14, and 15 causes a crashFixedMC-59850IllegalArgumentException - Crash when rendering MinecartChestFixed
Created Issue:
Minecraft Server crash
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).
Environment
Dedicated Server, Windows Server 2012 R2 Datacenter, 8 GB RAM, of which 4 GB assigned to Minecraft Server
Attachments1
duplicates
relates to
duplicates
Minecraft Server crashjava.lang.IllegalArgumentException: Cannot set property ayl
is duplicated by
relates to
is duplicated by
is duplicated by
java.lang.IllegalArgumentException: Cannot set propertyaylCrash loading containing blocks with removed data values: java.lang.IllegalArgumentException: Cannot set property
Crash loading world containing blocks with removed data values: java.lang.IllegalArgumentException: Cannot set property
is duplicated by
relates to
relates to
is duplicated by
is duplicated by
relates to
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
is duplicated by
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)
is duplicated by
is duplicated by
I'm getting this specifically with Minecart Chests on 14w27a
I'm getting this specifically for Minecart Chests in 14w27a. That attached file has 3 crash reports.
is duplicated by
relates to
is duplicated by
is duplicated by
Not a duplicate of the log-placing bug. More, MC-57470 (Minecraft Server crash, also reported by me) is related to this one.
Basically, both bugs end up in the same exception (unable to set value to ayj because the value is not among the valid blues), but this is the client side, while the other is the server side.
As I explained in the other issue, it tracks down to unexpected/invalid data values due to blocks incorrectly edited into the world.
Confirms, it's the exact same issue as MC-57470 I reported. It has to do with data values for chests, etc. that were valid before Beta 1.8, Beta 1.8 made them invalid, and now 14w25* are making it all apparent by incorrectly interpreting them and mapping them to invalid property values, making the game crash.
Its the ender chest, as its data value was removed. MC-57470
Data value for all of those blocks were removed. MC-57470
That's because you are in a chunk that contains a chest, which had its data value removed. MC-57470
Caused by the chests, which had their data values removed. MC-57470
MC-57470 is your issue. It appears the sign had its data value removed.
Dupe of MC-57470
Dupe of MC-57470
Dupe of MC-57470
Dupe of MC-57470
Doesn't matter about the letters.
Still a dupe of MC-57470, as its data value was removed.
Dupe of MC-57470
Dupe of MC-57470
Not a duplicate of MC-57470, chests minecarts will never have a data value.
Place a minecart with chest, or visit an abandoned mineshaft. Crash.
Chest in world, thus dupe of MC-57470
Suit yourself. They actually do have one.
Dec - 342
Hex - 156
Name - minecraft:chest_minecart
Still a duplicate of MC-57470
Dupe of MC-57470
Dupe of MC-57470
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.
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-56893I 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.
Yeah, it seems it has to do with certain blocks placed before Beta 1.8.1, such as chests. It seems some data values of certain blocks were valid in Beta 1.7.3 and earlier but became invalid later, and it wasn't apparent until now.
I think they should make Minecraft behave more gracefully in this kind of situation, my suggestion would be just assuming default value in case of an unknown/unexpected/invalid value.
Until then though, I recommend loading the world with MCEdit, having it analyze the world, then compare the analysis with MCEdit's internal list of block ID's and data values (MCEdit calls them subtypes) and nothing down any combinations present in the world that are not in said list, and then using MCEdit to replace them with either sane values or air blocks, one ID:data combination by one.
Here is my crash report for what it is worth. I'll go and update to java 8 now, BTW.
---- Minecraft Crash Report ---- // Quite honestly, I wouldn't worry myself about that. Time: 6/19/14 11:02 AM Description: Exception ticking world 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 ou.h(SourceFile:342) at ou.c(SourceFile:179) at net.minecraft.server.MinecraftServer.w(SourceFile:570) at net.minecraft.server.MinecraftServer.v(SourceFile:506) at coe.v(SourceFile:132) at net.minecraft.server.MinecraftServer.run(SourceFile:422) at java.lang.Thread.run(Unknown Source) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Stacktrace: at aya.a(SourceFile:131) at aow.a(SourceFile:425) at ou.h(SourceFile:342) at ou.c(SourceFile:179) -- Affected level -- Details: Level name: Rassilon Beta All players: 1 total; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-845.95, y=14.00, z=1142.53]] Chunk stats: ServerChunkCache: 552 Drop: 0 Level seed: -947871334830476033 Level generator: ID 00 - default, ver 1. Features enabled: true Level generator options: Level spawn location: -152.00,64.00,113.00 - World: (-152,64,113), Chunk: (at 8,4,1 in -10,7; contains blocks -160,0,112 to -145,255,127), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511) Level time: 68702376 game time, 1119050 day time Level dimension: 0 Level storage version: 0x04ABD - Anvil Level weather: Rain time: 138122 (now: false), thunder time: 50589 (now: false) Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false Stacktrace: at net.minecraft.server.MinecraftServer.w(SourceFile:570) at net.minecraft.server.MinecraftServer.v(SourceFile:506) at coe.v(SourceFile:132) at net.minecraft.server.MinecraftServer.run(SourceFile:422) at java.lang.Thread.run(Unknown Source) -- System Details -- Details: Minecraft Version: 14w25b Operating System: Windows 7 (amd64) version 6.1 Java Version: 1.7.0_03, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 709765208 bytes (676 MB) / 1309802496 bytes (1249 MB) up to 2673213440 bytes (2549 MB) JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2867M IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95 Profiler Position: N/A (disabled) Player Count: 1 / 8; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-845.95, y=14.00, z=1142.53]] Type: Integrated Server (map_client.txt) Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.And here is after I updated. Fiddling with render distance seems to induce it BTW, I don't know if that's important.
---- Minecraft Crash Report ---- // Hi. I'm Minecraft, and I'm a crashaholic. Time: 6/19/14 6:42 PM Description: Exception ticking world 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 ou.h(SourceFile:342) at ou.c(SourceFile:179) at net.minecraft.server.MinecraftServer.w(SourceFile:570) at net.minecraft.server.MinecraftServer.v(SourceFile:506) at coe.v(SourceFile:132) at net.minecraft.server.MinecraftServer.run(SourceFile:422) at java.lang.Thread.run(Unknown Source) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Stacktrace: at aya.a(SourceFile:131) at aow.a(SourceFile:425) at ou.h(SourceFile:342) at ou.c(SourceFile:179) -- Affected level -- Details: Level name: Rassilon Beta All players: 1 total; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-887.47, y=78.00, z=1852.25]] Chunk stats: ServerChunkCache: 647 Drop: 0 Level seed: -947871334830476033 Level generator: ID 00 - default, ver 1. Features enabled: true Level generator options: Level spawn location: -152.00,64.00,113.00 - World: (-152,64,113), Chunk: (at 8,4,1 in -10,7; contains blocks -160,0,112 to -145,255,127), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511) Level time: 68716122 game time, 1135559 day time Level dimension: 0 Level storage version: 0x04ABD - Anvil Level weather: Rain time: 90321 (now: false), thunder time: 72242 (now: false) Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false Stacktrace: at net.minecraft.server.MinecraftServer.w(SourceFile:570) at net.minecraft.server.MinecraftServer.v(SourceFile:506) at coe.v(SourceFile:132) at net.minecraft.server.MinecraftServer.run(SourceFile:422) at java.lang.Thread.run(Unknown Source) -- System Details -- Details: Minecraft Version: 14w25b Operating System: Windows 7 (amd64) version 6.1 Java Version: 1.8.0_05, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 211241712 bytes (201 MB) / 835190784 bytes (796 MB) up to 2673344512 bytes (2549 MB) JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2867M IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94 Profiler Position: N/A (disabled) Player Count: 1 / 8; [ox['Infinity_Dragon'/16, l='Rassilon Beta', x=-887.47, y=78.00, z=1852.25]] Type: Integrated Server (map_client.txt) Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.Since my bug was a duplicate posting my servers crash file here
Also this is happening with pistons on my server, not chests.
Confirmed for 14w25b. Is this fixable if you replace the chests in the new snapshot?
The crash seems to be induced by trying to render chests having the data value 0, as João de Camões commented earlier. However, all the chests in my world seem to have data value 0, so how do the previous versions of Minecraft know which way the chests are facing?
This issue is corrected by removing the chests in 14w21b and then placing them in 14w25b
The problem is... was an chest placed by me or is from some dungeons... someone knows in wich version of mc appeared dungeons?
:/ yah i cheked and the problem is on the dugeon... ive replaced then by air, works but now i have empty dungeons. Anyway i keep a backup of my map who knows maybe they fix that.
All chest with data value 0 in my world are dungeon chests, so removing and replacing all those chests just takes to long if I have to locate all of them.
Confirmed for 14w25b ,not only chest and piston, ladder also have problem in my old world.
I have the same issue, but with item frames. I have removed most of them, but there is one left and I can't figure out where it is... I wonder how likely this is to be fixed any time soon, if at all.
Has anyone any suggestions on how to locate problematic objects?
João de Camões: I can see what you're saying, but I just want to be sure. You're talking about using the Fill/Replace tool in MCedit?
If the crash was:
{name=facing, clazz=class dt, values=[north, south, west, east]}java.lang.IllegalArgumentException: Cannot set property ayl
to down on block minecraft:wall_sign, it is not an allowed value
What is the code for a wall sign with the down orientation? 68:something? 68:0? I'm a bit wary about using replace tools and not quite knowing what I'm doing.
Replacing chest blocks with, for example, data value 0 in mcedit replaces chests with all data types, so that wouldn't work.
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)Is this still an issue in 14w28b ?
I'm not sure if
MC-61495which is a ticking entity crash has anything to do with this. HoweverMC-58437which was related to this one was fixed by MogThe issue with Minecart Chests has been resolved
MC-61495andMC-58437are completely different to this crash.