Proposal: Multiple types of subspecies abilities
Times out and passes 3-0. -Bucky
Adminned at 07 Jan 2021 18:21:45 UTC
If Proposal “Typo Defense” passed, when this Proposal is resolved, all instances on “Defence” are treated as “Defense”
In rule DEVAs, subrule DEVA Sub-species
replace
The named Features of DEVAs, and those Features’ Effects, are listed below (with the name in bold and the Reaction afterwards):-
with
The named Features of DEVAs, and those Features Types and Effects, are listed below (with the Name in bold and then the Type, then the Effect):-
Make the Type of all existing features “Reactionary”. Make the Effect of all existing features their old Reaction text.
In rule “The Battlefield”, replace
If, after resolving a Fire Action, the target is still in play, Poindexter must apply all Reactions of its Features, in the order that they are listed in the ruleset. These should also be disclosed in the appropriate Schedule Post.
with
If, after resolving a Fire Action, the target is still in play, Poindexter must apply all Effects of its Reactionary Features, in the order that they are listed in the ruleset. These should also be disclosed in the appropriate Schedule Post.
In rule “The Battlefield”, also replace
If the Fire Vector is exactly equal to the target’s Defence, then the target is eliminated.
with
If the Fire Vector is exactly equal to the target’s Defense, Poindexter must apply all Effects of its Death Features, in the order that they are listed in the ruleset. These should also be disclosed in the appropriate Schedule Post. Then the target is eliminated.
I was going to make a new Refracted Crystal Heart proposal where I avoided the limit of features to react to unsuccessful shots by hardcoding it into The Battlefield.
Then I realized that it would be far more interesting to create an open-ended proposal allowing different types of features that activate at different times.
I decided to just include the Reactionary and Death feature types for now. I’m thinking about Emergence, Civil, and Military feature types for later.
Actually having a modular feature type of the same type as a stage of an action might be a way to quickly add support for all of those three.
Josh: he/they