Draco18s

Without an instance you can't call instance methods.

Read the documentation on the @EventBusSubscriber annotation again. There is something missing from your method signature.

Yes, only because you're using a ContainerScreen with does all of the important stuff for you. Never done it.

No, you are: You need to fix these problems, not just add random !isRemote checks and hope it works.

There isn't such a list any more. I'm not even sure I've run across crowbars before (wrenches, sure, but not very regularly). But yeah, I've shoved my own things (dusts, primarily) in under a "forge" tag using the same pattern Forge uses.

Then I suggest looking at the redstone torch.

Blocks don't have textures, they have models. There is no way to do this without using a TileEntity, I'm afraid.

Well, you're breaking a 3x3x3 cube because of your offsets. As I said, if I want a 3x3x1, you need to know either the facing of the player or the side that was hit so you can determine which of the three directions should be only 1 unit thick.

You mean, starting in the center? Your problem is here: AxisAlignedBB grid = (new AxisAlignedBB(pos.getX(), pos.getY(), pos.getZ(), (pos.getX() + 3), (pos.getY() + 3), (pos.getZ() + 3))); You need to subtract 1 from the first three values and only add 1 to the last three. so the range is -1, 0, 1.

If you want to break only 9 blocks (and not 27) you need to know either: a) which direction the player is facing b) which side of the block the player was aiming at

Its because setRegistryName doesn't work properly. If you don't pass your mod ID, Forge has to figure out what the mod ID should be, and it does that by checking what mod is currently "active" in the registration process. But because you've created your items in a static block, Forge cannot know what the correct mod ID is because your static code is being called at an unknown time. Oh, and specifying the mod ID might not be sufficient. Forge does a lot of things in the background and items MUST be created at a controlled time, and if its done too early, unexpected things might break.

Did you fix the two problems I pointed out?

https://github.com/TechnoVisionDev/Witchery/blob/master/src/main/java/com/technovision/witchery/items/ItemBase.java Code Style #4 https://github.com/TechnoVisionDev/Witchery/blob/master/src/main/java/com/technovision/witchery/WitcheryItems.java#L14 Problematic Code #14

Not as much as you'd think. 1.12 and 1.14 are leagues apart.

Its almost like I linked it so the path could be determined...

Not related to your issue, but use a longer mod ID. You have 64 characters of length, use them.

Oh! Hmm. Nope, not sure what's going on.

I'm not sure why you're having a problem. This works: https://github.com/Draco18s/ReasonableRealism/blob/1.14.4/src/main/resources/data/harderores/recipes/ores/iron_dust.json#L10 https://github.com/Draco18s/ReasonableRealism/blob/1.14.4/src/main/resources/data/forge/tags/items/dusts/tiny/iron.json

I think you're going to need to extend the FurnaceRecipe class, not the abstract class.

As an aside, you know that a redstone torch is already a "not block" right?

No, no it is not. https://www.reddit.com/r/raytracing/comments/c08qxz/ray_tracing_is_computationally_expensive_are/ While most "raytracing" things refer to rendering, the same process is applied by physics calculations (of which Minecraft's implementations qualify as). You have to use a very small delta otherwise you're bound to miss corners when moving diagonally at arbitrary angles.

BlockState#get(Property<T>) RayTrace() is going to be worse, because instead of checking at 1 unit distances, it checks at 0.1 unit distances.

The json system explicitly does not support angles other than 22.5% increments.

"result": { "item": "colorfulbuildings:black_cobblestone", }, "count": 8 There are two problems here. 1) You have a comma after "black_cobblestone" that causes a syntax error 2) Your "count" is outside the result block.

You imported the wrong Direction class.