Draco18s

If you want a tiny fraction of offset, use float.epsilon. 0.01 will actually be noticeable. It's about 1/6th of a texture pixel.

Oh gosh, how simple. Oh boy howdy, how easy. If only the documentation matched. Oh wait it does. (I will note that I haven't messed with the code in like 3 years and I am sending and not verifying the TE pos)

https://mcforge.readthedocs.io/en/latest/networking/simpleimpl/#sending-to-the-server

No, it's handled by Tags now.

Basically you can't.

Buttons are client side only, you must send a packet to the server saying "this button was pressed."

Really what happened was that this parameter you were passing: worldIn.setBlock(pos, state, ... ); was this: BlockState state = worldIn.getBlockState(pos); when it should have been this: ModBlocks.SCORCHED_EARTH.get().getDefaultState()

The Forge team can't support every version of Minecraft in-perpetuity. No software company does that with their software. Forge has decided that they will support the most recent major version (1.17) and a single LTS version (1.15) 1.12 is 4 years old at this point.

Well, no. You need to be able to cast the thing you want to register (in this case, a block). You can't make a RegistryObject<Item> store a new Block() for instance. That's precisely what the new keyword does.

This, by the way, doesn't need to be strictly typed to your class. You could just use RegistryObject<Block>

Why not?

Being a professional software developer, no, a "coder" is "someone who codes." A software developer is the professional term. At best, you're a script kiddie.

Yes

False. Your first thread on this very forum on this topic was this one in which you were already under the assumption that items and blocks were done via datapacks. The first reply even says "no you don't" and linked you the relevant documentation. Unless you mean this post which was referring to the blockstate, model, and loot table files which was already in reply to your complaint that datapacks are a hassle.

Having done this in the past, stepOn is not super reliable, it'll pick up about 2 in every 3 blocks (less if you're sprinting). And if you want it to break as if it was harvested and drop items, you'll need to call the drops function (which I don't know the name of off-hand).

Oops, you were correct. I was having trouble finding the recipe and searched the entire repo. It did have the correct path in it though. Anyway, I see you got it.

That's the wrong location. /resources/data/create/advancements/recipes/create.base/crafting/kinetics/cogwheel.json https://github.com/Creators-of-Create/Create/blob/mc1.16/dev/src/generated/resources/data/create/advancements/recipes/create.base/crafting/kinetics/cogwheel.json

Or more accurately, Create is overriding yours. It's a "who ever goes last wins" situation. You should change that from "BEFORE" to "AFTER"

Or stairs, slabs, portal frames, scaffolding, walls, fences, composter...

True enough. I think tags would be sufficient, but I also haven't looked at what vanilla did to make it work.

Note: D7 here means to place the recipe json at the same relative directory as the other mod's file. So if the other mod's ID is "createcraft" then you'd place the recipe at /src/main/resources/data/createcraft/recipes not at /src/main/resources/data/yourmod/recipes

If the top face isn't solid, it won't get snow. But you also wouldn't be able to place torches or redstone on it.

Yes

Forge PR. But if someone's going to do that, make it a freaking tag like all the other isXYZ methods.