AutoRefs implement several rules checks and send referee commands accordingly. But on the referee side the cause for the command is unknown. Knowing the event that occurred, we can:
Visualize this information with a dedicated scoreboard / field screen app
Compare it in a consensus app
log it for future analysis
I put the new message type into the existing message formats, as they are optional and thus won't break compatibility.
AutoRefs implement several rules checks and send referee commands accordingly. But on the referee side the cause for the command is unknown. Knowing the event that occurred, we can:
I put the new message type into the existing message formats, as they are optional and thus won't break compatibility.