Animefan8888

You don't have to add a constructor to your Item class you could simply do new Item().setRegistryName().setCreativeTab().setUnlocalizedName()...

There are many. I know TInkers Construct adds their own.

Yes I know what your problem is I even said it earlier. " And I wonder what to do if there is no parameter and you are calling one with a parameter in it. "

Does it just say quote with an arrow next to it? Click the arrow. Or you are using a very old browser, but it says "This is the support section for those modding with Forge. Help with modding goes in here, however, please keep in mind that this is not a Java school. You are expected to have basic knowledge of Java before posting here."

You didn't answer the first question. And I wonder what to do if there is no parameter and you are calling one with a parameter in it.

A furnace works ultimately very simply, especially with IItemHandler. A furnace simply needs to know if it can cook the item in question(is it part of a recipe/does it have fuel/does it have room for the result). This can be done very easily. You need a method that burns fuel if it can and needs to while also checking if it has fuel. You need a method that checks if the item in the input slot is part of a recipe. You need a method that checks if there is room in the output slot(s) (this can be done using IItemHandler.insertItem(slot, item, true) if it returns an empty ItemStack then there is room for the output). Next you just need to implement ITickable and in the update method check all of the above and once enough time has passed complete the burning by calling IItemHandler.insertItem and IItemHandler.extractItem.

Do you know Java? If not If you do then do you have a class called ItemBase? And if you do does it have a constructor that has a String parameter in it?

They should also be using a capability. The only possible way to ensure that the capability stays in sync on an nbt change would be to constantly verify with the server and then send an update packet back to the client. Though as I said they should also be using a capability for ItemStack data.

This could cause problems based on how you are doing it, hopefully you are still basing actions off of the servers data. Define updating the NBT.

Try returning true in isAmbientOcculsion

It depends on what you mean by re-creates and how you are editing it. ItemStack capabilities are not synced. How are you updating your capability data?

Does your entity move as a normal entity or is it more like a Shulker? If the later take a look at EntityShulker, if the former still take a look at EnttiyShulker.

I would use player.addItemStackToInventory It depends on what you mean by better ItemHandlerHelper.giveItemToPlayer will drop the item as an entity which is useful in most cases, but it also wraps the PlayerInventory in an IItemHandler and handles the input that way.

Is just a wrapper around So either works, one is just less writing.

You're doing it for your block, not others mods.

After looking at your silkspawners mod on github it turns out you have your own mob spawner block that can modify what you want on the client in the onItemUse method.

Then submit the event to forge on github. You could just send a packet updating the client.

Why do you need a client side block place event?

No Minecraft won't look for any variants it is not told about. Try creating a new world.

1.7.10 is not supported on this forum please update if you wish to receive help. This thread will later be locked by a moderator.

Because of 1.13 though you may have figured that out. Post your updated code, including its file path.

Is it the full cube or does it have your model. I am assuming it doesn't have your model, was this from a fresh run of the dev environment.

There is both a PlayerLoggedInEvent and a PlayerLoggedOutEvent please use those instead. ServerDisconnectionFromClientEvent is only called when the server disconnects a player, and ClientDisconnectionFromServerEvent is only called when the Client disconnects from the server. It is a little bit of a play on words, which one is doing the disconnecting.

This event is fired only on the server.