Proposal: Ghosts in Shells
Passes 10-0 with more than Quorum in favor. -Bucky
Adminned at 30 Nov 2020 23:42:39 UTC
Add a new rule to the ruleset, called Shells:
The gamestate tracking page for this dynasty is the Ansible Hangar page of the wiki. Unless otherwise stated, all publicly tracked gamestate information is tracked on it.
At any time each Pilot may be Demobbed or Jockeying, defaulting to Demobbed, and their status is publicly tracked. An Demobbed Pilot may change themselves to be Jockeying at any time. A Jockeying Pilot has the following tracked information: a Shell Archetype and amounts of Power, Attack and Defence (which are all non-negative integer).
When a Pilot sets themselves to Jockeying, they may select a Shell Archetype. The list of available Shell Archetypes can be found in the rule Shell Archetypes. They must then set their Power, Attack and Defence to the default value for their selected Shell Archetype.
Add a new subrule to that rule, called Shell Archetypes:
Each Shell Archetype has a name, a brief description (which is flavourtext), a default Power value, a default Attack and a default Defence.
The following is the list of Shell Archetypes that has been approved by RAID R&D:
The Mark I
Description: The first Shells to roll off of the Ansible’s production line. Clunky, slow, but durable.
Default Power: 90
Default Attack: 5
Default Defence: 20
Kevan: he/him
“At any time each Pilot may be Idle or Jockeying.” with an implicit alphabetical default will, I think, immediately idle everyone except the Poindexter out of the game.
“Unless otherwise stated, all publicly tracked gamestate information is tracked on it.” looks promising, although I don’t think it’s implicit enough that the Pilot stats are publicly tracked.