Monday, July 11, 2022

Proposal: Ready Or Not

Reached quorum 6 votes to 0. Enacted by Kevan.

Adminned at 12 Jul 2022 15:03:53 UTC

If Proposal: Start Your Engines, Proposal: Scrapheap Challenge and Proposal: Big Flipper were all enacted, in the rule Bouts, change “Operators have a Readiness, which is publicly tracked, which may be either In the Workshop or Ready, and which defaults to In the Workshop” to:

Operators have a Readiness, which is publicly tracked, which may be either Workshop, Ready, Staging, or Set, and which defaults to Workshop.
* When an Operator’s Readiness is Workshop they may set it to Ready at any time
* When an Operator’s Readiness is Ready and they are named in an Announcement Post then the Announcer should set their Readiness to Staging
* When an Operator’s Readiness is Staging then they may set it to Set at any time
* When an Operator’s Readiness is Set and they are participating in a Bout then the Announcer should set their Readiness to Workshop

Set the Readiness of all Operators to Workshop.

Comments

lendunistus: he/him

11-07-2022 12:28:10 UTC

you should define what a “legal value” is, since as far as I can tell, this allows you to set it to anything

SingularByte: he/him

11-07-2022 12:32:12 UTC

I’m fairly sure the legal values are defined by “Operators have a Readiness, which is publicly tracked, which may be either In the Workshop or Ready, and which defaults to In the Workshop.”
Any other value than those is not a legal value since Readiness is not permitted to hold anything else.

Kevan: he/him

11-07-2022 13:38:48 UTC

I think we might actually need three states here: Workshop (“go away, I’m busy”), Ready (“I’ve built a bot and am ready to be matched for a bout”) and Set (“I’ve seen which bot I’m up against and have written a Script accordingly”).

Possibly limiting Bot alteration to the Workshop state, and reprogramming to Workshop/Ready, and only allowing the Announcer to un-Set Operators, so that once a battle has started we can’t make any more changes.

Josh: Observer he/they

11-07-2022 13:52:01 UTC

@Kevan Thanks - have amended

Kevan: he/him

11-07-2022 17:53:29 UTC

for

Brendan: he/him

11-07-2022 19:56:57 UTC

for

Raven1207: he/they

11-07-2022 20:07:12 UTC

for

Darknight: he/him

11-07-2022 20:11:16 UTC

for

thundershrike:

12-07-2022 15:01:16 UTC

for