Allow judge to track which flags are returned

[timparenti]

Lower priority suggestion lifted from dev chat, S18:

Give the head judge checkboxes for the various red/yellow flags, counting from A to (X), based on the number of flags in the game? Optionally have a "simple scoring" mode where each letter has a fixed point value entered in and the console ties the published scores to those values as calculated by the app. Perhaps a further option to just use 1s throughout for linear flag-is-point stuff. Otherwise, if "simple scoring" is disabled, enable "custom scoring" or "hidden scoring" as they exist today.

Consider potential avenues by which the "flags remaining" information (or a summary thereof) could perhaps be securely transmitted to roaming judges, since it is often difficult to tell whether a game is close to ending or is running long.

Bonus points if checking the last flag on either side ends the game.

[michaelfelixmurphy]

For now, I will implement this as a local front end feature. No scoring or syncing. Just a digital chalkboard. We can add MQTT support later as a low priority feature.

…

-Murphy

On Mar 2, 2019, at 11:09, Tim Parenti ***@***.***> wrote: Lower priority suggestion lifted from dev chat, S18: Give the head judge checkboxes for the various red/yellow flags, counting from A to (X), based on the number of flags in the game? Optionally have a "simple scoring" mode where each letter has a fixed point value entered in and the console ties the published scores to those values as calculated by the app. Perhaps a further option to just use 1s throughout for linear flag-is-point stuff. Otherwise, if "simple scoring" is disabled, enable "custom scoring" or "hidden scoring" as they exist today. Consider potential avenues by which the "flags remaining" information (or a summary thereof) could perhaps be securely transmitted to roaming judges, since it is often difficult to tell whether a game is close to ending or is running long. Bonus points if checking the last flag on either side ends the game. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.