Draco18s

In order for full diamond armor to have 8/10 protection, you would need to alter each piece of armor to have less overall protection. The bar is literally a sum of all the pieces worn.

Define "fruit tree." What does this object look like? How does it behave?

Namely because it is unable to do so. The ItemStack doesn't have a reference to the inventory it is in, and is thereby unable to make itself null.

Well, you'd need to do the NBT data on the ItemStack correctly. Unfortunately I cannot locate the documentation regarding this, but it would be available by looking at the WrittenBook item class.

I think it is. I just read a few threads in Modder Support, and when one of them got a new reply, every thread showed the "new" label. When I read the new reply, went back to Modder Support and refreshed the page, the "new" markers dissappeared. EDIT: If you click the "new" button on a post without a new reply, it goes to another thread which does have a new reply. This is annoying the fuck out of me. As soon as I noticed it my immediate thought was, "What'd we do downgrade our forum software?" But Larsgerrits is correct, the new button doesn't even apply to the thread it's next to:

SSP is SMP only running its own copy of the server and with only a single player connected.

Your block gives no shits about metadata other than 0 and 1, which it uses to supply two different TileEntities.

Two random numbers like that would result in less than a 50% I think, but I'm not in a place to so the math. However, that two-numbers thing does get you a different result if you are returning a float (as compared to a uniform random), the Wald Distribution (Inverse Gaussian) uses that method.

There's a reason there's not a BlockUpdateEvent fired when any block runs its update tick method: the sheer number of calls that would be made to the event bus. Reducing this to only redstone powered objects wouldn't really do much. Afterall: do you expect every dot of redstone dust to fire this event?

Make sure to check null. Not all DamageSources have a source entity.

Stop using static variables any class-level variables at all inside your item class.

Yeah no, you're not going to be able to do that because power-able blocks check their neighbors for power. If none of their neighbors have power, they turn off. Creating a "virtual" connection like that would require replacing a block with the Redstone Block (or equivalent).

Presumably the method returns a value, that value being the amount inserted.

Making a recipe handler takes having an existent sample to work from, as the documentation is very limited. In that, have a working one-input-one-output NEI handler https://github.com/Draco18s/HarderStuff/blob/master/src/main/java/com/draco18s/ores/recipes/nei/ProcessorNEI.java

Or use the passed ItemStack to differentiate.

There's an entire BrewingRecipe class now. Take a look at it.

Note that you cannot set the near clip plane to 0. Well, you probably can, I wouldn't expect things to work right though. You can, however, set it very very small. Like 0.001 small. http://answers.unity3d.com/questions/129030/why-is-near-clip-plane-necessary.html As for how to actually do that in MC, I have no idea.

I misread, I read "to 100 blocks" to "by 100 blocks"

Does it use == or instance of? If the former: not easily (you will have to use events and basically duplicate all that code) If the latter: just extend ItemElytra

Support and bug reports. But long story short is you're using the wrong mod version for the version of Minecraft you are running.

It's the camera near-clip plane. I am not sure where it's defined.

Mod entity ids are sandboxed to your mod. Start at 0 and go up for each mob you have.

You have this: this.gatePosition = new BlockPos(pathpoint.xCoord, pathpoint.yCoord + 1, pathpoint.zCoord); You could add: this.gatePosition = new BlockPos(pathpoint.xCoord, pathpoint.yCoord + 0, pathpoint.zCoord); as a separate check.

35 blocks isn't going to make that much difference to the giant 191 block tall mountains. Oh no, 156 block tall mountains! They're still 93 blocks taller than the vanilla extreme hills, which, to be frank, already feel huge when you're looking at them.

That said, making 14 identical (except for color) blocks is easy. You just need a generic Block class that takes in the color parameter as part of its constructor and use a loop.