New onItemUseFirst issue.

[rich1051414]

If you return true to cancel a block's activation, it also prevents onItemUseFirst from running on the server entirely, you can reproduce this like this. Make a generic item and override onItemUseFirst, do a System.out.println(FMLCommonHandler.instance().getEffectiveSide()) then return true. It will only say client.

 

Do it again only returning false and it will return client and server, but then the blocks menu will activate.

 

Surely this is not intended, The server SHOULD cancel the activating block, but it shouldn't cancel the items onItemUseFirst as well(or maybe the client is prevented from sending the packet)...

 

I understand that System.out.println() could be reporting wrong, BUT I have other methods called from it, and those also do not run server side. When I call functions before returning true that should run both sides, it seems those are also only working client side, like playing sounds. When I call the exact same function from OnItemUse, the sounds work, but from OnItemUseFirst, they do not.

 

Edit: OH i see the problem, the function is triggered by theItemInWorldManager.activateBlockOrUseItem, and returning true prevents the server from going into any item use calls... God knows why OnItemUseFirst isn't simply ran on both server and client, and it can see for itself whether or not to activate the block... It's not a problem to force it to client side unless it is returning false from the method itself

 

I solved it by just sending a packet and doing the server stuff from my packet handler.

[LexManos]

Its working as intended, you need to undertstand that it compleetly prevents any further processing, which means the server doesnt event get told the user did anything if you cancel it on the client.

So, just work with it.