Draco18s

#1: You're wrong, it's 3 values, not four. #2: No integers are present, see #1: you're wrong, its 3 values not 4. #3: 1, 1, 0 is not invisible, it is yellow: Ergo yes, you're an idiot. The reason it isn't showing up has nothing to do with the color values, but the fact that you're moving them around by manipulating the Z position.

http://minecraft.gamepedia.com/Sapling#Block_state The 4th bit of the metadata component number is the "stage." Saplings need to receive two block updates in order to turn into trees, rather than 1. That bit stores whether or not its already "grown" once (it's similar to crop's AGE state value). The bitwise operators are just a fast way of composing and decomposing the state into/outof metadata integers.

Oh jesus christ. First, the color arguments are only 3 values, not 4. The -2 there is not part of your color values. It's part of your "position Z" argument. Second, -1 and 0 are functionally identical. Color values range from 0 to 1 as a floating point number and are clamped to this range. Third, you didn't "find" green. You threw random numbers at it until green occurred which everyone else here could have told you (and did, actually) that green is 0, 1, 0.

Yellow is yellow that's why they call it that goofball Your computer screen does not contain yellow pixels. It contains RED pixels, GREEN pixels, and BLUE pixels. In order to display yellow it turns on both the RED and the GREEN pixels. Hence: I am now muting all of your posts because you're a bloody idiot.

You want what to do the thing you said? You want an item that activates your 9th hotbar slot? A block? An event?

Yellow is RED + GREEN. https://en.wikipedia.org/wiki/Additive_color

Funnily enough, I was actually contacted about working on the XBox version of Minecraft. If it weren't for the fact that my C++ skills are virtually non-existent I'd have taken it.

Oh. I know why him removing ITileEntityProvider "erases his data." He doesn't have @Override marked and/or isn't dealing with the IDE error involved when he removes the interface. So he's not overriding the correct method, so when the game runs it treats the block as not having a TE.

We posted at the same time. Anyway. The annoying thing I find about IItemProperties is that you will end up with a bunch of model json files (I much prefer blockstate files in this regard). I haven't found a way to just "give it a different texture" as the base model file (e.g. this one* in my own mod), the format is such that it expects a "model" tag, not a "texture" tag. I tried just supplying a new texture and it threw a Missing Model at me for my efforts. I think it has to do with the fact that an item model is still made out of baked quads, so in order to "change texture" you're actually just displaying a different model (which was run-time generated from a pre-specified texture in that model file). *The "time" string should be changed, but as I was working from the vanilla Clock as a starting point I haven't changed it yet, it's just the name of the property that was created. In this case it should be "rainfall" as it is arbitrary, but needs to match.

As I've found it large comes down to "if it's been a few days, post a comment asking why it's not been accepted." The entire process is ungodly tedious with several points of failure that it is very easy as a programmer to overlook and which Lex will come along and go "You did X wrong" and then proceed to mark every occurrence with "..." as if you're somehow only barely intelligent. The "how to do this properly" list of guidelines is very sparse and doesn't teach you how to look at the patch file and find these problems on your own. Took at least four rounds of review before I fully understood how I was supposed to be doing things. Or in one case for me, "rejected because it alters vanilla behavior" which I thought was the whole point (as opposed to "rejected because you should have gone about it in by doing X instead of Y").

BreakSpeed seems like the one to use to me. But again, what are you trying to achieve, not how you plan to code it, but what you want to happen from the player's point of view as he's playing the game. e.g. Goal: "If the player tries to mine coal with an iron pick, it starts a fire in a random nearby tile." Code: "I want an event that lets me check the player's held item so that..."

Skipping over the "where to start" because don't. You will not find Forge-specific details on starting to coremod. There used to be slight hint here and there, but the Forge team is working to make it so that coremodding is not needed at all. Instead, make a pull request to get the change you want implemented into Forge itself. I recently did that myself. On to the other question, alternatives: Block/Item substitution OreDictionary ("requiring pistons in recipes") or outright modifying the list of recipes to find entries that don't use oredict recipes. Events - almost everything you'd want to be able to do as a result of coremodding has an event. If it doesn't: Make a pull request

You may have to combine models as well, which is doable,

Your TE's constructor must take 0 parameters or it will be unable to be recreated when the game is loaded from disk.

world.getTileEntity for one.... You were told already how to do the other...

It's a method you haven't overriden, therefor it exists in one of your class's parent classes.

Entities have a UUID field. Get it. Save it into a field of your TE.

Yes, that change would indeed make it spin faster. Because math.

Also, don't create your own PropertyDirection, use the one from BlockDirectional

Also, why this? for (Field f : Items.class.getDeclaredFields()) One shouldn't have to use reflection to register blocks/items/models IMO

Actually, that was Dropbox. http://superuser.com/a/1131164/528962

In your IDE you can look for classes that extend the Event class from forge. Right Click -> Open Type Hierarchy

Oh sorry, you were right the first time. I didn't realize the event was declared as a static class inside the OreDict. What's your problem?

public void OreRegisterEvent(OreRegisterEvent e) { }

https://mcforge.readthedocs.io/en/latest/events/intro/