Multimeter changes about createaddition HOT 3 CLOSED

Yeah, I Agree, the reason the multimeter prints in chat and why the Goggles don't show charge is because of network syncing and limitations of the Goggles. The Goggles isn't coded to sync every tick, it just reads whatever data is already on the client. This means that the server would need to figure out when a player is looking at a block then sync that data.

from createaddition.

I think that it could be made using simple probing mechanism on the client - for example every x ticks/seconds, whenever player is looking at a block that has FE support he sends a probe to the server requesting measurement start. He will send those requests in some specified intervals for example once every half a second.

On the other side whenever server receives a request to measure specific block, it creates a Measurement object and stores it's value in some map with <block coords, Measurement> (block cords or some other method of identification). Measurement could be a simple object containing last reading, watchdog timer and a list of subscribers to notify. Each time a request for block measurement comes, a watchdog is reset and current measurement is returned. When watchdog reaches 0 the <block, measurement> pair is removed from map. Watchdog should have bigger timeout than frequency of client sending probes, to prevent constant allocations in realistic scenario. From the rough sketch of that it's easy to see, that measurements map could be shared globally among players and reused - the only thing that changes dynamically is a subscriber list for measurement.

Additionally if by any chance googles could utilize the animation from "ponder" mechanic (with the bar filling up), we could play this animation with frequency of player's probing.

from createaddition.

The goggles now do this in 20210625a.

from createaddition.