Draco18s

Because it's a right pain in the arse to update them.

That's all vanilla. When a block gets an update, it's given a world object and it's location. world.getBlock(x, y+1, z);//block above

Did you set EntityAIOrder.instance ?

Change ++this.furnaceCookTime; to be bigger. Magic.

Basically the whole of Minecraft is open to you. What is your goal?

And your client proxy?

It depends on what you're trying to render. What are you trying to render? And don't say "a techne model" because that's the visual representation, not what it is.

Whoops, I thought I had one in my code and I checked where I was getting my angle values from (and having radians) but didn't check to make sure I was actually using GL11 for the rotation. You're right, it uses degrees. The Techne model, however, does use radians.

In Techne: File -> Export -> Java Name it something intelligent. Move the file into your source files directories, somewhere intelligent. Refactor the code so it stops throwing errors (Techne assumes that you plan to put this file in the net.minecraft.client.entities package, which is Wrong with a Capital W, so it throws a ton of errors that are easy to fix, provided you know anything about Java). Register a new rendering doodad as appropriate for the kind of model you wish to render in your client proxy. Bam, done

The rotation degrees are also in radians, not degrees.

I get thrills out of the challenge. <3

I've also had issues with checklight, and IIRC, there was a fix in Forge "a while back" (1271?) that fixed an issue with it. Might want to update Forge and see if it goes away. Also, I've never seen "root.root.[...].root" like that before.

Ah well. How could we have possibly helped you, then?

player.cameraPitch is definitely the wrong thing. You want player.getLookVec() and call world.rayTraceBlocks(...) with it (before the block is set to air) and that will tell you what side it intersects. You'll have to figure out which of the two parameters is the player's location and which is the vector to trace.

Uh, you set the block's harvest level to a larger integer than 3? Seriously, there is nothing in the code saying you can't do that. You just won't be able to harvest them unless you also create a tool material with a corresponding harvest level.

Technically speaking, there is a function call to the Block class when a block is placed into the world by any form of World.#setBlock: Block#onBlockAdded(World, int, int, int). It's called from Chunk#func_150807_a, which is responsible for actually changing the block storage arrays. But that's extremely generic and won't tell you anything about having been pushed by a piston.

That's....a tick handler.

Doing such things is above your skill level as the things you want to modify aren't publicly accessible and you would need to inject new code into some places, so even Reflection won't be enough, you'll need ASM. And ASM is a dark, uncaring abyss.

That sounds like it works pretty well. Glad you figured it out.

I've been pretty lazy about updating my dev-environment-forge. I was likely doing a lot of my screwing around with keyboard stuff on 1180 which would, in fact, not have that change.

Ladders are fairly easy, redstone is super complicated, as each side of the redstone dust (that is, the connecting/not connecting edge) is rendered separately.

ClientKeyHandler.up.getKeyCode() ClientKeyHandler.down.getKeyCode() Wut. I had some issues with that, actually. And yes, 1.7.10 here. Do you know if it was a specific Forge version?

Its amazing what kind of information you can convey in your opening post, and how a lack thereof doesn't result in useful replies. Here's what I did when I needed key-up and key-down (specifically, a key bound to an existing option). //client-side event handler @SubscribeEvent public void tickStart(TickEvent.ClientTickEvent event) { EntityPlayer player = Minecraft.getMinecraft().thePlayer; if(player != null) { int jumpKey = Minecraft.getMinecraft().gameSettings.keyBindJump.getKeyCode(); boolean sendPacket = false; boolean state = false; if(jumpKey >= 0) { sendPacket = HazardsEventHandler.instance.setPlayerSwimming(player, Keyboard.isKeyDown(jumpKey)); state = Keyboard.isKeyDown(jumpKey); } else { jumpKey = Minecraft.getMinecraft().gameSettings.keyBindJump.getKeyCode()+100; if(jumpKey >= 0) { sendPacket = HazardsEventHandler.instance.setPlayerSwimming(player, Mouse.isButtonDown(jumpKey)); state = Keyboard.isKeyDown(jumpKey); } } if(sendPacket) { PacketBuffer out = new PacketBuffer(Unpooled.buffer()); out.writeBoolean(state); CtoSMessage packet = new CtoSMessage(player.getUniqueID(), out); UndergroundBase.networkWrapper.sendToServer(packet); } } } You'll not that there are packets involved.

Key event handlers.