I tried to update my FallingSand spawners, but even if I add {block:"minecraft:stone"} in the FallingSand tags, the game crashed when the Entity spawn.
Here's the command I'm using:
setblock ~ ~1 ~ minecraft:mob_spawner 0 replace {SpawnData:{Data:0,Dimension:0,DropItem:0,Motion:[0.0,0.06,0.0],Pos:[562.5,92.5,7.5],block:"minecraft:dirt",Time:0},id:MobSpawner,EntityId:FallingSand,SpawnCount:2,SpawnRange:5,Delay:1,MinSpawnDelay:0,MaxSpawnDelay:1,MaxNearbyEntities:64}
Works fine in 1.7. Using the TileID tag doesn't work too.
Description: Loading entity NBT
java.lang.NullPointerException: Loading entity NBT
at ww.a(SourceFile:222)
at rl.f(SourceFile:1197)
at agr.a(SourceFile:131)
at agr.a(SourceFile:254)
at bpv.a(SourceFile:19)
at bpv.a(SourceFile:14)
at bpv.a(SourceFile:9)
Linked issues
Attachments
Comments 3
This is not a bug, the handling for entities has changed. For whatever reason, although not quiet pinpointed by me yet, the new entity handling system works. I have proven my work by making a spawner as by such methods/commands with mcedit filters, then I put a NEW fallingsand entity in my world. I then copied the NBT data from that sand into the spawner and it works! Give me a few minutes and the new handling will be found! NOTE TO MODS: This is NOT a bug, simply a new system. Please remove this from confirmed status
EDIT: Problem was in the original command syntax is "Block:"minecraft.dirt"" as opposed to "block:"minecraft.dirt"
EDIT #2: Also the block will not spawn without a required player range, ie "RequiredPlayerRange:10" should be on the end of that command
Ok, thanks.
Doesn't crash with
setblock ~ ~1 ~ minecraft:mob_spawner 0 replace {SpawnData:{Data:0,Dimension:0,DropItem:0,Motion:[0.0,0.06,0.0],Pos:[562.5,92.5,7.5],Block:"minecraft:dirt",Time:0},id:MobSpawner,EntityId:FallingSand,SpawnCount:2,SpawnRange:5,Delay:1,MinSpawnDelay:0,MaxSpawnDelay:1,MaxNearbyEntities:64,RequiredPlayerRange:10}
Confirmed, crash report attached.