- edited description
Destroying block with 'wood' material causes game crash.
CustomStaff version: 0.11.6.
With material = 'iron';
works fine.
Block type is normal.
java.lang.NullPointerException: Ticking memory connection
at cubex2.cs2.block.WrappedBlock.damageDropped(WrappedBlock.java:347)
at cubex2.cs2.block.BlockCS.func_149692_a(BlockCS.java:205)
at net.minecraft.block.Block.func_149643_k(Block.java:1058)
at net.minecraftforge.event.world.BlockEvent$BreakEvent.<init>(BlockEvent.java:83)
at net.minecraftforge.common.ForgeHooks.onBlockBreakEvent(ForgeHooks.java:405)
at net.minecraft.server.management.ItemInWorldManager.func_73084_b(ItemInWorldManager.java:255)
at net.minecraft.server.management.ItemInWorldManager.func_73074_a(ItemInWorldManager.java:151)
at net.minecraft.network.NetHandlerPlayServer.func_147345_a(NetHandlerPlayServer.java:486)
at net.minecraft.network.play.client.C07PacketPlayerDigging.func_148833_a(SourceFile:53)
at net.minecraft.network.play.client.C07PacketPlayerDigging.func_148833_a(SourceFile:8)
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:197)
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:165)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:639)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:527)
at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:186)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:414)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:665)
Comments (8)
-
reporter -
i think this problem has to do with a problem with item drop specifications (ik it happens in creative as well) because it only happens with my blocks which dont "drop themselves" as far as i can tell
-
hmmm it looks like silktouch tools bypass this bug and adding a specified drop does as well, meaning i think that if you give the block a normal drop it should work
-
but disabling the silktouch parameter doesnt for some reason fix it so idk
-
or just set it to drop itself i guess that works lol as in set the drop field to its id
-
this will work
name = "platinumOre"; material = "wood"; stepSound = "stone"; creativeTab = "buildingBlocks";
addToCreative[0] = true; hardness[0] = 3.0; toolClass[0] = "pickaxe"; harvestLevel[0] = 2; drop[0] = "Tutorial:platinumOre 1"; textureFileXP[0] = "platinumOre.png"; textureFileXN[0] = "platinumOre.png"; textureFileYP[0] = "platinumOre.png"; textureFileYN[0] = "platinumOre.png"; textureFileZP[0] = "platinumOre.png"; textureFileZN[0] = "platinumOre.png";
This will not
name = "platinumOre"; material = "wood"; stepSound = "stone"; creativeTab = "buildingBlocks";
addToCreative[0] = true; hardness[0] = 3.0; toolClass[0] = "pickaxe"; harvestLevel[0] = 2; textureFileXP[0] = "platinumOre.png"; textureFileXN[0] = "platinumOre.png"; textureFileYP[0] = "platinumOre.png"; textureFileYN[0] = "platinumOre.png"; textureFileZP[0] = "platinumOre.png"; textureFileZN[0] = "platinumOre.png";
-
The bug seems to occur when you add a metadata on the dropped block ID.
-
repo owner Does this still happen in the most recent version?
- Log in to comment