Draco18s

Same way you make any inventory slot empty.

You haven't done anything to remove the item from the player's equipment slots.

That would also do it

I am not sure how the multistate format works, so I'm going to suggest going the rout of a custom state mapper. I have a value that is only true for some states, otherwise, its ignored. So here's the state-mapper: https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/java/com/draco18s/flowers/states/StateMapperFlowers.java And the resulting blockstate files: https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/resources/assets/oreflowers/blockstates/oreflowers1.json https://github.com/Draco18s/ReasonableRealism/blob/1.12.1/src/main/resources/assets/oreflowers/blockstates/oreflowers1_tall.json Notice all of the "oreflowers:items/na" entries? Those will never ever be seen. I know that, but Minecraft doesn't, and so rather than specifying a bunch of state pairs that'll never be used, I used the one value to split the states out into two different files. You'd do the same thing on your FEMALE value, and the two files will be 99% the same, but one will have the "stage 7" be different. Don't forget to register your custom state mapper on the client.

You need to handle each character pair as a separate object, then combine them later. e.g. deg = new String(charPair1) + new String(charPair2);

More or less. In this case, yes. However, blockX >> 4 and blockX / 16 are not the same. For example: -280 >> 4 = -18 -280 / 16 = -17

Sure. Save the file as UTF-16. Or you can do it like this: int codePoint = 0x1D3C; char[] charPair = Character.toChars(codePoint); deg = new String(charPair);

Well, for one, that's not how you compare item stacks.

Yes. Vanilla obviously does it, so the answer is yes.

Here: If a method isn't working, you need to place a break point in it so you can figure out why. If your breakpoint is never hit, even when you do the thing that should call it, then your method is never called and you need to figure out why.

No. Yes: https://github.com/Draco18s/ReasonableRealism/blob/master/src/main/java/com/draco18s/hardlib/client/ClientEasyRegistry.java#L167

You know you can just call item.getRegistryName() right? ModelLoader.setCustomModelResourceLocation(item, 0, new ModelResourceLocation(item.getRegistryName(), "inventory")); Also means you don't need the id parameter. This is pointless. All it does is this: Which you could have done there in the first place: private static <T extends Item> T register(T item) { //other code main.proxy.registerItemRenderer(item, 0); } Also, you don't need this generic: private static <T extends Item> T register(T item) { This: private static Item register(Item item) { Works just fine

And yes, you can create your own conditions. And yes, that class looks hellishly complex. The cool thing is, 99% of it is the same for all conditions.

Less trolled and more me just not paying as close attention as I should have been.

I'm a derp >..<

Which is fired for EVERY key that's pressed EVERY time its pressed. You should not use it. Use the ClientTickEvent

It's a ghost item. You spawned it on the client. Because only the client knows about it, it can't be picked up (server action) or killed (server action). If you log out and log in again, it'll be gone.

Ok, different problem than I thought you had. Good, you posted code.

There you go then:

You don't need to do anything except reduce the stack size on the server.

You're on 1.12. You don't need to "delete" stacks. A stack with 0 size is already the same as air. If "the inventory updates and the item comes back" thing is happening, that sounds to me like you're only subtracting 1 from the stack size on the client and not doing it on the server. So when "the inventory updates" (cough, gets an update packet from the server) the item "reappears" again because it was never gone in the first place.

Where is this called?

Where is this called?

That's not the debugger, that's the log. http://www.vogella.com/tutorials/EclipseDebugging/article.html

Have you tried the debugger?