Tuesday, August 30, 2022

Call for Judgment: Closing the Warp hole

Enacted popular, 5-0. Josh

Adminned at 31 Aug 2022 13:03:31 UTC

In the rule BotScript move the following statement:

If it’s a Melee System and the Opponent’s Bot is not in any of the three spaces immediately in front of the reacting Bot, then the System’s Effect is instead not used.

To be its own item in the rule above.
Rephrase it to read:

If the system being used is a Melee System and the Opponent’s Bot is not in any of the three spaces immediately in front of the reacting Bot, then the System’s Effect is instead not used.

If the Call for Judgment: Warp Zone Closed is still open and has not been enacted, then fail it.
If the Call for Judgment: Warp Zone Closed has been enacted, then undo its changes before enacting this proposal

If enacted, this should modify the standard ruleset immediately as defined in the Standardized Rule Books rule.

Instead of getting rid of it, just move the special situation from the reaction to its own rule, why was it even there to begin with?

posted by Maldor at 30 Aug 2022 18:52:00 UTC Comments (8)

Comments

Brendan: he/him

30-08-2022 19:26:33 UTC

(Per Habanero, this would also have to update “Standardised Rule Books” to have an effect.)

SingularByte: he/him

31-08-2022 05:06:25 UTC

for

Josh: Mastermind he/they

31-08-2022 07:55:42 UTC

for

Darknight: he/him

31-08-2022 09:57:29 UTC

for

Brendan: he/him

31-08-2022 12:29:27 UTC

for

SingularByte: he/him

31-08-2022 12:41:24 UTC

CoV against
I’ve just realised, this doesn’t actually resolve the issue, since it doesn’t specify what it means to be “its own item”. The enacting admin would have every right to make it a new reaction (i.e. a new item in the list), which would make the wormhole permanent for the whole bout without the need for a status.

Josh: Mastermind he/they

31-08-2022 12:52:58 UTC

Eh, I think we can deal with admin malice if it arises - I mean, I don’t *have* to run the bout, and will continue not to do so if something urgently needs to be fixed. (You can take this as a general notice that I will not be playing along with timing scams.)

SingularByte: he/him

31-08-2022 13:00:17 UTC

Fair enough. CoV for