Count, Minimum and Maximum on purpose

Three living rooms, a gas sensor called “Wohnen” in each. You want to know: how many sensors are running at all? Where is the air worst? That is what Count, Minimum and Maximum are for, with a few quirks.

Count counts devices#

Count returns the number of devices, not a value. The chip still checks the LogicType: if a matching device cannot read it, you get IncorrectLogicType. Every device can read PrefabHash.

lb count SENSOR PrefabHash Count    # all gas sensors on the network

Count ignores the name#

In the game code Count counts all devices with the matching prefab hash. It does not look at the name, not even with lbn:

lbn count SENSOR HASH("Wohnen") PrefabHash Count   # counts ALL gas sensors

If a sensor “Aussen” hangs on the same network, it counts too. For a count by name there is a trick: every device reports its own PrefabHash. The sum over all devices with this name, divided by the hash, is their number:

lbn total SENSOR HASH("Wohnen") PrefabHash Sum
div count total SENSOR              # only the sensors "Wohnen"

Sum respects the name. Without a match you get 0 divided by the hash, so 0. That case is right too.

The weakest link#

Minimum finds the smallest value, Maximum the largest. For the air this means: the room with the least oxygen decides on the alarm, not the average. An average of 21 %, 21 % and 15 % looks harmless at 19 %. The minimum shows the 15 %.

lbn o2 SENSOR HASH("Wohnen") RatioOxygen Minimum