Basically if I call

sendUpdates()

(see below) every so often, I can be reasonably assured that the renderer will update, just not instantly.

 

e.g. I can create a timing variable and call the method every 100 ticks and that results in the model changing within 5 seconds of when it should.

 

	private void sendUpdates() {
	markDirty();
	worldObj.markBlockRangeForRenderUpdate(pos, pos);
	worldObj.notifyBlockUpdate(pos, getState(), getState(), 3);
}

 

If I call this method both after any time the TE changes its own contents (i.e. "smelting" an item into another item or consuming "fuel") and not every few seconds, then it also seems to work and pretty much instantly.

 

However, when inserting items via a hopper the update is not always applied.  That is, for inserts from the sides into the input slot, the update is instant.  When inserting from the top (for fuel) the update never occurs (unless the fuel is consumed, which also sends an update, and that one works).

 

If I try to delay all updates by 1 tick (so that all methods that would send a synchronization packet merely flip a boolean and then at the end of onUpdate if that boolean is true, call sendUpdates() and set the bool to false), then I still get the same behavior: inserting from the sides updates instantly (1 tick delay) inserting from the top never updates (and in fact, fuel consumption doesn't update this time either).

 

I don't get it.

 

http://pastebin.com/PKMvsdJu

You may want to store a reference to the

TileEntity

in

ItemLeatherHandler

and override

ItemStackHandler#onContentsChanged

to trigger the update packet.

 

I'm not entirely sure why your current code isn't working properly.

You may want to store a reference to the

TileEntity

in

ItemLeatherHandler

and override

ItemStackHandler#onContentsChanged

to trigger the update packet.

 

Its the salt that's not working correctly, but I'll give that a shot.

 

Faux Edit:

Nope, that doesn't help either. :\