Saturday, July 23, 2022

Proposal: Shove clarity

Enacted 4-0. Josh

Adminned at 25 Jul 2022 16:19:14 UTC

If the Bout between SingularByte and Jumble announced in Announcement #13 has been resolved in Jumble’s favour due to SingularByte failing to set their Readiness to Set then undo the resolution of that Bout, consider it to have been announced at the time of the enactment of this proposal, and set the status of both of those Operators to Staging.

Reword the rule When Push Comes To Shove to read as follows:

When an actor has an opponent in a space adjacent to it and and its reaction is to move into or beyond that opponent’s space, the existing reaction ceases to take effect and instead a Shove occurs.

A Shove is resolved as follows:
* The Shove Power of the actor and opponent is calculated, where Shove Power is Effective Power Output minus 50% of the consumption of the chassis and every system on the bot.
* For every 50 that the Shove Power of the Actor exceeds the Shove Power of the Opponent, both the Actor and Opponent move in the direction that the Actor stated they were moving in by 1 space, up to the number of spaces the Actor’s script stated they were moving.
* Scratch Damage is taken by both the Actor and the Opponent.

The Shove Power of a bot is halved if they are shoving (or being shoved by) a bot they are facing away from.

If there is no rule called Configuration then any Bouts that were announced in Announcement #13 that have yet to be resolved by the Announcer cease to have their listed Configurations apply, and this proposal has no further effect.

In the rule Configuration, change “When a Bot is Shoved in while occupying a square that has another square above or below it, instead of being moved backwards, it is moved into one of the squares above or below it and is flipped” to say:

If a Shove is taking place and, during the resolution of that Shove, the Opponent passes through a square that has another square above or below it, instead of being moved backwards, it is moved into one of the squares above or below it (at random if both are present) and is flipped, and then the Shove immediately ends.

Resolving a debatable ambiguity in the Shove rules. I accept that on the current reading SingularByte’s interpretation is more likely to be correct, but I’m setting this to work the way I’d like it to work because otherwise I think that the Physical Obstacles configuration becomes pointless.

Comments

SingularByte: he/him

23-07-2022 14:11:10 UTC

for

Brendan: he/him

23-07-2022 15:14:54 UTC

imperial

Darknight: he/him

24-07-2022 09:08:30 UTC

for