I have a machine patterned after a minecraft furnace in which I display the remaining burnTime in the Gui. I have changed all related 'short' in my code to 'int' (even in Nbt code).

 

When I run it on Single Player the Gui works as desired, displaying the progression of values 20000, 40000, and 60000.

 

When I make a Server and run Multiplayer, my machine's Gui displays 20000, -25536, -5536.

 

Why would the server make it behave differently?

 

int myBurnTime = 60000;

 

I was using Integer.toString(myBurnTime) when I display the value (worked fine on client, not on server). I tried String.valueOf((long)myBurnTime)--it had the same problem.

 

Does anyone know if there is some reason the server-side values would act like 'short' while the client-side values continue to act 'int'?

We need to code to help you. Most likely a packet problem.

If it is a packet problem, where would that code be? (I have not written any "packet" code.)

 

What do you need to see? My TileEntity, my GuiContainer, my Container, my Machine class? Does it have anything to do with Nbt-related code?

 

by packet problem i mean the server and client are out of sync but yes the things you listed we need to see its maybe just a thing where MC casts it down to a short to send the data over the TE update packet.

Thank you.

 

The TileEntity is here:

https://github.com/Justmakinmusic/Diamerald/blob/1.7/src/main/java/jmm/mods/Diamerald/tileentity/TileEntityGrinder.java

 

The other pieces are under jmm/mods/Diamerald.

I have no idea what the problem is note right now I am on moible device not on pc I will get back here later.

Thank you. I was poking around there and hadn't yet looked at the contract. I am not at my terminal right now, but i don't remember getting a warning about possible loss of precision going from 'int' to 'short'.