Proposal: Hack the Gibson
Reached quorum 7 votes to 0. Enacted by Kevan.
Adminned at 08 Mar 2023 12:36:15 UTC
In the rule “Disks”, just before the subrule “Terminals”, add the following text:
If a disk Effect would report or change one or more values that are privately tracked by the Gridmaster, the Runner who is Activating the disk must privately inform the Gridmaster of the disk being Activated and all values that were chosen as part of the Effect.
In the rule “Disks”, add the following entry to the table “Disks”:
|-
| hack.c || 5 || You may pay 3 Power. If you do, privately request the Gridmaster for up to 2 Features, which may both be the same Feature, for the next Initialise action, or request that no Features should be set. If any other Runners have also Activated their copy of this disk since the last Initialise, the Power must still be paid, but the Gridmaster must ignore all requests from this Effect and instead privately inform each Runner who made these requests that their hack has failed due to another hacker in the system.
In the rule “The Lines”, replace this bullet:
* Repeat the following DICE4 times: Select a random Feature and add it to the Grid.
with this bullet:
* If exactly 1 Runner has Activated their copy of the hack.c disk since the last Initialise, select the Features requested by that Runner and add each to the Grid in the order in which they were mentioned in the request. Otherwise, repeat the following DICE4 times: Select a random Feature and add it to the Grid.
This is mostly introducing hacking, but also a little clarification on how some of the Effects should work when they involve variables that the Runner cannot change due to those variables being tracked privately by the Gridmaster.
Brendan: he/him
I am legally required to vote in favor of this.