I'm developing the "ItemEntity" concept, which is TileEntity for Item.

 

Everything was fine, except that I got some problem with Obfuscation of the ItemEntity.

 

The problem was that my ItemEntity and IInventory has the same "markDirty" method, but mine is not being obfuscated.

 

So when the subclass of ItemEntity implementing IInventory got referenced by IInventory#markDirty's obfuscated code, It got the crash: java.lang.AbstractMethodError

 

So, is there any way to force obfuscation for my ItemEntity#markDirty function?

Anyone..?

Sorry, but I really need help on this..

Not sure but I suspect it would be something that would be specified in the build process, maybe in the build.gradle file.  What does your build.gradle look like?

 

Also by the way, what exactly are you doing with the ItemEntity concept?  Sounds interesting, but I wonder if it is something that is solved in some other way.  TileEntity makes sense because blocks are physically placed in the world so you have an idea of all "instances" (not actual Java instances but at least known locations for the blocks).  Items aren't really placed in the world in the same way.  They can be in containers, in your hand, in inventories, etc.  And when there is an item on the ground, it is already an EntityItem.  Anyway, just curious on what you're trying to do exactly,

Thank you, I'll try with the build.gradle file.

+ ItemEntity concept is based on the Inventory World concept, which considers certain Inventory as World.

It has several advantages:

  1. An ItemEntity can know its Position. It is useful for "Inventory Machine", like the ones in my InvWorks mod.

  2. Easier "Per ItemStack Control". You can use itementity similar with tileentity.

    Also, one can make custom inventory check for each itemstacks via ItemEntity.

    But in Forge, you can only control the items in the player's inventory!