Happens only with Dedicated Server (last test).
Using the following (often used) construction:

*A highly overclocked machine is cooled by an WaterCooler; which is automaticly refilled with water buckets (this part works correctly).

At Server side anything is correct and the System works.

But at client side:
You have the last known state of the WaterCooler, normaly by looking into the GUI. So its smoking a while and consume the water (client is never informed about the automatic refilling). At this point no big problem, but if you look into the GUI or Upgrade GUI the system burns down in some seconds and it seems the machine is inoperable (also in normal GUI). So at all you are not able to work with the overclocked machine, unless you look into the WaterCooler every ~ 30 Seconds.

Also found out why the mecanism steam is not working.
https://github.com/aidancbrady/Mekanism/blob/1.10/src/main/java/mekanism/common/MekanismFluids.java#L33

https://github.com/CovertJaguar/Railcraft/blob/mc-1.10.2/src/main/java/mods/railcraft/common/fluids/RailcraftFluids.java#L35

Mekanism uses "steam" and railcraft uses "fluid.steam"

The only real problem is the items are gone at client in Chipset Gui and nothing more ?

Ok add to the problem, that it schould allways smoking, if it cools a machine.

So Other Idea: We don't need the amout of fluid, only on and off.
So we can use a meta state for on (can cool and is smoking) and off (no smoke, empty, no cool).
The state is changing if the watercooler gets empty(0mB) and full(>=1mB)

I dont like this way of "fixing" at all., because if a steam mod is installed this would no longer work or result in an blockstate update spamming.

solved in 123