Add a bullet point to the atomic action in the Battlefield rule:-

* If the Bogey is still in play, apply all Reactions of its Features to this Fire Post, in the order that they are listed in the ruleset.

Create a subrule of “DEVAs” called “Features”, with the following text:-

The named Features of DEVAs, and those Features’ Reactions, are listed below (with the name in bold and the Reaction afterwards):-

* ‘’‘Deflector Shield’‘’. If the Fire Vector is smaller than the Bogey’s defense, the Bogey gains 1 defense, if this would bring the Bogey’s defense above the maximum it becomes the maximum instead and the Poindexter should add a comment saying that the Bogey’s shield has shorted out.
* ‘’‘Radiant Beam’‘’. If the Fire Vector is greater than the Aggressor’s Defense, the Aggressor’s Power is reduced by 10.

Add a DEVA sub-species to the tracked list:-

Designation OPHANIM, Energy range 11-20, Attack range 11-20, Defence range 11-20, 75% chance of “Radiant Beam”, 50% chance of Deflector Shield.

Remove the definition of Deflector Shield (and the quotemarks around it) from the Ansible Hangar, if it exists there.

hey, I’d like to unidle

haven’t had time to play the past few days unfortunately

Pilot Lendunistus idles out automatically after seven full days without a post or a comment from them. Quorum drops to 6.

If “Mod Your Pod” doesn’t pass, nothing happens.

Otherwise,

In rule “Shells”, subrule “Mod”, under “The following is the list of Modules that are approved by RAID R&D:”, add:

Side Jets(Attachments)
Modifiers: -20% Power +10% Attack +10% Defense

In section “Mechanoids” change

Until a Pilot assigns or sets themselves a Mechanoid, they will be set to “-”.

Pilots can only assign themselves 1 Mechanoid.

Mechanoids can help assist Pilots in combat or research.

to

Mechanoids can help assist Pilots in combat or research.

Ownership of any Mechanoids will be tracked on Ansible Hangar. Until a Pilot assigns or sets themselves a Mechanoid, they will be set to “-”.

More than one Pilot can own the same Mechanoid Type.

Pilots can only assign themselves 1 Mechanoid.

I’m the ruleset, replace the string “An individual DEVA is known as a Bogey, and has statistics” with “A DEVA has statistics”.

Add a new rule to the ruleset, called The Future Is Already Written:

A DEVA becomes a Bogey when it enters the game. All Bogeys are publicly tracked.

The Poindexter is responsible for privately scheduling and tracking, and then publicly or secretly (as appropriate) carrying out, the actions of all DEVAs. For each DEVA, the Poindexter should secretly keep a chronological list of planned actions and when they will occur. To whatever extent is possible, the Poindexter must generate and maintain any necessary information to map out the generation and actions of any DEVA for at least the next week. If a DEVA’s planned actions do not cover the full period of the next week then the Poindexter should randomly generate new actions for it until the full period of the next week is scheduled with actions.

Subrules to this rule detail actions that the DEVAs may take, how they are generated and how information about them is tracked.

All scheduled actions for a DEVA must include a specific date or time at which they will come into effect. Planned DEVA actions should be enacted by the Poindexter as close to that date or time as possible. If the specific time is missed then the Poindexter should carry it out at their first opportunity thereafter.

If a DEVA’s scheduled action can’t legally take place for any reason (such as an invalid target) then it is stunned and all subsequent actions on its schedule are delayed for 48 hours.

Add a subrule to that rule, called Emerging from the Breach:

When Poindexter has created a new DEVA, the first item on its schedule should be Emerging from the Breach. Emerging from the Breach may not be selected as an action for a Bogey. When a DEVA carried out an Emerging from the Breach action, they enter the game, become a Bogey, and become publicly tracked. A DEVA should Emerge from the Breach at a secretly randomly selected time between 24 and 120 hours after it has been created.

The date and time upon which the next new Bogey will Emerge from the Breach is publicly tracked information.

Add a further subrule to the rule called The Future Is Already Written, called Attack a Civilian Target:

When attacking a civilian target is added to a DEVA’s schedule, it must be scheduled to take place between 2 and 72 hours after the action on that schedule that takes place immediately before it. Whenever a Bogey’s attack on a civilian target is enacted, Poindexter must make a blog post informing the Pilots that the attack has taken place.

Add a further subrule to the rule called The Future Is Already Written, called Attack a Military Target:

When attacking a military target is added to a DEVA’s schedule, a Jockeying Pilot must be secretly randomly selected as its target, and it must be scheduled to take place between 48 and 96 hours after the action on that schedule that takes place immediately before it. Whenever a Bogey’s attack on a military target is enacted, Poindexter must make a blog post informing the Pilots that the attack has taken place and the Attack value of the Bogey who carried it out, which then becomes publicly tracked information. The targeted Pilot then loses Power equal to the Attack of the Bogey minus their own Defence.

Add bullet points to the list of Shell Archetypes so that each name has “*” in front of it and each other line describing an aspect of a Shell has “**” in front of it.

Add bullet points to the list of Mechanoids so that each line has “*” in front of it.

Add bullet points to the list of Modules, merging each pair of lines into a single line with a “*” in front of it.

Reformat the “MECHATECH”, “Dynocorp” and “Azamo’s Children” parts of the ruleset to be subrules of “Corporations”.

Add the following to the end of the rule Shells:

If a Jockeying Pilot ever has a Power of zero then their Shell is destroyed. A Jockeying Pilot with a destroyed Shell must set their status to Demobbed and blank their Archetype, Power, Attack and Defence.

Add a new rule to the ruleset, called Pilots:

Each Pilot has the following trackable variables: Experience and Memes.  Experience and Memes can never be lost.

Experience can be gained in the following ways:

* A Pilot gains 1 Experience every time they start Jockeying a new Shell
* A Pilot gains experience equal to the Experience Value of a Bogey’s sub-species whenever a Bogey is removed from the game as a result of one of their Fire Posts
* A Pilot gains 1 Experience every time they cease to be Jockeying because their Shell is destroyed

A Pilot may exchange Experience for Memes whenever they are Demobbed. Available Memes, their costs, and their effects are as follows:

* Rakshasha Targeting: Cost: 5 Experience. Effect: When Firing on a Rakshasha Bogey, a Pilot with this Meme may select a range of two contiguous integers as the attack’s Fire Vector.

Deactivate the special case rule Imperial Deferentials.

Add the following to the tracked DEVA sub-species:

Designation KNIGHT, Energy range 90-125, Attack range 10-28, Defence range 5-25, 75% chance of special feature “Deflector Shield”: “When a fire post is resolved against this Bogey, if the fire vector is smaller than this Bogey’s defense, this Bogey gains 1 defense, if this would bring this Bogey’s defense above the maximum it becomes the maximum instead and the Poindexter should add a comment saying that the Bogey’s shield has shorted out.”.

Add a new dynastic rule called “Corporations”

Each Pilot has a publicly tracked Affiliation, which may be one of the Corporations listed as subrules of this rule and by default is Unaffiliated. Two Pilots whose Affiliation are the same Corporation are said to be Affiliated with each other.

Each Corporation has a Creed, which is Flavor Text.

Each Corporation has a Requirement. An Unaffiliated Pilot may change their Affiliation to any Corporation for which they meet the Requirement.

== MECHATECH ==

Creed: Growth At All Costs

Requirement: Any Pilot may join MECHATECH

== Dynocorp ==

Creed: Only the Strong Survive

Requirement: A Pilot’s Power must be at or above 100 to join Dynocorp

== Azamo’s Children ==

Creed: Fortune Favors Us

Requirement: Roll a DICE3 and have the result be a 1. Each Pilot may only attempt this once.

Add a subrule to the rule “Shells”. Call it “Custom Shells” and give it the following text:

A Shell Subtype is a Shell Archetype combined with one or more distinct Modules. Its name is the Shell Archetype’s name preceded by the modules’ Module Adjectives, and its default Power, Attack and Defense are the Shell Archetype’s respective stats multiplied by 100% plus the total respective modifiers of those Modules (with unspecified modifiers defaulting to no change). A Shell Archetype has a numerical Module Limit associated with it, defaulting to 1. Its Shell Subtypes may each have at most that many Modules.

In the rule “Shells”, replace the text “they may select a Shell Archetype” with “they may select a Shell Archetype or Subtype” and “the following tracked information: a Shell Archetype” with “the following tracked information: a Shell Type (whether Archetype or Subtype)”

Add a new subrule to the rule “Shells”. Call it “Mods” and give it the following text:

Each module has a name followed by its Module Adjective in parentheses, followed by its Modifiers, followed by an optional Special Effect which is ruletext that only applies to a Jockeying Pilot whose current Shell Subtype has that Module.

The following is the list of Modules that are approved by RAID R&D:

Default Configuration (Basic)
Modifiers: +0% Power

Auxiliary Reactor (Boosted)
Modifiers: 20% Power -20% Defense

Structural Reinforcement Plates (Plated)
Modifiers: -20% Power 20% Defense

Add a subrule to DEVAs named “Too many”:

If there are more Bogeys than active Pilots, any Pilot may remove the dynastic rules, beginning a metadynasty with no Poindexter.

Add a new rule to the ruleset, called Mechanoids:

Until a Pilot assigns or sets themselves a Mechanoid, they will be set to “-”.

Pilots can only assign themselves 1 Mechanoid.

Mechanoids can help assist Pilots in combat or research.

Add a new subrule to that rule, called Mechanoid Type

Fire Mechanoid - No description
Water Mechanoid - No description
Wind Mechanoid - No description
Earth Mechanoid - No description
Dark Mechanoid - No description
Electric Mechanoid - No description
Metal Mechanoid - No description

Replace “An individual DEVA has statistics” with:-

An individual DEVA is known as a Bogey, and has statistics

Replace “generate a new DEVA” with “generate a new Bogey”.

Add a new rule, “The Battlefield”:-

A Jockeying Pilot may fire on a Bogey by making a blog post that specifies a Bogey as its target, and an integer number from 1 to 100 as the attack’s Fire Vector. This is known as a Fire Post.

As an atomic action, the Poindexter may resolve the oldest Fire Post that they have not already resolved, as follows (where its poster is the Aggressor):
* If the Fire Vector is exactly equal to the Bogey’s Defence, and is no greater than the Aggressor’s Attack, then the Bogey is removed from play and the Poindexter adds a comment to say this.
* If the Fire Vector is above the Bogey’s Defence, the Poindexter adds a comment to say that the Bogey has evaded the shot.
* If the Fire Vector is below the Bogey’s Defence, the Poindexter adds a comment to say that the Bogey has deflected the shot.

Add a new rule to the ruleset, called DEVAs:

There are various sub-species of DEVA, each of which has its own characteristics. Each sub-species of DEVA has a Designation (which is flavour text), an Energy range, an Attack range, a Defence range and a list of possible special features.

The known sub-species of DEVA are tracked on the Ansible Hangar page of the wiki.

An individual DEVA has statistics that are secretly tracked by Poindexter, that fall within the ranges for that DEVA’s sub-species. Whenever Poindexter has to generate a new DEVA, they should secretly randomly determine its Energy, Attack and Defence based on the published ranges, and secretly randomly determine whether it has any of the special features possible for its sub-species.

Add the following to the tracked DEVA sub-species:
Designation RAKSHASHA, Energy range 110-145, Attack range 32-57, Defence range 21-34, no special features.

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

General Jenny Haniver, Fleet Commander of the Earth Deep Space Expeditionary Corp, entered the ISV Relentless Inquisition’s Crisis Room at 4.37am Sol Adjusted Time and threw herself unceremoniously into the chair at the head of the table. The assorted Generals and other attendees at the table sat ramrod straight, eyes forward, as she lit a cigar and fixed them with a baleful gaze.

“Let’s have it, then.”

Captain Ken Park stood and gestured towards the holoboard, which lit up and started scrolling images and information. “At 2.14am SAT this morning we received word that the seal containing the DEVAs was breached.”

Cmdr Haniver looked impassive but several gasps and groans of dismay could be heard around the table.

“As best as we can make out, the breach took place on the planet Blogia, when some of the local pre-Type-One human civilization completed a tile mosaic that just happened to be the quantum key to the DEVA’s 5th-dimensional cage.”

“Gimme a break”, rasped Haniver around her cigar. “What are the odds.”

“It’s a big universe,” said General Hannah Pak, Commander of the Fleets. “Sooner or later it was bound to happen.”

“We should have wiped them out long ago,” added another General.

“That was never an option,” said Haniver. “Probably isn’t an option now. Last time humanity squared up against the DEVAs they knocked us back to the dark ages. Decimated our population, probably held us off of Kardashev Type 1 for a millennium.” An uncomfortable silence fell around the table.

“Options, people,” said the Commander after a moment.

“I have a core-buster ready to deploy,” said General Pak, to instant dismay at the table. Haniver raised a hand and silenced the room. “Within eight hours I can have Blogia wiped off the map, and everything on it.”

“Surely we can manage this situation without needing to resort…” began General Omololu, but Hanniver silenced her with a look.

“This is the DEVAs, people. None of us squared off against them last time and I’m not sure that any of us want to this time. All options are on the table.”

“My concern…” came a small, querulous voice from the food of the table.

“What the fuck is he doing here?” snarled General Pak.

“I have as much right…”

“He’s half DEVA!” General Omololu gestured at the new speaker while looking to Cmdr Haniver for support.

None was forthcoming. “I asked Specialist Poindexter to be here,” she said, knocking the ash off of her cigar. “In this instance, his lineage is an asset. Please go on, Poindexter.”

“Thank you,” said Poindexter, his angular eyes flitting around the room defensively. “As I was saying, the concern is that merely destroying the planet would not, in fact, destroy the breach itself, and that DEVAs can – as we know – survive and still be a threat in deep space. Sooner or later we would face the problem again.”

“Do you have a better solution?”

“As a matter of fact, I do.”

Specialist Poindexter stood, drawing himself up to his full nine feet in height. As he walked over to the holoboard the articulation of his arm and knee plates made it look a if he was gliding. Captain Park handed him the control baton and stepped aside.

“I propose,” said Pondexter, “that we make use of the presence of the Ansible in the area and deploy the Rapid Atmospheric Insertion and Deployment team against the DEVAs. With the Ansible’s ability to transmit limitless quantities of information instantly, RAID pilots can remotely pilot mechanical shells against the DEVAs with no risk to themselves, allowing them to learn new tactics and retain knowledge of how to defeat the enemy. With only a small amount of retrofitting, the Ansible can also be used to synthesise stellar matter to produce functionally limitless numbers of new shells, meaning that we will be able to deploy an army that is self-sustaining. We will have the opportunity to see past the superior firepower of the DEVAs, and perhaps even work out how to defeat them once and for all.”

“Absurdly risky,” cried General Omololu. “If even one of them makes it off of that planet then –“

But Commander Haniver had leaned forward in her seat. “If that happens then at least we will have the benefit of RAID’s information on the DEVAs and how to defeat them. I like it. The DEVAs have been locked away for generations – they’re weak. This might be our best chance. Okay. Generals Omololu and Pak, please draw up contingency plans for deep space combat against the DEVAs. For now – Poindexter – you are green to go.” She stood, looked around the room at the tense, confused, despairing faces. She briefly considered saying something comforting or inspiring, but instead just nodded. “Dismissed.”

Repeal all dynastic rules. Throughout the ruleset, change the term Monk to Pilot and Abbot to Poindexter. Deactivate the Traitor Special Case rule.

I’d like to unidle.

May I be unidled? Thanks

I’m going to take a day or so to consider my options so consider this a thread for a post-dynastic washup.

I enjoyed the core mechanism but felt that it didn’t come together in the end.

Unidle me please =)

As per the rule Desiderata and the Abbott’s declaration, I have achieved victory.

The Mosaic is Complete

With an Accomplishment of 29 (or 14, depending on how you count), Josh is the Artisan

With 4 spots left, we are nearing the end of this dynasty. As I wish we could have had more interesting mechanics that would have made end game more interesting, it’s been a pleasure creating this masterpiece. And hopefully to whoever is declared winner will make an interesting chapter as well.

I’m reverting two Circle Benedictions made at the same time by Josh. 11-1 because a circle must be eight tiles, and 11-3 because a circle must set the center tile to the color of an adjacent (not diagonal) tile.The CfJ shouldn’t have ratified those either since it only affected color choices “as required by its Motif”.

Add the following line to the end of the rule “Natural Colors”

Jewel: blue, cyan, green, lime, pink, purple, red

The intent of the Circle Motif is clear, even though per the proposal “A Motif Squared”, its Benediction is mislabeled as a Motif.

Set the color of the tiles 7-4, 4-10, 2-10 and 13-13 to black. For each Circle claimed while this CfJ was pending, where the center tile was white at the time and where the Monk completing the Motif chose a color as required by its Motif, set the color of the center tile to the chosen color.

In the rule “Motifs”, change the text:

A Circle is eight tiles that compose the border of a 3x3 square. Its Motif:

to

A Circle is eight tiles that compose the border of a 3x3 square. Its Benediction:

If the CfJ “Pins and Wheedles” has enacted, this CfJ has no further effect.

Fail the CfJ “Pins and Wheedles”.

Reword the Pinwheel Motif to:-

A Pinwheel is 2x2 square of four different colours. Its Benediction is: If no other Pinwheels exist on the Mosaic with these same four colours, change the colours of any 2x2 square of White Stone Tiles to match this Pinwheel.

Uphold, in chronological order, every attempted game action which is either:

• The application of a Pinwheel Benediction; or
• The direct reversion of such an action as illegal

...up to (and including) the performance of this action.

Then make the materials of tiles 10-1, 1-8 and 1-9 into stone.

The Pinwheel motif reads:

Pinwheel: A Pinwheel is 2x2 square of four different colours. Its Benediction is: If no other Pinwheels exist on the Mosaic with these same four colours, replace any 2x2 square of White Stone Tiles with a copy of this Pinwheel.

I have been taking the effect of the pinwheel as meaning that the colours are transposed to white stone tiles, meaning that the destination tiles retain their stone-ness. Kevan has been taking the effect of pinwheels to mean that the tiles are transferred in toto, with their source material replacing the stone of the destination material.

This has material consequences (excuse the pun) - all of the black tiles on the board are from pinwheels or reworking, so under Kevan’s interpretation, they should be ink that could not have been erased and should therefore be restored. Doing so would invalidate several subsequent moves and would take an age to unpick.

The proposed solution is the line of least resistance: reword the pinwheel motif as follows:

Pinwheel: A Pinwheel is 2x2 square of four different colours. Its Benediction is: If no other Pinwheels exist on the Mosaic with these same four colours, replace any 2x2 square of White Stone Tiles with a copy of the colours of this Pinwheel.

Uphold, in chronological order, all edits made to the Mosaic page up to this one, then make the materials of tiles 10-1, 1-8 and 1-9 into stone.

Set all backing tiles to grey stone.

The cloister bell tolls, and Brother Josh and Brother Kevan are still debating points of scripture across the refectory table. “While the Lord resisteth the proud,” says Brother Josh, raising an empty fork to tap the air dramatically, “it is only implicit in his word that his servants should encourage one another to humility through their actions. Were it so that they declined or failed in that task, or that a servant of the Lord toiled alone without witness, that measure is theirs alone. They would face their maker’s resistance directly, and who are we to discern the precise scales of the Lord?” The last of the evening’s candles begins to gutter. “You will observe that none of my vows have been broken here…”

Yesterday it was made very clear that Brother Josh has the colour Black among his Desideratum, yet in that time only I have stepped up to cover any of his Black Tiles, with Raven contributing a Black Tile of their own. Are any other Monks interested in reducing this colour’s prominence in the Mosaic, or could it be that a quorum of Monks have Black in their Desiderata and are entirely happy to see it increase? (I appreciate that such Monks would rather remain silent.)

If any Monks are deliberately sitting the gameplay out on this one: I’ll say now that if the dynasty ends with me as victor and this is due to an absence of Black Tiles (let’s say: if the Mosaic were considered to have 100 additional Black Tiles, I would not have won), I’ll give a bounty of 1% of that victory for each Black Tile covered by a player during the dynasty from today onwards. By which I mean, for the benefit of new players: if Monk A covers 12 Black Tiles and Monk B covers 3, I will roll a 100-sided die after victory and on a roll of 1-12, pass the victory to Monk A; on a 13-15 pass it to Monk B; on a 16+ keep the victory. Private negotiations are welcomed.