In “The Quarry”, change

Every hour the amount of Stone in the Quarry decreases by 1, to a minimum of zero; whenever any Engineer or City Architect would perform any action that would cause the amount of Stone to change they must first update its value to reflect any reduction due to the passage of time.

to

Erosion is an atomic action that decreases the amount of Stone in the Quarry by 24. Whenever any Engineer or City Architect would perform any action that would cause the amount of Stone to change, they must first perform the Erosion atomic action if it has been more than 24 hours since the last Erosion.

Set the amount of Stone in the Quarry to 650.

If Hands Off is passed, update “If no action has been taken in the past 24 hours that has changed the Building Contents, and the Building is not Collapsed, then the Building is Stable.  Otherwise, it is not Stable.” to the following

If no action has been taken in the past 24 hours that has changed the Building Contents, and the Building is not Collapsed, and the building stability is greater than 100 but less than 200 then the Building is Stable. Otherwise, it is not Stable.

Also if Workplace Safety is passed then add a bullet to the end of the Move On atomic action:

* Increase the Accident count of the acting Engineer and the most recent Engineer to perform the build action

Enact a new rule entitled “Guilds” as follows:

Each Engineer belongs to a single Guild, which is publicly tracked, defaulting to Stonemasons. An Engineer with their Guild set to X is considered to be a member of X and to belong to X; being a member of a Guild confers certain abilities listed in this rule (Guild names are bolded with the relevant abilities listed immediately thereafter). As a Weekly Action, an Engineer may change their Guild to any of the following:

• Stonemasons: An Engineer belonging to the Stonemasons may, as an atomic Daily Action, Mine, which consists of reducing the quantity of Stone in the Quarry by DICE2 and then increasing their own Stone by the same amount.
• Logisticians: An Engineer belonging to the Logisticians may, as a Daily Action, spend up to 10 Stone to increase another Engineer’s Stone by the same amount.
• Electricians: An Engineer belonging to the Electricians may, when spending Focus as part of an Atomic Action, proceed as if they have spent an additional 10 Focus.

Remove the sentence beginning “As a daily action, each Engineer may Mine…” from the rule “The Quarry” if it exists there.

To the end of the “Move On” atomic action, add a bullet point:-

* Set every Engineer’s Focus to 500

In “The Building”, after the bulleted list of building contents, or after the subrule “Building Contents” if it exists, add the following:

If no action has been taken in the past 24 hours that has changed the Building Contents, and the Building is not Collapsed, then the Building is Stable.  Otherwise, it is not Stable.

and change any instances of the rulestext “If the building has collapsed, then any Engineer can Move On.” and “While the Building is Collapsed, any Engineer can Move On.” to

While the Building is Collapsed or Stable, any Engineer can Move On.

After the first sentence of “The Building”, add:-

The start of this list is its base, and the end of this list is its top.

Replace “ordered list of items that defaults to” with:-

ordered list of items (known as Blocks) that defaults to

Replace “item” with “Block” and “rightmost” with “topmost” throughout the steps of the Build action.

Update the layout of the Construction Site page to display the Building vertically.

Add a new rule named “Accidents” and give it the following text:

Each Engineer has a publicly-tracked number named Accidents that defaults to 0.

In the rule “The Building”, add the following bullet as the last step of the atomic action Build:

* If Building Stability is 0 or lower, add 1 to their Accidents

In the rule “The Building”, remove the text “Possible building contents are shown in the list below: W: Wood. A reliable building material. S: Stone. A sturdy but very heavy building material. -: Empty.”

Create a subrule called “Building Contents” with the text:

The possible building contents for The Building, known as Materials, are listed in the table below. The ruleset may refer to a given Material using either its Name or Abbreviated Name - they are considered equivalent. The Description is flavour text.

If Engineers have a numerical publicly tracked variable with the same name as a Material, they are said to have that amount of the Material - otherwise, they are said to have 0 of that Material and are not capable of spending it.

Name | Abbreviated Name | Description
Empty | _ | This represents open space.
Wood | W | A reliable building material.
Stone | S | A sturdy but very heavy building material.

Throughout the Build atomic action in the rule The Building, replace each hyphen with an underscore.

In the rule “The Building”, replace “Optionally choose any W in the Building Contents and chose a replacement item from the list of the possible building contents that is not W or -. If they choose this option, the Engineer must first spend 1 of a publicly-tracked variable associated with that Engineer such that this variable is a legal value after the spend and the action of this spending would allow the Engineer to use 1 of the replacement item. If they do, they may then replace the W in the Building Contents with the replacement item.” if it exists, with:

Optionally, by spending 1 from any of their Materials except Wood or Empty, they may choose any W in the Building Contents and replace it with the spent Material.

From the rule “The Quarry”, remove the text “Whenever an Engineer spends 1 of their Stone in the manner described in the Build atomic action, they are able to use 1 S as a replacement item in that same action.” if it exists.

If there exists ruletext reading “As a Daily Action, if the Building has not collapsed, a Engineer may Build” then reword it as follows:

As a Daily Action, if the Building is not Collapsed, a Engineer may Build

If there exists ruletext reading “If Building Stability is 0 or lower, the building has collapsed!  If the building has collapsed, then any Engineer can Move On.” then reword it as follows:

If Building Stability is 0 or lower, then the Building is Collapsed; otherwise, the Building is not Collapsed. While the Building is Collapsed, any Engineer can Move On.

If “Building a Building” was not enacted, this Proposal has no effect.

In the rule “The Building”, add the following bullet as the first bullet in the atomic action Build:

* Optionally choose any W in the Building Contents and chose a replacement item from the list of the possible building contents that is not W or -. If they choose this option, the Engineer must first spend 1 of a publicly-tracked variable associated with that Engineer such that this variable is a legal value after the spend and the action of this spending would allow the Engineer to use 1 of the replacement item. If they do, they may then replace the W in the Building Contents with the replacement item.

If the rule “The Quarry” exists, add the following text to that rule:

Whenever an Engineer spends 1 of their Stone in the manner described in the Build atomic action, they are able to use 1 S as a replacement item in that same action.

Add a new rule, “Focus”:-

Each Engineer has a publicly-tracked amount of Focus, being a number that defaults to 500.

Add a bullet point to the “Build” atomic, after the first point:-

* Spend any amount of Focus

Remove “Decrease Building Stability by that amount.” and add a further bullet point to the end of the action:-

Decrease Building Stability by the Wobble. (The Wobble for this action is equal to the result of its die roll, minus any Focus spent during it, to a minimum of zero.)

Josh is now mentoring Pokes until the Third Dynasty of Misty has ended and the date is past the 27th of April 2023.

Yes, I’m an admin, but I can’t remember exactly how unidling works and I don’t have time to figure it out again at the moment. If someone would be so kind as to facilitate my laziness I would be thankful!

Add a new rule, called The Quarry

The Quarry is an entity that contains a publicly tracked quantity of Stone, defaulting to 720; each Engineer also has an amount of Stone which is publicly tracked and which defaults to zero. Every hour the amount of Stone in the Quarry decreases by 1, to a minimum of zero; whenever any Engineer or City Architect would perform any action that would cause the amount of Stone to change they must first update its value to reflect any reduction due to the passage of time.

As a daily action, each Engineer may Mine, which is an atomic action that consists of reducing the quantity of Stone in the Quarry by DICE2 and increasing their own Stone by the same amount.

If there is a rule called The Building, after the line which starts with “W: Wood”, add:

S: Stone. A sturdy but very heavy building material.

Add a new rule called “The Building”:

The Building is comprised of the following variables, which are all publicly tracked: Building Number, which defaults to 0, Building Stability, which is an integer that defaults to 1,000, and Building Contents, which is a ordered list of items that defaults to WWWWWWWWWWWWWWWWWW.  Possible building contents are shown in the list below:
W: Wood.  A reliable building material.
-: Empty.

As a Daily Action, if the Building has not collapsed, a Engineer may Build, which is a atomic action with the following steps:
* Choose a item that is not one of the five rightmost items in the Building Contents.  Add a copy of it in the rightmost place of the Building Contents, then replace the original item with a -.
* Roll a DICEN, where N is the number of - currently in the Building Contents, times 25.  Decrease Building Stability by that amount.

If Building Stability is 0 or lower, the building has collapsed!  If the building has collapsed, then any Engineer can Move On.

Move On is an Atomic Action with the following steps:
* Increase Building Number by 1
* Set Building Stability to (1,000+Building Number*100) and Building Contents to WWWWWWWWWWWWWWWWWW

Hey!  All of ya!  Hello and welcome!  As you may already know, that black hole had finally evaporated from that place, which means that construction for the city of our dreams has finally begun again!  Now you might be wondering why you were brought in so late.  There’s uh, one small problem that cropped up.  Someone was an absolute incompetence and blew up half of our construction materials.  Supply chain issues caused by major parts of Asia no longer existing mean that we won’t be getting any replacements soon, so we kind of have to make do with what we have.  That’s why you’re here!  Your job is to take all the non-essential building stuff from the lower floors and hand them right back to the workers.  They won’t suspect a thing, and we might be able to stretch our last few resources far enough to complete the city!  Any questions?

Okay, I guess you could call this “pulling a Jenga”, but don’t let the workers know about that.  Or any of this, really.

Dynasty theme: Jenga.  Repeal all dynastic rules.  Set the player synonym to Engineer and the emperor synonym to City Architect.  Set the gamestate tracking page to be “Construction Site”.

As per “Running”, I have achieved victory.

Please post your thoughts on the The Grid dynasty here

The blue lines around you, which have been your world since what seems like an eternity, begin to fade to black. The random lines and dots on your wrist-screen fade as well, plunging you into darkness. After a few seconds, the screen shows the following message:

Replace this text:

If a Cell’s Value is not “-”, it is said to “contain” an instance of that Value.

with this text:

If a Cell’s Value is not “-”, it is said to “contain” an instance of that Value. Otherwise, it contains “-”.

Retroactively consider all Cells with a Value of “-” as containing “-” and thus considered Empty for all dynastic actions that have occurred since March 9 2023 10:04:10 UTC

The voice from your wrist-screen says “Twenty-five” at the same time that the number 25 shows up on the screen.

A green box states:

The voice from your wrist-screen says “Twenty-four” at the same time that the number 24 shows up on the screen.

A green box states:

Remove Raven1207 from the list of tenured players.

Add the following to the end of the first paragraph of the rule Mentors, changing the word ‘players’ to its synonym as per the rule Synonyms:

The Mentorships page is also used to list the names of players who are prohibited from becoming Tenured; this list may only be amended by the effect of a votable matter.

Add a new section to the Mentorships page for prohibited players, and add the name of Raven1207 to that list.

The voice from your wrist-screen says “Twenty-three” at the same time that the number 23 shows up on the screen.

A green box states:

The voice from your wrist-screen says “Twenty-two” at the same time that the number 22 shows up on the screen.

A green box states:

Your wrist-screen beeps, and a new notification in green appears among the random lines and dots:

In the rule “Running”, replace this text:

If, during the most recent 3 Tick atomic actions (excluding this one), the number of Runners in the Exit has been at least 1 for the entire Tick atomic action

with this text:

If there is at least 1 Runner in the Exit at this step, this Tick is considered a Shutdown Tick. If the most recent 3 Ticks (excluding this one) have been Shutdown Ticks

Retroactively treat any Tick that would have met the criteria of the replacement text as having been a Shutdown Tick.

The voice from your wrist-screen says “Twenty-one” at the same time that the number 21 shows up on the screen.

A green box states:

Your wrist-screen beeps, and a new notification in green appears among the random lines and dots:

In the rule “Basic Grid Rules”, replace this text:

A Runner is said to be “in” a Cell

with this text:

A Runner is said to be “in” a Cell or to “occupy” a Cell

Add the following to “The Grue”:

The Grue cannot move into any cells with the value of “Exit”. If the Grue ever occupies a cell with the value of “Exit”, the Gridmaster should blank the Grue’s location at the earliest possible convenient time.

The voice from your wrist-screen says “Twenty” at the same time that the number 20 shows up on the screen.

A green box states:

The voice from your wrist-screen says “Nineteen” at the same time that the number 19 shows up on the screen.

A green box states:

In the rule The Lines, replace the text “Repeat the following DICE4 times: Select a random Feature and add it to the Grid. Weight the random selection such that each feature not selected during the last Initialise action has twice the probability compared to any feature that was selected last time.” with:

Add each Feature to the Grid once, in a random order.

The voice from your wrist-screen says “Eighteen” at the same time that the number 18 shows up on the screen.

A green box states:

In “Running”, change

If the most recent Tick was more than 24 hours ago

to

If the most recent Tick was more than 24 hours ago, or if the most recent Tick was more than 8 hours ago and only one Live Runner has no Heading,

After the 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, append:

It is permissible for a Gridmaster to activate a Runner’s disk on their behalf at their private request, or to Execute on that Runner’s behalf at their private request, with the Gridmaster processing that request at their earliest convenience. The effects of such a disk activation should also be handled by the Gridmaster on that Runner’s behalf, using the legal values (if any) that were chosen by the Runner for that effect.

Uphold any previous instances of the Gridmaster activating a disk on a Runner’s behalf.

Misty has established a Mentorship mentoring jjm3x3

Hey all I am writing to make a formal declaration of intent to join in the grid.

In the rule “The Lines”, replace this text:

Loading a new Stratum is an atomic action with the following steps:

with this text:

Loading a new Stratum is an atomic action that is also called Initialise and has the the following steps:

Uphold all previous “Loading a new Stratum” actions as if they were also Initialise actions.

The voice from your wrist-screen says “Seventeen” at the same time that the number 17 shows up on the screen.

A green box states:

Your wrist-screen beeps, and a new notification in green appears among the random lines and dots:

The voice from your wrist-screen says “Sixteen” at the same time that the number 16 shows up on the screen.

In the rule “The Lines”, in the subrule “Features”, remove the bullet that begins with “Passcoded Egress”

In the rule “The Lines”, in the bulleted list, add the following bullet just above the last bullet:

* If the Stratum is 6, set the cells D4, D5, E4 and E5 to have the value of Exit.

In the rule “The Grue”, add the following just before the final sentence:

The Grue should then add that Runner’s Number-Crunches to its own (without subtracting any of that Runner’s Number-Crunches).

In The Lines, replace “If no Cells have a value of Battery, set the value of a random Cell to Battery” with:

If no Cells have a value of Battery, set the value of a random non-Purple Cell to Battery

At the end of the rule “The Lines”, add a new sentence after the bullet point list:

If the value or colour of a cell would be modified in the loading of a new stratum but it would be illegal to do so, that modification is skipped for that cell.

In the rule “Running”, replace the text “If the number of runners in the Exit has been at least 1 for the entirety of the last three ticks, and if one of those runners has the highest non-zero Number-Crunches out of all Runners in the Exit, that Runner has achieved victory.” with

If, during the most recent 3 Tick atomic actions (excluding this one), the number of Runners in the Exit has been at least 1 for the entire Tick atomic action, and if one of the Runner currently in the Exit has the highest non-zero Number-Crunches out of all Runners in the Exit, that Runner has achieved victory.

In “The Exit”, replace “A Runner can spend any positive amount of Power to increase their Number-Crunches by that amount” with

A Runner can spend any positive amount of Power to increase their Number-Crunches by that amount by notifying the Gridmaster of the amount of Power they wish to spend

In the rule “The Exit”, append the following paragraph:

When a Runner besides the Grue has achieved victory, the Gridmaster should, at their earliest convenience, post a blogpost announcing that that Runner has escaped.

The voice from your wrist-screen says “Fifteen” at the same time that the number 15 shows up on the screen.

In the rule “The Grid”, subrule “Location”, replace “If no other Runner has this Cell in their Location at the time the message is processed, the Gridmaster sets the Location of the Runner to the requested Cell and replies with an acknowledgement of the request. Otherwise, the Gridmaster replies that the Cell is taken. ” with “The Gridmaster should then set the Location of the Runner to the requested Cell. If at least one other Runner has this Cell in their Location at the time the message is processed, the Gridmaster should also reply that the Cell is occupied.”

As a subrule of The Lines, create a rule called “Downloading a new Stratum” with the text:

A Runner may Download by privately informing the Gridmaster that they are doing so, and that Runner is considered to be Downloading until the end of the next Tick action. If a Runner has Executed since the most recent Tick, they may not Download. If a runner is Downloading, they may not Execute.

In Running, replace the bullet point “If no Cells have a value of Battery, Load a new Stratum” with:

If no Cells have a value of Battery, or if the number of Runners that are Downloading is greater than 50% of Live Runners, Load a new Stratum

In the same rule, replace the bullet pont “Post a blog entry announcing the new Watch Number, and announcing any Runners whose Locations are cells in the Alpha Sector.” with

Post a blog entry announcing the new Watch Number, the number of Runners that are Downloading, and announcing any Runners whose Locations are cells in the Alpha Sector.

The voice from your wrist-screen says “Fourteen” at the same time that the number 14 shows up on the screen.

The voice from your wrist-screen says “Thirteen” at the same time that the number 13 shows up on the screen.

In the rule “Basic Grid Rules”, in the subrule “Status Report”, add the following bullet after the bullet “* Power”:

* Number-Crunches

The voice from your wrist-screen says “Twelve” at the same time that the number 12 shows up on the screen.

In the rule “Running”, replace this bullet:

If the Grue’s Location is in the same row or column as any other Runners (excluding those in the same Cell as it), change the Grue’s Heading to face a secretly random such Runner.

with this bullet:

If the Grue’s Location is in the same row or column as any other Runners (excluding those in the same Cell as it), select all of the Headings where the Grue would be facing such Runners, and where the orthogonally adjacent Cell to the Grue in the direction of each Heading does not contain “Firewall”, and change the Grue’s Heading to a randomly chosen Heading from this selection. If there are no such selections possible, instead select all of the Headings where the orthogonally adjacent Cell to the Grue in the direction of each Heading does not contain “Firewall”, and change the Grue’s Heading to a randomly chosen Heading from this selection if possible.

The voice from your wrist-screen says “Eleven” at the same time that the number 11 shows up on the screen.

Your wrist-screen beeps, and a new notification in green appears among the random lines and dots:

Create a rule called The Exit:

The Exit consists of all cells with a value of “Exit”, and all cells with that value have a colour of Purple. Once a cell’s value is set to the value of “Exit”, that cell can never have its value changed, nor its colour changed.

Each Runner has a non-negative integer called Number-Crunches which is privately tracked by the Gridmaster. A Runner can spend any positive amount of Power to increase their Number-Crunches by that amount, though if that runner is in a non-empty cell, this increase is divided by four (rounded down to the nearest integer).

In the rule Running, add a new bullet point to the start of the list of bullet points describing a Tick:

* If the number of runners in the Exit has been at least 1 for the entirety of the last three ticks, and if one of those runners has the highest non-zero Number-Crunches out of all Runners in the Exit, that Runner has achieved victory. (If the Grue achieves victory in this way, the Gridmaster should create a Blogpost to confirm that the Grue has escaped. The Grue’s location should be blanked, and it can never have its location set to a value again, but otherwise its victory is ignored.)

Create a bullet point in the list in the rule Features with the following text:

* Passcoded Egress: If this is exactly the second time that the Passcoded Egress feature is being added to the Grid, set the cells D4, D5, E4 and E5 to have the value of Exit.

If “Veni veni venias” is enacted, this Proposal has no effect.

Add a new rule called “The Beacon” and give it the following text:

The Beacon is a privately tracked variable with either a blank value or the partial or full identification of a Cell, defaulting to blank.

Whenever a Runner is the only Runner with a Location exactly matching the same Cell as the Beacon, and the Beacon is not blank, the Gridmaster should make a blog post indicating the Runner’s name and Location and that they found the Beacon. That Runner achieves victory.

In the rule “The Lines”, add this bullet just before the last bullet:

* Blank the Beacon’s value

In the rule “Disks”, add this row to the table:

|-
| signal.c || 3 || You may pay 3 Power. If you do, send a private request to the Gridmaster setting either the row letter or the column number of the Beacon, then remove this Disk. If honoring this request would result in the Beacon containing the same Location as the Runner executing this Disk, the Gridmaster should privately randomly select a row letter if the Runner requested a column number, or privately randomly select a column number if the Runner requested a row letter, and set the Beacon’s value to the randomly-selected value plus the Runner’s requested value. Otherwise, the Gridmaster should only set the Beacon’s row letter or column number value with the Runner’s choice. In either case, the Gridmaster should privately respond at their earliest convenience confirming only the setting that the Runner chose.

The voice from your wrist-screen says “Ten” at the same time that the number 10 shows up on the screen. A yellow notification appears:

Darknight idles out after seven days without any posts or comments.

Under the recently changed idling rule, this now means that they can’t be unidled within the next four days, and that for both this and the next dynasty they will idle out at four days rather than seven.

Create a new dynastic rule named “The End” with the following body:

Each Runner has a Chance, which is a publicly tracked value defaulting to False.

If the current date and time is on or after the 10th of April, 00:00:01 UTC, 2023, then the game is in Endgame. While the game is in Endgame, the Gatemaster may not Load a New Stratum and the Location of Runners whose Location is set to blank cannot be changed.

If the game is in Endgame and they haven’t done so already, the Gatemaster should, at their earliest convenience, Load the Final Game, which is an atomic action with the following steps:
* Set the Location of all Runners whose Chance is set to True to A1
* Blank the Location of all Runners whose Chance is set to False

A Runner has achieved victory when their Chance is set to Fulfilled.

In the rule Disks, add a new entry to the list of Disks:

| mark.c || 5 || Set your Chance to True

If Proposal: Woops, we were muted enacted, In the rule Short-Distance Comms, change “Any two Runners who share the same Location” to “Any two Runners who are Nearby each other”.

If Proposal: Woops, we were muted was not enacted, create a new dynastic rule named “Short-Distance Comms” with the following body:

Any two Runners who are Nearby each other may privately communicate with each other as if the special case rule “No Collaboration” is not active.

Add the following rule to the ruleset, known as “Short-distance Comms”:

Any two Runners who share the same Location may privately communicate with each other as if the special case rule “No Collaboration” is not active.

The voice from your wrist-screen says “Nine” at the same time that the number 9 shows up on the screen.

In the rule “Disks”, replace this text for the Effect of yank.c:

You may add a copy of a Disk from the Heap which shares a row or column with your Location to your own Stack

with this text:

You may add a copy of a Disk from the Heap which shares a row or column with your Location to the rightmost end of your own Stack

For any dynastic action taken where yank.c was Executed and the copied Disk was not placed at the rightmost end of the Runner’s Stack, move that Disk to the rightmost end of that Runner’s Stack if it is still present in their Stack.

The voice from your wrist-screen says “Eight” at the same time that the number 8 shows up on the screen.

In the “Warped” entry of “Features”, replace “Set the Location of all Live Runners to a random Cell” with:-

Simultaneously move each Live Runner to a different random Cell

Uphold the Gridmaster’s earlier application of the Warped Feature on March 12.

The voice from your wrist-screen says “Seven” at the same time that the number 7 shows up on the screen.

In the rule “Running”, at the end of the rule add the following text:

If the most recent Tick was more than 24 hours ago and the Gridmaster has not done so since the most recent Tick, at their earliest convenience they should privately remind every Live Runner who has no Heading that they are in danger of being Derezzed.

Tug, blur, movement. Yep, it’s another watch number.

The voice from your wrist-screen says “Six” at the same time that the number 6 shows up on the screen. Interestingly, there’s no warning this time, although you get the feeling that the threat of Derezzing is still real.

In “Idle Runners”, replace “An Admin may render a Runner Idle if that Runner has asked to become Idle in an entry or comment from the past 96 hours (4 Days), or if that Runner has not posted an entry or comment in the past 168 Hours (7 days). In the latter case, the Admin must announce the idling in a blog post.” with:-

An Admin may render a Runner Idle if that Runner has asked to become Idle in an entry or comment from the past 96 hours (4 Days), or if that Runner has not posted an entry or comment in the past 168 Hours (7 days). In the latter case, the Admin must announce the idling in a blog post, and the 168 Hour idle timeout is considered to be reduced to 96 hours for that Runner during the current and subsequent dynasty.

Replace “unless the Runner who would be Unidled asked to become (or rendered themselves) Idle within the past 96 hours (4 days)” with:-

unless the Runner who would be Unidled has become Idle within the past 96 hours (4 days)

Chiiika idles out after a full seven days without making a post or comment. Quorum drops to 5.

In the rule “Disks” just before the subrule “Executions” add the following text:

The suffix of a Disk is the last two characters of its name

In the rule “Disks” add a subrule named “Compression” and give it the following text:

If a Runner has not done so since the most recent Tick, they may spend 3 Power to perform the Compression action.

The Compression action is an atomic action in which the Runner selects two Disks in their Stack which are adjacent in list position and which may end in any suffix. The Runner combines them into one Disk by removing the names of the two Disks and replacing them with a name in the format “Disk1-Disk2.z”, where “Disk1” is the name of the first disk without the suffix and “Disk2” is the name of the second disk without the suffix. The Capacity of this disk is half of the combined original Capacity of all Disks listed in the new name, rounded down to the nearest integer but no less than 1.

When a Runner performs the Execute action, they may not Execute a Disk with the suffix “.z” unless they spend an extra 2 Power. If they do so, they may Execute each Disk listed in the name in the order listed in the name, but only pay the Power required for the Index of that “.z” Disk as well as any additional Power required by each Disk’s Effects.

In “Disks”, replace “You may Push a Disk from the Heap which shares a row or column with your Location, but only to your own Stack” with:-

You may add a copy of a Disk from the Heap which shares a row or column with your Location to your own Stack, marking that Disk in the Heap as Yanked if it is not already

To the rule “The Heap”, add:-

Each Disk in the Heap may have the condition of Yanked, and defaults to lacking it: a Disk being Yanked is tracked by it being italicised.

In Running, after “Blank every Runner’s Heading”, add a bullet point:-

Remove all Yanked Disks from the Heap

In the rule “Disks”, replace the Effect text for the disk “yank.c” with the following:

You may Push a Disk from the Heap which shares a row or column with your Location, but only to your own Stack

and replace the Effect text for the disk “send.c” with the following text:

If you are in the Alpha Sector, you may choose junk.c or remove a Disk from the Heap which shares a row or column with your Location, and then add that Disk between any two adjacent Disks in any Runner’s Stack, or add it to the leftmost position of any Runner’s Stack.

In the rule “Disks”, replace:

If a Disk’s Effect begins with “Trigger:”, then it may be activated by the Runner whose Stack it is in within 24 hours of when the triggering event described in that Disk’s Effect takes place.

with:

If a Disk’s Effect begins with “Trigger:”, then a Runner may Activate it if all of the following are true:
*The Disk is in that Runner’s Stack
*It has been less than 24 hours since the triggering event described in the Disk’s Effect last took place
*The Disk has not been Activated since the triggering event described in the Disk’s Effect last took place

In the rule Executions, reword “Runners are able to Execute, though a Runner cannot Execute more than once in a given tick.” to

Runners are able to Execute, though not if they have already Executed since the most recent Tick.

The tug…the blurring of lines…it’s now becoming normal.

The voice from your wrist-screen says “Five” at the same time that the number 5 shows up on the screen. Again, the warning appears:

Your wrist-screen beeps, and a new notification in green appears among the random lines and dots:

Create a rule called Pointers:

A cell is said to have a Pointer when it contains a “->” along with the name of a Runner; that name being said to be referenced by the Pointer. Cells that have a Pointer are not said to contain that Runner’s name, except for the purposes of this rule.

A runner’s Pointer Count is equal to the number of Pointers that are currently referencing their name.

Any Runner can Create a Pointer when they are in a cell with a value of “-”, or in a cell that has a Pointer.

When a runner Creates a Pointer, they set the value of the cell they are in to “->” followed by their name. Whenever a cell gets such a value, the referenced Runner increases their score by 5 multiplied their Pointer Count. Alternatively, if that Pointer was Created such that it overwrites another Pointer that references a Runner, they may instead transfer an amount of score from that Runner of up to 5 times the Pointer Count that the previously referenced runner had immediately prior to their Pointer being overwritten.

A Runner may not create a Pointer in a given cell if they have already done so in that cell since the most recent tick.

If “It’s a game of Tag, after all” failed, create a new rule called “Score”:

All Runners have a score, which is a publicly tracked non-negative integer defaulting to 0.  If a Runner has a score that is at least 1,000 and is higher than any other Runner’s Score, they have achieved victory.

In “The Stack”, change

When a Stack is Popped, its rightmost Disk is removed and added to the Heap in a Cell of the Popper’s choice (or a random Cell if the Gridmaster Popped it).

to

When a Stack is Popped, its rightmost Disk is removed and, if it is not junk.c, added to the Heap in a Cell of the Popper’s choice (or a random Cell if the Gridmaster Popped it.)

In “Running”, change

Each Runner optionally has a Heading, being a direction of North, South, East or West

to

Each Runner optionally has a Heading, which can be North, South, East, West, or Stay Put

and

Simultaneously move every Live Runner one Cell in the Direction of that Runner’s Heading

to

Simultaneously move every Live Runner one Cell in the Direction of that Runner’s Heading, if it is not Stay Put

Create a new rule called “Score”:

All Runners have a score, which is a publicly tracked non-negative integer defaulting to 0.  If a Runner has a score that is at least 1,000 and is higher than any other Runner’s Score, they have achieved victory.

In “The Stack”, append the following after “If the total Size of Disks on a Stack ever exceeds its Capacity, that Stack has Overflowed; the Runner or Gridmaster whose action caused a Stack to Overflow must repeatedly Pop that Stack until it only contains one Disk, then reduce its capacity by 1, unless reducing the capacity this way would cause the Stack to be Overflowed.”

Then, the Runner who’s Stack Overflowed has their score halved, rounding down.  The Runner who caused their stack to Overflow gains 100 score if they are a different Runner; if it was the Gridmaster, all other Runners gain 50 score instead.

Create a new rule called “One-Off”

As soon as convenient after the Stratum value is first changed to 3, if it did not have at least two instances of the Database Feature added to the Grid, the Gridmaster should add the Database feature to the Grid twice.
Once two Database Features have been added to the Grid, any Runner (or the Gridmaster) may revoke this rule.

Benbot idles out automatically after a full week with no posts or comments. Quorum drops to 6.

In the subrule “Location”, remove the following text:

At any time, a Runner may privately request a Glance around their current Location from the Gridmaster, to which the Gridmaster replies with that Runner’s current Location, their full Spoor, and the names of all Runners (if any) who are Nearby that Runner.

In the subrule “Encounters”, replace this text:

Whenever the set of Runners which are Nearby a Runner changes, the Gridmaster must privately inform that Runner of this.

with this text:

Whenever the set of Runners which are Nearby a Runner changes, the Gridmaster must execute the Status Report action for that Runner as described in the subrule Status Report

In the rule “Power”, remove the following text:

At any time, a Runner can privately request their current Power value from the Gridmaster, to which the Gridmaster should respond with the Runner’s current Power value.

In the rule “Running”, add the following bullet point just before the last bullet point:

* Execute the Status Report action for each Live Runner as described in the subrule “Status Report”

In the rule “Basic Grid Rules”, add a subrule called “Status Report” and give it the following text:

When the Gridmaster takes the action Status Report, they privately inform the target Runner of the following in a single message, each of which is regarding that Runner and the values at the time the message is sent:
* Location
* Spoor
* Power
* The names of all Runners (if any) who are Nearby that Runner

You’re getting used to the tug of the Grid, with the usual blurring and sharpening of lines.

The voice from your wrist-screen says “Four” at the same time that the number 4 shows up on the screen. By now, the warning is getting old, but yet it still shows up:

Add the following entries to the table “Disks”:

|-
| save.c || 2 || You may set any two orthogonally adjacent Cells’ colours to green, if they were not Red.
|-
| alph.c || 3 || You may set any two orthogonally adjacent Cells’ colours to red.
|-
| fire.c || 3 || You may set any two orthogonally adjacent Cells’ colours to yellow, if they were not Red.

In “The Lines”, change “Set the Value of all Cells to -, and set them to their default colour.” to “For every cell, if it is not green, set the Value of the cell to - and set it to its default color.”
In “Running”, after the bulletpoint reading “For each Cell whose value is Battery,”, add the following:

* If any runner is on a yellow cell, they lose 1 Power.  If they do not have any Power, they instead add a junk.c disk to their stack in a random position.

To “Basic Grid Rules”, add:-

The Progress Bar is a publicly tracked pair of numbers, known as the Needle and the Maximum. The Gridmaster may, at any time, update the Maximum to be the number of Live Runners, and the Needle to be the number of Live Runners who have a Heading.

In the rule The Lines, replace the fourth step onwards in that rule with:

*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. Weight the random selection such that each feature not selected during the last Initialise action has twice the probability compared to any feature that was selected last time.
**If neither Database nor Access Point was select in the previous step, select one of those two at random and add it to the grid.
*If no Cells have a value of Battery, set the value of a random Cell to Battery
*Post a blog entry announcing the new Grid’s Features

In the effect of flow.c in the rule Disks, replace “When someone in your cell activates a disk other than flow.c. this trigger is met” with

When someone in your cell activates a disk other than flow.c, this trigger is met

If Computational Watches was not enacted, rename the rule “Terminals” to “Executions”, and change its text to read as follows:

Runners are able to Execute, though a Runner cannot Execute more than once in a given tick. Executing is an atomic action with the following steps:

*If the Runner has no Terminal in their location, they choose a Disk to activate in either Index 0 or Index 1 in their Stack, and pay an amount of power equal to that Index value plus 1.
*If the Runner has a Terminal in their location, they instead choose a Disk to activate which is in either their own Stack, or is in the Heap in a Cell whose value is Terminal, and pay power equal to the following criteria:
**If the chosen Disk is in their stack, they pay an amount of Power equal to half the Index value, rounded down.
**If the chosen Disk is in the Heap and is in the same Cell as them, they pay 2 Power.
**If the chosen Disk is in the Heap and is in a different Cell than them, they pay 6 Power.
*Whether or not the Runner has a Terminal in their location, they then Activate the chosen Disk.

Append the following paragraph to the rule “Disks”:

If they have not done so since the last Tick, a Runner may select a Disk in their Stack and pay Power equal to that Disk’s Index to Activate it.

Create a new rule, called “Perimeter”:

Each of the cells on the edge of the grid (those in the A and H rows, in addition to the ones in the 1 and 8 columns) are known as Border Cells.

In between the current second and third steps of the atomic action “Tick”, add the following step:

For each Runner that is not the Grue, if all three cells in that runner’s Spoor are a Border Cell and that runner’s location is also a Border Cell, set that runner’s location to a random non Border cell which has a value of “-” and which the Grue does not have as its location. Then, reduce the Capacity of the Stack for each runner that was moved in this way by 1.

In the rule “The Grue”, remove the following text:

If the Grue’s Location is changed and the Cell in the Grue’s new Location contains a Battery, the Gridmaster should process the Collect action as if requested by the Grue as described in the Power section of the rules.

In “Features”, replace “Then, select two random Cells from each of the rows or columns selected in the previous step and set their Values to “-”.” with:-

Then, if there are any Dark Sectors on the Grid, the Gridmaster should change random Cell Values which are orthogonally adjacent to a Dark Sector from Firewall to “-”, until no Dark Sectors exist. (A Dark Sector is a group of orthogonally-connected Cells where none of those Cells have either a value of “Firewall” nor identifications which are the Location of a Runner, and where all the Cells which are outside of that group and orthogonally-adjacent to a Cell in that group have a value of “Firewall”.)

To the end of “Basic Grid Rules”, add:-

Whenever the Gridmaster is required to make a random selection, they may do so in a secretly random manner.

In the rule “The Lines”, replace this text:

Select a random Feature and add it to the Grid.

With this text:

Select a random Feature and add it to the Grid, using the following faces for the die: {Energized, High-Security, Warped, Database, Database, Access Point, Access Point, Alpha Sector}

In the rule “Basic Grid Rules”, add a subrule titled “The Alpha Sector” and give it the following text:

The Alpha Sector is composed of all cells that are coloured Red.

To “Basic Grid Rules”, add a paragraph:-

A Runner is said to be “in” a Cell if their Location is the identification of that Cell. To “move” a Runner to a Cell is to set their Location to be the identification of that Cell. If a Cell’s Value is not “-”, it is said to “contain” an instance of that Value.

Where they appear in the ruleset, replace:

• “A Runner is Live if they have a Cell as their Location.” with “A Runner is Live if they are in a Cell.”
• “If multiple Runners share a Location which is a Cell” with “If multiple Runners are in the same Cell”
• “or the Cell in that direction has a Value of Firewall” with “or the Cell in that direction contains a Firewall”
• “Any Runner whose Location is set to a Cell whose value is Terminal” with “A Runner who is in a Cell which contains a Terminal”
• “the Heap in a Cell whose value is Terminal” with “the Heap in a Cell which contains a Terminal”
• “Whenever the Grue and another Runner have their Location currently set to the same cell” with “Whenever the Grue is Nearby another Runner”

You feel that tug in your stomach again, but it’s a little less nauseating this time. Once again, the lines blur for a moment and then stop.

The voice from your wrist-screen says “Three” at the same time that the number 3 shows up on the screen. That same red box shows up with the same warning:

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.

In “The Lines”, replace “Each week as a weekly action, the Gridmaster should, at their earliest convenience, Initialise, which is an atomic action with the following steps:” with:-

Loading a new Stratum is an atomic action with the following steps:

Add a bullet point before the final one in “Running”:-

* If no Cells have a value of Battery, Load a new Stratum

Add a bullet point before the final one in “The Lines”:-

* If no Cells have a value of Battery, set the value of a random Cell to Battery

Remove all the content from the rule “Power” except for the first and last paragraphs of it, and add a bullet point to “Running” after the second:-

* For each Cell whose value is Battery, and whose identification is the Location of one or more Runners: increase by 1 the Power of each such Runner, then set that Cell’s value to “-”

Change the value of Cell H8 to “-”.

Your wrist-screen beeps, and a new notification in green appears among the random lines and dots:

If the proposal “Showboating?” passed, revert it.

In the rule Basic Grid Rules, append the following text as a new paragraph:

Each Cell also has a publicly tracked colour, defaulting to Black. The colour of a cell is not considered to be part of its Value.

In the rule The Lines, replace “Set the Value of all Cells to -” with

Set the Value of all Cells to -, and set them to their default colour.

Create a new subrule of “The Grid” called “The Alpha Sector”:

The Alpha Sector is composed of all cells that are coloured Red.

In Running, change “Post a blog entry announcing the new Watch Number” to

Post a blog entry announcing the new Watch Number, and announcing any Runners whose Locations are cells in the Alpha Sector.

In the rule Features, add the following to the list:

* Alpha Sector: Privately randomly choose a number from 2 to 4 to represent the size of the Alpha Sector: 2 by 2 cells, or 3 by 3 cells, or 4 by 4 cells respectively. Privately randomly choose the location of the Alpha-Sector and colour all cells within the chosen region red. Then, set the value of a random cell within the Alpha Sector to Terminal.

In the rule Features, change “Database: Repeat the following 5 times: Select a Disk at random and add a new instance of it to the Heap in a random cell.” to:

Database: Repeat the following 5 times: Select a Disk other than junk.c at random and add a new instance of it to the Heap in a random cell.

Add the following Disks to the table of Disks in the rule Disks:

| -
| gain.c || 1 || If you are in the Alpha Sector, gain 3 capacity, then remove this Disk.
|-
| send.c || 2 || If you are in the Alpha Sector, you may add one junk.c disk between any two adjacent disks in any Runner’s Stack, or add it to the leftmost position of any Runner’s Stack.
|-
| junk.c || 2 || No effect.

In the Appendix rule “Names”, replace “may only include the 26 letters of the Latin alphabet, numbers, underscores, hyphens, full stops and apostrophes” with:-

may only include the 26 letters of the Latin alphabet, spaces, numbers, underscores, hyphens, full stops and apostrophes

For each Runner (and idle Runner) who included a comment on this proposal including the words “space please”: if that Runner has multiple capital letters in their player name, add a space before all but the first capital letter of that name.

Append to the rule The Grue

Whenever the Grue and another Runner have their Location currently set to the same cell, the Gridmaster should Derez that Runner and destroy any Disk at index 0 in that Runner’s Stack. A blog post should be made to declare that the Derezzed runner was “eaten by a Grue”.

You suddenly feel a strange tugging at the center of your body. The lines around you blur for a moment as you are pulled in the direction that you are facing. You’re nauseated for a moment, but then the feeling stops and the lines become sharp around you again.

The voice from your wrist-screen says “Two” at the same time that the number 2 shows up on the screen. Meanwhile, in the middle of the random lines and dots, a red box with text pops up:

In the rule Fair Play, remove the bullet point that reads “A Runner should not use a Core, Special Case, or Appendix rules scam to directly or indirectly cause a Runner to achieve victory.”

Add a new entry entitled “String” to the Appendix Keywords under the “Other” heading as follows:

A gameplay variable being defined as a “string” or a “text string” means that variable can hold a text value (being a mix of alphanumeric characters, punctuation, and spaces) of any length, unless more specifically defined by another rule.

If “Power Meter” is not enacted, this Proposal has no effect.

In the rule “The Grue”, add the following text:

Any time the Grue does not have a copy of yank.c in its Stack, the Gridmaster should add a copy of yank.c in its Stack if possible, according to the Stack section of the rules.

If the Grue’s Location is changed and the Cell in the Grue’s new Location contains a Battery, the Gridmaster should process the Collect action as if requested by the Grue as described in the Power section of the rules.

In “The Stack”, change

If the total Size of Disks on a Stack ever exceeds its Capacity, that Stack has Overflowed; the Runner or Gridmaster whose action caused a Stack to Overflow must repeatedly Pop that Stack until it is empty.

to

If the total Size of Disks on a Stack ever exceeds its Capacity, that Stack has Overflowed; the Runner or Gridmaster whose action caused a Stack to Overflow must repeatedly Pop that Stack until it only contains one Disk, then reduce its capacity by 1, unless reducing the capacity this way would cause the Stack to be Overflowed.

If Special Case [Reinitialisation] is inactive, this proposal does nothing.

Add a new subrule to “The Grid” named “The Battleship”:

The Battleship is comprised of cells D3, D4, D5, D6, E3, E4, E5 and E6.

In “Running”, change

Set the Value of all Cells to -

to

Set the Value of all Cells to -, except for those on The Battleship

and change

Post a blog entry announcing the new Watch Number

to

Post a blog entry announcing the new Watch Number, and any Runners who are on The Battleship.

Add the following Disks to the table of Disks in the rule Disks:

| -
| mem.c || 1 || If you are on The Battleship, gain 3 capacity, then remove this Disk.
|-
| write.c || 2 || If you are on The Battleship, you may add one dat.c disk to any Runner’s Stack in any position except the first.
|-
| dat.c || 2 || No effect.

In the subrule “Features”, change

Database: Repeat the following 5 times: Select a Disk at random and add a new instance of it to the Heap in a random cell.

to

Database: Repeat the following 5 times: Select a Disk other than dat.c at random and add a new instance of it to the Heap in a random cell.

Rename the rule “Runners” to “Power”

In the rule “Power”, add the following text at the end:

At any time, a Runner can privately request their current Power value from the Gridmaster, to which the Gridmaster should respond with the Runner’s current Power value.

Set the status of the Special Case rule “Reinitialisation” to Active.

If the proposal “Put on Your Running Shoes” failed, then add a paragraph to the end of “Running”:-

If the most recent Tick was more than 48 hours ago, the Gridmaster may Derez every Live Runner who has no Heading. When a Runner is Derezzed, their Location is set to a blank string and their Power to zero. The Gridmaster may also Derez a Runner at that Runner’s request, if they have not already Derezzed that Runner since the most recent Tick.

Replace “Each Runner optionally has a Heading, being a direction of North, South, East or West, and defaulting to not having a Heading” with

Each Runner optionally has a Heading, being a direction of North, South, East or West, or being Idle, and defaulting to not having a Heading

Replace “If all Live Runners have a Heading, the Gridmaster may perform the following atomic action, known as a “Tick”:-” with

If all Live Runners have a Heading, or no less than 36 hours have passed since the last Tick, the Gridmaster may perform the following atomic action known as a “Tick”:-

Add the following Disks to the table of Disks in the rule Disks.

| -
| swap.c || 2 || Swap the positions of two disks in your stack.
| -
| copy.c || 2 || Choose a disk at position 0 in any stack, and replace the type of any disk in your stack with the chosen disk’s type.
| -
| find.c || 1 || Get the identity and location of every runner within 3 cells of your location, and of the grue irrespective of its location.
| -
| wall.c || 2 || Put the value of Firewall in up to 3 cells with a value of “-” of your choice.
| -
| sell.c || 3 || Destroy any number of disks from your stack, and from the heap in your cell. Gain 1 power for each disk destroyed as a result of this activation.
| -
| flow.c || 3 || Trigger: When someone in your cell activates a disk other than flow.c. this trigger is met. When this disk is activated take 1 power from the runner that activated the disk that triggered this power, or from any Runner in your cell if this disk was activated by any other means. (The Gridmaster must inform you if you successfully took 1 power from them, or if you failed.)
| -
| meet.c || 3 || Trigger: When a runner’s Location is changed such that you now are in the same cell as another runner, this trigger is met. When this Disk is Activated as a result of meeting the trigger, you may activate the disk at index 0 in their stack, making all choices that it requires you to make. This Disk, (i.e. meet.c), may not be chosen as part of the Execute action.

Unidling; quorum is still 7

Add a new rule to the ruleset, called Texture Packs:

A Texture Pack is a publicly tracked non-variable set of information that contains a name and any number of Substitutions. Each Substitution is a single noun or verb from the dynastic ruleset that does not appear anywhere else in the ruleset (its Referent), along with another word of the same grammatical type that also does not appear anywhere in the ruleset (its Replacement). Texture Packs may only be created by Proposal or CfJ.

Each Runner has a publicly tracked variable for Texture, which may be blank or the name of a single Texture Pack, defaulting to blank. When a Runner’s Texture is not blank they may use its Replacements instead of its Referents whenever they would be used, including in votable matters.

At any time, any Runner may correct a Replacement that has made its way into the ruleset for its appropriate Referent. In all situations, the Referent of a Substitution is considered definitive for determining the meaning and interpretation of the Ruleset.

Create the following new Texture Pack:

Boats
Grid - Sea
Cells - Sectors
Gridmaster - Poseidon
Runners - Boats
Battery - Gust
Disk - Cannon
yank.c - 6 pounder
Push - Fire
Pushed - Fired
Heap - Fusillade
Stack - Battery

Rewrite the rule Location as follows:

There is a string variable named “Location” which is privately tracked by the Gridmaster for each Runner and is either a blank string or contains the identification of a Cell, defaulting to a blank string. At any time, a Runner whose Location is a blank string may privately request the Gridmaster to set their Location to a specific Cell. The Gridmaster should process these requests in the order in which they were received. If no other Runner has this Cell in their Location at the time the message is processed, the Gridmaster sets the Location of the Runner to the requested Cell and replies with an acknowledgement of the request. Otherwise, the Gridmaster replies that the Cell is taken.

There is a string variable called “Spoor” which is privately tracked by the Gridmaster for each Runner. A Runner’s Spoor is either a blank string or contains the identification of up to three Cells. Whenever a Runner’s Location changes, its former value is added to that Runner’s Spoor at its leftmost point. If this would result in that Runner’s Spoor containing a reference to more than three Cells then the rightmost value is removed from that Runner’s Spoor and is instead set as that Runner’s Ping.

A Runner’s Ping is a publicly tracked variable which may only hold Cell references, and which defaults to blank.

At any time, a Runner may privately request a Glance around their current Location from the Gridmaster, to which the Gridmaster replies with that Runner’s current Location, their full Spoor, and the names of all Runners (if any) who are Nearby that Runner.

Add a new subrule to “The Lines”, titled “Features”:

There are certain Features which change the way that a new Grid is generated. When the Gridmaster adds a Feature to the Grid, they carry out the instructions in that Feature, performing any random selections secretly randomly. The list of all Features is as follows:
**Energized**: Randomly select 5 Cells and set their Value to Battery.
**High-Security**: Select 3 random columns or rows in the Grid, and set the Value of all their Cells to Firewall. Then, select two random Cells from each of the rows or columns selected in the previous step and set their Values to “-”.
**Warped**: Set the Location of all Live Runners to a random Cell, and inform each of them of their new Location.
**Database**: Repeat the following 5 times: Select a Disk at random and add a new instance of it to the Heap in a random cell.

Append two new bullet points to the Initialise atomic action in “The Lines”:

*Repeat the following DICE4 times: Select a random Feature and add it to the Grid.
*Post a blog entry announcing the new Grid’s Features

In the rule “Running”, replace “unless there is not a Cell in that direction from that Runner’s Location” with “unless there is not a Cell in that direction from that Runner’s Location or the Cell in that direction has a Value of Firewall”.

If the Proposal “I’m afraid it’s terminal” was enacted, add a new Feature to the list in “Features”:

**Access Point**: Set the Value of the Cells in the corners of the Grid to Terminal. Then, randomly select 3 Cells and set their Value to Terminal.

Enact a new rule, “The Grue”:-

The Grue is an entity that counts as a Runner for the purposes of all dynastic rules. If the Gridmaster is required to notify the Grue of any information, they may instead choose not to do so.

If the Grue’s Location is a blank string and the Watch Number is 10 or higher, the Gridmaster may set the Grue’s Location to a secretly random Dormant Cell and its Heading to a secretly random direction from either North, South, East or West.

Add a step to the start of the bullet list in “Running”:-

* If the Grue’s Location is in the same row or column as any other Runners (excluding those in the same Cell as it), change the Grue’s Heading to face a secretly random such Runner.

Add another step after “Blank every Runner’s Heading”:-

* Set the Grue’s Heading to a secretly random direction from either North, South, East or West.

In the bullet point of the rule “The Lines” that begins “Privately randomly select…”, replace “Cells” with “Dormant Cells (or as many as can be selected, if fewer than that number exist)”.

Then add to the end of that bullet point:-

(A Cell is Dormant if no Runner has a Location in the same row or column as it, and if no Runner is in the Cells orthogonally and diagonally adjacent to it.)

If either of the proposals Memory Management or Round One were not enacted, this proposal does nothing. Otherwise:

To the end of The Stack, append:

Each Disk in a Stack has an Index. The rightmost Disk in a Stack, if such a disk exists, has an Index of 0. Each other Disk in the Stack has an Index of 1 greater than the Disk to its right.

To the end of the rule Disks as part of its final paragraph, append:

If a Disk’s Effect begins with “Trigger:”, then it may be activated by the Runner whose Stack it is in within 24 hours of when the triggering event described in that Disk’s Effect takes place.

Create a rule called “Terminals” as a subrule of “Disks”, with the following text:

Any Runner whose Location is set to a Cell whose value is Terminal is able to Execute, which is an atomic action with the following steps:
*They choose a Disk which is in either their own Stack, or is in the Heap in a Cell whose value is Terminal.
*They pay Power according to the following calculation:
**If the chosen Disk is in their stack, they pay an amount of Power equal to half the Index value, rounded down.
**If the chosen Disk is in the Heap and is in the same Cell as them, they pay 2 Power.
**If the chosen Disk is in the Heap and is in a different Cell than them, they pay 6 Power.
*They Activate the chosen Disk.

A Runner cannot Execute more than once in a given Tick.

In the table in Disks, add the following entries:
| link.c || 1 || Trigger: If this Disk is in a Stack and the Disk immediately to the right of this Disk is Activated, this trigger is met. When this Disk is Activated as a result of meeting the trigger, the Disk immediately to the left of this Disk is activated (if such a Disk exists). This Disk, (i.e. link.c), may not be chosen as part of the Execute action.
| halt.c || 3 || You may pay 1 Power. If you do, remove the value of Terminal from a cell of your choice.
| jump.c || 2 || You may set your Location to a cell whose value is Terminal by messaging the Gridmaster stating so.

If there is a rule called The Lines, in that rule replace “If they have not done so in the last 48 hours, the Gridmaster should, at their earliest convenience, Initialise” with

Each week as a weekly action, the Gridmaster should, at their earliest convenience, Initialise

If there is a rule called The Lines, in that rule replace “Privately randomly select 5 Cells and set their Value to Battery” with

Privately randomly select 10 Cells and set their Value to Battery

If there is a rule called Runners, remove the line “Set the value of the Cell contained in the Runner’s Location at the time of them making the request to -” and replace “if they haven’t already done so since the last Tick” with:

if they haven’t already done so since the last Tick, and haven’t done so for this Battery

If the Proposal “Pretty Little Rows and Columns” was not enacted, then this Proposal has no further effect.

Add a new dynastic rule, titled “Disks”:

There exists a number of Disks, each of which has a name by which it is referred to, a Size, and an Effect. The list of all types of Disk is as follows:

{| class="wikitable"
|+ Disks
|-
! Name !! Size !! Effect
|-
| yank.c || 2 || You may Push a Disk from the Heap which shares a row or column with your Location.
|}

When a Disk is Activated by a Runner, the Runner follows the instructions in that Disk’s Effect; a Disk’s Effect may only be carried out when it is Activated.

Add a new dynastic rule, titled “The Stack”:

Every Runner has a Stack, which is a publicly tracked ordered list of Disks defaulting to the empty list. Every Stack has a Capacity, which is a non-negative integer defaulting to 10. If the total Size of Disks on a Stack ever exceeds its Capacity, that Stack has Overflowed; the Runner or Gridmaster whose action caused a Stack to Overflow must repeatedly Pop that Stack until it is empty.

As a Weekly Action, a Runner with an empty Stack may add a copy of yank.c to their Stack.

When a Stack is Popped, its rightmost Disk is removed and added to the Heap in a Cell of the Popper’s choice (or a random Cell if the Gridmaster Popped it). At any time, a Runner may Pop their Stack.
When a Disk is Pushed, it is added to a Stack of the Pusher’s choice at the rightmost position and that instance of the Disk is removed from where it was previously being tracked.

Add a new dynastic rule, titled “The Heap”:

The Heap is a publicly tracked unordered list of Disks and the respective Cells of the Grid they are currently in, defaulting to the empty list. Every Disk in the Heap is tracked as a pair of its name and Cell (e.g. (yank.c, E4)).

I want to be unidled.

Add a subrule to “Location” called “Encounters”:-

If multiple Runners share a Location which is a Cell, then those Runners are all considered to be Nearby each other.

Whenever the set of Runners which are Nearby a Runner changes, the Gridmaster must privately inform that Runner of this.

In “Location”, replace “At any time, a Runner may privately request their current Location from the Gridmaster, to which the Gridmaster replies with that Runner’s current Location.” with:-

At any time, a Runner may privately request a Glance around their current Location from the Gridmaster, to which the Gridmaster replies with that Runner’s current Location and the names of all Runners (if any) who are Nearby that Runner.

If Proposal: Pretty Little Rows and Columns did not enact, skip the rest of this proposal.

Create a new dynastic rule named “Runners” with the following body:

Each Runner has a set amount of Power, which is a non-negative integer value privately tracked by the Gridmaster for each Runner.

If a Runner’s Location is set to a Cell whose value is Battery, the Gridmaster should notify them of this at their earliest convenience if they haven’t already.

While a Runner’s Location is set to a Cell whose value is Battery, if they haven’t already done so since the last Tick, they may privately request the Gridmaster to Collect, after which the Gridmaster should perform the following atomic action:
- Increase the Runner’s Power by 1
- Set the value of the Cell contained in the Runner’s Location at the time of them making the request to -

Create a new dynastic rule named “The Lines” with the following body:

The Stratum is a publicly tracked non-negative integer value that defaults to 0.

If they have not done so in the last 48 hours, the Gridmaster should, at their earliest convenience, Initialise, which is an atomic action with the following steps:
* Increase the Stratum by 1
* Set the Value of all Cells to -
* Privately randomly select 5 Cells and set their Value to Battery

Enact a new rule, “Running”:-

Each Runner optionally has a Heading, being a direction of North, South, East or West, and defaulting to not having a Heading: this is tracked privately by the Gridmaster. (Row A is considered to be the North edge of the Grid; Column 1 the West edge.) The Gridmaster may change a Runner’s Heading to match a Heading privately requested by that Runner, so long as no Tick has occurred since that request was made.

A Runner is Live if they have a Cell as their Location.

If all Live Runners have a Heading, the Gridmaster may perform the following atomic action, known as a “Tick”:-

* Simultaneously move every Live Runner one Cell in the Direction of that Runner’s Heading (unless there is not a Cell in that direction from that Runner’s Location)
* Blank every Runner’s Heading
* Increase the Watch Number by 1
* Post a blog entry announcing the new Watch Number

Enact a new rule, “The Watch”:-

The Watch Number is a publicly tracked number, starting at 1.

I unidle.

Add a new rule titled “Basic Grid Rules”, and give it the following text:

There is a Grid made up of Cells, where each Cell is a string variable with a default value of “-”, arranged in an 8 x 8 collection which is publicly tracked. The columns of the Grid are labeled with the integers 1 through 8 inclusive in numerical order, and the rows of the Grid are labeled with the letters A - J inclusive in alphabetical order. A specific Cell is identified by its row letter and column number in the Grid in the format “RowColumn”, where Row is the row letter and Column is the column number. e.g. The Cell in the fourth row and second column is identified as “D2”.

A Cell containing “-” is considered to be Empty.

Add a new subrule in the rule “Basic Grid Rules” titled “Location”, and give it the following text:

There is a string variable named “Location” which is privately tracked by the Gridmaster for each Runner and is either a blank string or contains the identification of a Cell, defaulting to a blank string. At any time, a Runner whose Location is a blank string may privately request the Gridmaster to set their Location to a specific Cell. The Gridmaster should process these requests in the order in which they were received. If no other Runner has this Cell in their Location at the time the message is processed, the Gridmaster sets the Location of the Runner to the requested Cell and replies with an acknowledgement of the request. Otherwise, the Gridmaster replies that the Cell is taken.

At any time, a Runner may privately request their current Location from the Gridmaster, to which the Gridmaster replies with that Runner’s current Location.

It is pitch black. You are likely to be eaten by a grue. Then again, maybe you’ll be fine. You don’t really know. You can hear the mumbling of other voices off in the distance, but you’re not sure where they’re coming from, or whether they are friendly or hostile.

A clear voice right next to you says, “It’s time to play Hide-and-Seek. But who are the Hiders and who are the Seekers? Maybe it’s others like you. Maybe it’s something else. You’ll find out soon enough, on the count of ten.”. You realize that the voice is coming from some sort of device strapped to your left wrist. The device, previously dark, now lights up with a random pattern of dots and lines, and you can see that it looks something like a digital touchscreen watch, although the touchscreen is a bit larger and is not displaying the time. Blue-hued lines fade into view around you, forming a square around you. Aside from the glow of those lines and the screen on your wrist, you see nothing else.

Next to the random lines and dots, the number “1” is displayed at the same time the voice from the device says, “One”.

The dynasty’s theme shall be “The Grid”.

Repeal all dynastic rules.

Set the synonym for Player to “Runner” and the synonym for Emperor to “Gridmaster”.

Change the gamestate tracking page to “The Grid”.

Set the Special Case rule No Collaboration to Active.

In the rule “Victory and Ascension”, in “no Idle Group may be made unidle”, replace Group with the current term for Player.

By the enactment of the Call for Judgement tpgc9lyfyz0, the random dice roll resulted in my name being drawn, therefore I have achieved victory.

Post dynasty comments and chit chats