Draco18s

Try telling Gradle to look in the place you actually put it (hint: libs is not mods). Adding it to src/api/java means that WAILA will end up inside your JAR

It's a bad idea because Forge hasn't hit the Pre-Init phase yet and it will not let you register blocks and items then.

You should probably call world.notifyBlocksOfNeighborChange(x, y, z, block)

This post makes me lol because it's 4 posts after the solution saying its not possible.

Nope that other mods may still place down the ore. COG works differently and does not fire events to cancel.

This class, if I am remembering correctly, is a modified version of the redstone renderer. https://github.com/Draco18s/Artifacts/blob/master/main/java/com/draco18s/artifacts/client/RenderLaserBeam.java It's got some alterations to handle "corners" as pluses and to render "into" glass and other transparent blocks that don't actually interrupt the beam (but in which it can't occupy due to the cellular automata nature of Minecraft). But it might help you get started.

That would outright destroy your block (which is fine, snow layer does this). If you wanted it to drop stuff (torch, tall grass, etc.) you'd want to make the block break instead.

Or check that the block below does not have a solid top surface. Passions could push a non-air block under it.

You don't have the convert-from-meta-to-state or the convert-from-state-to-meta functions. Vanilla isn't magic.

Pretty much

Make another mod that does something else. You're dealing with a rather complex problem with your idea and you should get the basics down first.

That picture is text, you could have just pasted the text. As for your idea: that sounds a lot like Tinkers Construct. And if you don't know how to do it, you need to do other things and come back to this idea later.

Ok, I said that, because when I was doing my artifacts mod, I had to send a packet from there, even though it did run on the server.

onItemRightClick is a client sided function. You need to use packets and tell the server to move you.

Ha. Good friggin' luck. You'd be better off creating your own stone block and doing a wholesale replacement of the vanilla block. Then you could use the metadata for things like that.

To err is to be human. To really fuck up, you need a computer.

IExtendedEntityProperties

The vanilla Item class already has SideOnly (client) on it. Redeclaring it isn't going to fuck up anything, and neither will leaving it off. Nothing in vanilla code calls getIcon when running a dedicated server. There is NO rendering code on the server, so all rendering related calls are client-side-only and marked as such.

Calling that function isn't going to do you any good (see below). As soon as the entity gets another update tick, its air supply will reset. I told you to use IEEP to track "your" air. Which means replicating the effects of that private function on "your" data. if (this.isEntityAlive() && this.isInsideOfMaterial(Material.water)) { //stuff } else { this.setAir(300); } No matter what you do to the air supply of an entity, if it is not in water, that air supply value will ALWAYS be reset.

You need to store "mode" in the ItemStack's nbt, or it's going to reset every time that function is called.

Its done in the entity class and you can't duplicate the effect you're looking for. Use IEntityExtendedProperties, track the air amount there, and do whatever render effect you want manually.

Possible. As I said, I haven't really looked into it, but you might be best off completely overriding onUpdate (copy all of the code from super and then edit as needed).

Local variable is local.

<Nitpick> Actually the result there would be 0, because neither of those numbers (7 or 15) are floats. </Nitpick>

I don't understand this part. Post this code