Wednesday, October 18, 2023

Proposal: The Need for Speed

Exceeded Quorum, 4-1 with 2 DEFs and Battle Master voting FOR. Enacted by JonathanDark.

Adminned at 19 Oct 2023 16:43:41 UTC

In the rule “Spells”, add the following bullet after the bullet “a set of inputs”:

* a speed

and in the same rule add this text:

A spell’s speed is a non-negative integer. If a spell does not have a speed defined, its speed defaults to 1. Any action that would lower a spell’s speed below 0 instead sets it to 0.

In the rule “Commencing a Duel”, replace “Each spell selected for casting by a Wizard is cast simultaneously.” with the following:

Each spell selected for casting by a Wizard is cast starting with the Spells with the highest speed, where Spells with equal speed are cast simultaneously, and then repeating this step in decreasing numerical order by speed until all selected spells are processed. Spells cast at a lower Speed cannot affect Spells cast at a higher Speed.

In the subrule “Misdirection” add this text:

Speed: 2

and in the same subrule replace the text “any Spell this Duel” with this text:

any Spell with a lower Speed than this Spell

and in the same subrule remove the text “This also applies to a targeted position changed by another Wizard’s Misdirection spell.” if it exists.

In the subrule “Siphon” replace the text “receives” with “received” and add this text:

Speed: 0

I know that this might not be strictly necessary, as Clucky pointed out in Discord, but it helps establish the base mechanic of Speed. It also keeps Misdirection from being too overpowered. I anticipate more uses for Speed if this is enacted.

Comments

Clucky: he/him

18-10-2023 17:48:20 UTC

for

Raven1207: he/they

18-10-2023 19:53:07 UTC

for

Zack: he/him

18-10-2023 21:16:40 UTC

for

Snisbo: she/they

18-10-2023 21:59:53 UTC

for

Brendan: he/him

19-10-2023 00:42:04 UTC

against I think it would be better to just shuffle the battle ring when it’s time to conclude the duel and then resolve spells in that order.

Snisbo: she/they

19-10-2023 01:12:05 UTC

imperial Oh I also like Brendan’s idea! I’d be fine with either

Clucky: he/him

19-10-2023 05:11:04 UTC

I think knowing that you misdirect will work rather than hoping you get put early in the order is overall better

Kevan: City he/him

19-10-2023 07:48:20 UTC

imperial