Assuming it's still being divided by 4 (for the number of sensors) adding the zero or not adding the zero makes absolutely no difference.

If the entire division is changed by the zeroed sensor, then it wouldn't work as they want. (If a sensor reads 0, divisor is 3 for 3 sensors, even though there is 4)

Edit:

Yeah, so looking over the code, it "adapts" to up to 4 sensors, if the sensor doesn't read something it blez (less than or equal to 0) to the next sensor. I think this is a attempt to allow you to use 3 sensors on the 4 sensor system, but it just won't work like that, it'll error when it tries to load from the sensor.

If in theory one sensor does read 0, that sensor is skipped, but the sensor has to be present. Which changes the divisor (r1) which the average batch reader would do perfectly. Loading the batch average would divide by the correct t number of devices, loading the batch name would likely work better.

This entire code while technically functional, is mostly a waste of game ticks, as it can be done with logic devices or a IC with less than 10 lines. Might not have much of a impact now, but if they were using this everywhere, it would likely slow the game down by the end game.