Draco18s

1) generate a random number 2) do something with it

1) generate a random number 2) do something with it

It gets called if the player is inside the 1x1x1 standard volume of the block (your block would need a bounding box smaller than 1x1x1 for this to occur). You would need to either: a) schedule tick updates (say, every 10 ticks) and check in updateTick (and reschedule the update) b) not schedule ticks and rely on random ticks (about once a minute) c) use a tile entity and check every tick A is the best solution.

It gets called if the player is inside the 1x1x1 standard volume of the block (your block would need a bounding box smaller than 1x1x1 for this to occur). You would need to either: a) schedule tick updates (say, every 10 ticks) and check in updateTick (and reschedule the update) b) not schedule ticks and rely on random ticks (about once a minute) c) use a tile entity and check every tick A is the best solution.

No no no, leave the collision box alone. You want to getEntitiesWithinAABB(thing I said)

No no no, leave the collision box alone. You want to getEntitiesWithinAABB(thing I said)

The only reason Mojang has two blocks for the furnace (redstone ore, redstone lamp, redstone torch....) is because they weren't clever enough to figure out how to get blockstates to change lighting.

The only reason Mojang has two blocks for the furnace (redstone ore, redstone lamp, redstone torch....) is because they weren't clever enough to figure out how to get blockstates to change lighting.

1) spawn more particles per tick with horizontal offsets from each other. 2) make the block less than a full block on that side. 3) step 1: get the facing direction step 2: multiply that direction by 3 step 3: make an AABB from the block to this new position

1) spawn more particles per tick with horizontal offsets from each other. 2) make the block less than a full block on that side. 3) step 1: get the facing direction step 2: multiply that direction by 3 step 3: make an AABB from the block to this new position

Don't register your renderers there. You must do it in your client proxy or you will crash the dedicated server. Do not use item.getUnlocalizedName().substring(5) this is awful awful awful, should never be done, and if you got it from a tutorial, go punch that person in the face for being an idiot. This is why setRegistryName and getRegistryName exist.

Don't register your renderers there. You must do it in your client proxy or you will crash the dedicated server. Do not use item.getUnlocalizedName().substring(5) this is awful awful awful, should never be done, and if you got it from a tutorial, go punch that person in the face for being an idiot. This is why setRegistryName and getRegistryName exist.

You need the reference inside the capability not the packet handler.

You need the reference inside the capability not the packet handler.

removeTask(new Task()) isn't going to do anything. It won't find the newly created object in the array, so it won't remove it from the array.

removeTask(new Task()) isn't going to do anything. It won't find the newly created object in the array, so it won't remove it from the array.

Well 90 degrees of rotation applied: 0% to the X axis, 0% to the Y axis, 0% to the Z axis would do precisely nothing.

Well 90 degrees of rotation applied: 0% to the X axis, 0% to the Y axis, 0% to the Z axis would do precisely nothing.

You started a new thread for this. Don't do that.

You started a new thread for this. Don't do that.

Ok, look, a task already exists in the build file. I don't give a shit what it's named. Add from incrementBuildNumber to it.

Ok, look, a task already exists in the build file. I don't give a shit what it's named. Add from incrementBuildNumber to it.

Locate the mod, PM the mod author.

Locate the mod, PM the mod author.

The closest you can get is 3 consecutive rotations: "+x, +y, -x" (all rotations 90 degrees). The problem is I don't think the json supports two rotations on the same axis. This is, of course, assuming that all 6 sides are uniquely textured (e.g. a die) and that +z is uniquely different than all sequences of a single rotation on x, y, or both.