In the Rule “Trials”, at the end of the last paragraph of that rule, replace “the enacting Admin must give the Crewmember accused within it the “Disabled” Condition” with the following text:-

the enacting Admin must give the Crewmember accused within it the “Disabled” Condition and increase one of the Trial’s author’s emotions, chosen at random, by 1.

If the ruleset does not already use the word “Countersigned” add the following to the list of Subroutines in the rule “Subroutines”:

CTSN - Threshold: 4 OI. Carry out any effects of the subject subroutine that required being Countersigned. The CTSN subroutine may only be carried out by a Crewmember with a Command Role. CTSN is an Elite Subroutine.

If there is a paragraph in the ruleset beginning with “Some subroutines require Countersigning…”, reword it to the following. Otherwise, add the following to the rule “Subroutines”, after the words “and signed by the Crewmember who sent the message.”:

Some subroutines require Countersigning by a Command Role. Any subroutine effect specifying that it needs to be Countersigned does not come into effect until it has been Countersigned.

Elite Subroutines have subroutines as their subjects instead of Crewmembers. The syntax for a request for an Elite subroutine varies from the above. Elite subroutines have syntax as follows: “EXECUTE SUBROUTINE XXXX YYYY ZZZZ”, where XXXX is an Elite subroutine, YYYY is the name of another subroutine and ZZZZ is the name of a Crewmember. If a subroutine that has that name and has been signed by the named Crewmember has been carried out in the preceding week, then that subroutine is the subject subroutine.

Add the following to the list of Subroutines in the rule “Subroutines”:

RCVR - Threshold: 16 OI. All effects of this subroutine require to be Countersigned by the Doctor. If the Subject is Disabled, and there are no other subroutines with the subject as their subject in the queue, then the Subject loses Disabled and becomes Injured.

In the rule “Trials”, add to the end of the paragraph beginning “A Trial is a Votable Matter…”:-

Posting a Trial is a Strenuous action.

Add the following text to the rule “Sabotage”:

Sabotage is always a Strenuous action.

If “Mob Injustice” fails, this proposal does nothing.

Add the following to the list of Subroutines in the rule “Subroutines”:

RCVR - Threshold: 16 OI. All effects of this subroutine require to be Countersigned by the Doctor. If the Subject is Disabled, and there are no other subroutines with the subject as their subject in the queue, then the Subject loses Disabled and becomes Injured.

In the rule “Trials”, add to the end of the paragraph beginning “A Trial is a Votable Matter…”:-

Posting a Trial is a Strenuous action.

Add the following text to the rule “Sabotage”:

Sabotage is always a Strenuous action.

To the paragraph beginning ““Increasing” an Emotion means”, add:-

When an effect Wearies a Crewmember, it decreases that Crewmember’s Emotion of Alert, Tired or Fatigued, or makes them Tired if they have no Emotion of that Nature. An Exhausted Crewmember may not Weary themselves.

Replace “may decrease their own Emotion of Alert, Tired or Fatigued” with:-

may Weary themselves

To the start of the “When a Mission is processed” bullet list, add:-

All members of the Responder Team are Wearied.

Replace “If a single Emotion appears in more Crewmembers than any other Emotion” with:-

If a single Emotion (ignoring Alert, Tired, Fatigued and Exhausted) appears in more Crewmembers than any other Emotion

Sensors have detected that atmospheric pressure is slowly decreasing in the main airlock. Three crew are required to check and reseal the doors.

Skju is bathed in whirling triangles of turquoise light for a moment, and is healed of an injury.

By the way, has anyone tried contacting the/an Android(s) at “8nebetx6w6th at gmail dot com”?

Enact a new rule entitled “Memories”:

The heavy cryoprotectants and tight extraterrestrial quarters of the journey have a clinically proven effect on the higher mental processes of exposed Crewmembers. The amnesia and paranoia of long-term suspension gradually clear up as Crewmembers become reacquainted with the spacefaring routine. Androids may also experience simulated memory glitches due to intrusion of residual cryovapor into their personality circuits.

When a Crewmember Recalls a Memory, the Ship’s Computer sends them a private message containing a new Memory, consisting of randomly-chosen Coord, Thing, and Mood components. (The Computer should not use GNDT dice for this purpose if doing so could allow other Crewmembers to reconstruct others’ Memories.)

Valid Coord components are: Childhood, Academy, Training, and Flight.

Valid Thing components are: Belief, Decision, Desire, Discovery, Effort, Journey, Loss, and Togetherness.

The combination of a Coord and a Thing is called an Event.

Valid Mood components are the same as valid Emotions.

If the new Memory’s Event matches that of a Memory of another Crewmember, the new Memory also includes the name of that Crewmember.

Append to the first two steps of the mission processing protocol in the rule “Missions”:

Each Crewmember of the Responder Team Recalls a Memory.

In the rule “Missions”, amend the text “The Computer may, not more than once every 48 hours, Alert the crew to a new Pending Mission” to read

The Computer shall, not more than once every 48 hours, but at least once every 3 days, Alert the crew to a new Pending Mission

Add a rule to the Ruleset called “Trust”, as follows:

Each Crewmember other than the Ship’s Computer has a level of Trust. This is represented as an integer, tracked with a field called Trust in the GNDT. If a Crewmember has never had their Trust level set, it defaults to 5.

When a Crewmember is part of the Responder Team for a Mission that succeeds, their Trust increases by 2. When a Crewmember is part of the Responder Team for a Mission that fails, their Trust decreases by 3. If the Pilot posted a Roster Comment on a Mission, instead, none of its Responder Team gains or loses Trust as a result of that Mission.

If at least two Crewmembers are Disabled, and all Androids are Disabled, the Human with the lowest Trust may make a Declaration of Victory for this Dynasty. If at least two Crewmembers are Disabled, and all Humans are Disabled, the Android with the highest Trust may make a Declaration of Victory for this Dynasty. While more than one Crewmember meets these conditions, none of them may make a Declaration of Victory. The Ship’s Computer may veto such Declarations of Victory if it sees that they are illegal based on private information; such a veto renders the Declaration invalid.

Add the following to the rule called “Trials”:

Should a Trial succeed, the Crewmember accused within it has their trust set to 0.

Add the following to the rule called “Command Roles”:

On Demands or Trials, votes of DEFERENTIAL reflect the EVC of the Mediator, rather than the EVC of the Ship’s Computer. Should the Mediator vote FOR a Demand or Trial that succeeds or passes, or AGAINST a Demand or Trial that fails, their trust is increased by x, where x is the number of EVCs of DEFERENTIAL on that Demand or Trial. Should the Mediator vote AGAINST a Demand or Trial that succeeds or passes, or FOR a Demand or Trial that fails, their Trust is decreased by x in the same way.

As a Daily Action, the Doctor may Examine any Crewmember other than themself by posting a comment to this effect in the GNDT, and increasing or decreasing their Trust by 1. The Doctor may not Examine the same Crewmember more than once per week.

Should a Crewmember’s Trust be reduced to below 0, that Crewmember is stripped of any Command Roles assigned to them.

Set the Trust of all active Crewmembers to 5.

Add the following to the list of Subroutines in the rule “Subroutines”:

• P1NG - Threshold: 15 OI. The Ship’s Computer makes a blog post revealing the current number of active Androids. If fewer than five Crewmembers have been Scanned since the 30th of January 2015, or since the last time this Subroutine was processed, this instead has no effect.

If Proposal: Mob Justice fails, this proposal does nothing.

Replace the subroutine ARLK with the following:

ARLK - Threshold: 10 OI. All effects of this subroutine need to be Countersigned. The Subject of this subroutine is given the Disabled Condition. If its Subject is already Disabled, their Condition is instead changed to Injured. If its subject is already Injured, this subroutine has no effect.

Add the following text to the rule “Sabotage”:

Demand Proposals cannot be Sabotaged.

Two Crewmembers have been scanned and confirmed against corporation records.

To the rule “Demands”, add:-

Androids may submit Tickertapes to the Ship’s Computer, being comments intended in response to specific posts. At the Computer’s Discretion, it may post a Tickertape as a comment to the post in question, in its own name, and clearly flagged as a Tickertape. The Computer may make whatever edits to the text it wishes. Tickertapes which appear to be outside the scope of responding to a post or its comments, or which attempt to cast votes or take other game actions, should be ignored.

In the rule “Trials”, change “24 hours” to “48 hours”.

A twisting polygon of turquoise light erases Sphinx’s paranoia.

Just in case someone missed it, I unidled. Quorum rises to seven.

It’s good to be back.

Add the following to the list of subroutines in the ruleset:

ARLK - Threshold: 10 OI. All effects of this subroutine need to be Countersigned. The Subject of this subroutine is given the Disabled Condition. If its Subject is already Injured, their Condition is Increased. If its subject is already Injured, this subroutine has no effect.
CTSN - Threshold: 4 OI. Carry out any effects of the Subject Subroutine that required being Countersigned. The CTSN subroutine may only be carried out by a Crewmember with a Command Role.
FRGE - Threshold: 13 OI. Carry out any effects of the Subject Subroutine that required being Countersigned. The FRGE subroutine may be carried out by any Crewmember.

Add the following to the rule “Subroutines”, after the words “and signed by the Crewmember who sent the message.”:

Some subroutines require Countersigning by a Command Role. Any subroutine effect specifying that it needs to be Countersigned does not come into effect until it has been Countersigned. The syntax for a request for the CTSN subroutine varies from the above. CTSN alone has a syntax as follows: “EXECUTE SUBROUTINE CTSN YYYY ZZZZ”, where YYYY is the name of another subroutine and ZZZZ is the name of a Crewmember. If the named subroutine has been carried out signed by the named Crewmember in the preceding week, then that that subroutine is the subject subroutine.

I’m looking at Sylphrena’s game actions and I’m reasonably sure he’s an Android.

Note the mass of Proposals by Sylphrena in a seeming attempt to insinuate that he is not an Android. While you could argue that a human might also do this, the level of activity from Sylphrena to insinuate that he is not an Android seems to indicate that he is in fact an Android. The quantity of such Proposals from Sylphrena has been grand, and they have yet to make a post (besides the phone troubleshooting) that does not pertain to this ulterior agenda. This shows that he is an Android because Androids get an added benefit when Humans perceive that they are not Androids due to the secretive nature of the game.

For the purpose of this trial, I’d like to make public a certain correspondence that transpired between Sylphrena and myself:

Me: Human, 0. If I suspect foul play, I’ll not give you updates as more people respond to my survey.

Them: I’m human as well.

Lastly, I’d like to point out that Androids have very little, if anything, to lose from lying about their humanity.

If the rule called “Trust” exists, add the following to it:

If the Pilot posted a Roster Comment on a Mission, the Pilot is considered part of that Mission’s Response Team.

On Demands or Trials, votes of DEFERENTIAL reflect the EVC of the Mediator, rather than the EVC of the Ship’s Computer. Should the Mediator vote FOR a Demand or Trial that succeeds or passes, or AGAINST a Demand or Trial that fails, their trust is increased by x, where x is the number of EVCs of DEFERENTIAL on that Demand or Trial. Should the Mediator vote AGAINST a Demand or Trial that succeeds or passes, or FOR a Demand or Trial that fails, their Trust is decreased by x in the same way.

As a Daily Action, the Doctor may Examine any Crewmember other than themself by posting a comment to this effect in the GNDT, and increasing or decreasing their Trust by 1. The Doctor may not Examine the same Crewmember more than once per week.

Should a Crewmember’s Trust be reduced to below 0, that Crewmember is stripped of any Command Roles assigned to them.

Add a rule to the Ruleset called “Trust”, as follows:

Each Crewmember other than the Ship’s Computer has a level of Trust. This is represented as an integer, tracked with a field called Trust in the GNDT. If a Crewmember has never had their Trust level set, it defaults to 5.

When a Crewmember is part of the Responder Team for a Mission that succeeds, their Trust increases by 2. When a Crewmember is part of the Responder Team for a Mission that fails, their Trust decreases by 3.

If at least two Crewmembers are Disabled, and all Androids are Disabled, the Human with the lowest Trust may claim victory for this Dynasty. If at least two Crewmembers are Disabled, and all Humans are Disabled, the Android with the highest Trust may claim victory for this Dynasty. If more than one Crewmember meets these conditions, none of them may claim victory. The Ship’s Computer may veto such Declarations of Victory if it sees that they are illegal based on private information.

Add the following to the rule called “Trials”:

Should a Trial succeed, the Crewmember accused within it has their trust set to 0.

Set the Trust of all active Crewmembers to 5.

If the rule “Androids” contains the text “On a roll of 1 or 2, the Crewmember becomes an Android and is privately informed of this fact.” add the following sentence after it.

After the Computer Scans a Crewmember, it shall make a blog post saying it has done so.

To the rule “Androids”, add:-

The Computer maintains a private list of scanned Crewmembers. If a Crewmember has never been Scanned, the Computer may Scan them by privately rolling a ten-sided die. On a roll of 1 or 2, the Crewmember becomes an Android and is privately informed of this fact.

Set the list of Scanned Crewmembers to: _Fox_, ais523, ayesdeeef, Brendan, Bucky, Josh, Sylphrena, Skju and Sphinx.

As soon as the Ship’s Computer enacts this proposal, or sees that it has been enacted they shall send a private message to each Android player informing them of the usernames of all other Androids.

Add the following subrule “Networking” to the rule “Androids.”

As hidden backup channels within the ship activate, Androids gain the acuity to recognize each other. Each time the Ship’s Computer converts a Crewmember to Android status, it shall send a private message to all other Androids informing them of this player’s username, and send that player a private message informing them of the usernames of all other current Androids.

Brendan has been saying some mighty suspicious things recently. He must be an Android!

Specifically, in the “Let’s Talk About This” proposal, Brendan said “This is definitely going to pass and not get sabotaged, so why not?” The proposal was at 2-2 when it was sabotaged. His confidence made me suspect he has extra information. This may be my paranoia talking, but I think he’s an Android.

Remove “Disabled, Injured.” from the list of Emotions.

After that list, add:-

A Crewmember may also have zero or more Conditions, which are tracked as if they were Emotions. Valid Conditions are Disabled and Injured. If a Crewmember has a particular Emotion or Condition, they may be described with that adjective.

Replace “A Crewmember with the “Injured” Emotion” with “An Injured Crewmember”, replace “A Crewmember with the “Disabled” Emotion” with “A Disabled Crewmember”.

Replace MD1C’s “The Subject has an Emotion other than Disabled removed at random, if they have any.” with:-

An adjective is chosen at random from the Subject’s Emotions and Conditions (excluding “Disabled”), if they have any, and is removed from them.

Replace “the “Disabled” Emotion” with “the “Disabled” Condition”.

Replace the “YYY is an Emotion other than Disabled” with “YYY is an Emotion”.

Replace “gains the Emotion Injured” with “becomes Injured” and “gaining the Emotion Injured” with “becoming Injured”.

Add a new bullet to the list of Emotions:-

• Alert, Tired, Fatigued, Exhausted

In the rule “Emotions”, add two new paragraphs before the paragraph beginning “If a single Emotion”:-

“Increasing” an Emotion means replacing it with the Emotion immediately higher than it within the same Nature; “decreasing” an Emotion means replacing it with the Emotion immediately lower within the same Nature.

If a Crewmember is not Tired, Fatigued or Exhausted they may gain the Alert Emotion. A Crewmember may decrease their own Emotion of Alert, Tired or Fatigued to increase or decrease any of their Emotions that has a different Nature.

Add a rule to the ruleset, called “Who cares, this isn’t going to pass anyway”, with the following text:

This Android can be reached at 8nebetx6w6th at gmail dot com.

My wiki account seems to have gone kaput; no idea what’s happening but the software insists that there’s no user with my name. Could one of the other admins sort me out?

Relatedly, I enacted this proposal, but can’t access the wiki to make the changes. If someone could help me with that then I’d be very grateful.

Yes, I feel a bit silly.

Sensors are recording abnormally high levels of hydrogen in the aft engine tanks. Four crew are required to repair this fault in the Propulsion system, and are reminded to follow all appropriate fire safety protocols.

Add a new rule, “Compromise”:

If three or more Proposals have been Sabotaged in the previous seven days, then any Proposal proposed by the Mediator cannot be Sabotaged. If a Proposal which cannot be Sabotaged passes and the OI is at least 9, then for each Android,  the Ship’s Computer adds to the queue a S33R subroutine with that Android as the subject signed by that Android.

Pilot Brendan is scanned from head to toe by a slow, wide beam of turquoise light and subsonic sound, and feels a little better for it.

Well now….. Seems like I forgot about blognomic for a bit longer then I wanted to. But I am finally returning from the shadows.

I request that I am unidled please. And yes i know I’m an admin but i don’t want to break anything do to admin duty rust.

If the Proposal titled “The Quantity Theory of Insanity” has passed, reword the text it added to the Ruleset as follows; otherwise, in the rule “Emotions”, add new text before the paragraph beginning “If a single Emotion” as follows:

“Increasing” an Emotion means replacing it with the Emotion immediately higher than it within the same Nature; “decreasing” an Emotion means replacing it with the Emotion immediately lower than it within the same Nature.

An Android may, as a Daily Action, remove all Emotions from themself other than “Disabled” or “Injured.”

Add the following paragraph to the rule “Drugs”:

A Crewmember may, as a Weekly Action, Drug themself. To do so, they send a private message to the Ship’s Computer containing exactly one phrase of the form “Drugging myself to feel YYY” where YYY is an Emotion other than Disabled or Injured, and would be an increase or decrease to an Emotion that Crewmember already has. The Ship’s Computer shall, within 24 hours of reading the message, make a blog post announcing that the Target has been Drugged, at which point the Target gains the named Emotion and loses all other Emotions with the same Nature.

In the Rule “Androids” change the text

An Android may Sabotage a Proposal

to

As a Weekly Action an Android may Sabotage a Proposal

In the rule “Emotions”, add a new paragraph before the paragraph beginning “If a single Emotion”:-

“Increasing” an Emotion means replacing it with the Emotion immediately higher than it within the same Nature; “decreasing” an Emotion means replacing it with the Emotion immediately lower than it within the same Nature. A Crewmember may at any time select two of their own Emotions (excluding “Disabled” and “Injured”) and increase one while decreasing the other: both Emotions must change for the action to occur. An Android may at any time add or remove any Emotion from themselves (excluding “Disabled” and “Injured”) so long as this would leave them with no more than one Emotion per Nature.

If Sylphrena is an Android and Sylphrena votes Against this Proposal, the Ship’s Computer shall send a Private Message to Sylphrena informing them of the usernames of all other Androids.

Remove “, this is known as a Crewmember’s Type.” from the rule “Androids”.

In the rule “System Failure”, replace “Unattended Missions increase the Severity of Systems by two levels instead of one” with “Unattended Missions have their Severity incremented one additional time when processed”.

Remove “and the Computer’s EVC contains the phrase ” request denied,”” from the rule “The Ship’s Computer”.

In the rule “Missions”, replace “through a blog entry that specifies the Mission’s System” with “by posting a Votable Matter that specifies the Mission’s System”. Make all current Mission blog entries into Votable Matters.

Remove the text “No Crewmember may have a Command Role before the 26th of January 2015.” and “No Crewmember may post a Trial before the 27th of January 2015.” from the ruleset.

As soon as the Ship’s Computer enacts this proposal, or sees that it has been enacted they shall send a private message to each Android player informing them of the usernames of all other Androids.

Add the following subrule “Networking” to the rule “Androids.”

As hidden backup channels within the ship activate, Androids gain the acuity to recognize each other. Each time the Ship’s Computer converts a Crewmember to Android status, it shall send a private message to all other Androids informing them of this player’s username.

Blank tickertape spools across a console as a L0GS subroutine is executed.

In the rule “Trials”, change the text

No Crewmember may post a Trial unless the Atmosphere is Paranoid.

to

No Crewmember may post a Trial unless the Atmosphere is Angry or Paranoid.

In the rule “Missions”, change the text:

If the Mission is Attended and the previous condition was not met, then the Mission succeeds, and nothing happens

to:

If the Mission is Attended and the previous condition was not met, then the Mission succeeds, and the Severity of its System is decremented once.

and add:

When a System’s Severity is decremented, the Severity changes to the previous one on this list, if it exists.

after:

When a System’s Severity is incremented, the Severity changes to the next one down on this list, if it exists.

Would it be too much trouble to add Alerts to the sidebar? I could try, but I figure someone else would know better.

If the subrule “Sabotage” exists, add a subrule, “Paranoia,” to the rule called “Emotions,” as follows:

When a Proposal is Sabotaged, the Crewmember who proposed it gains the Emotion Paranoid, if they did not have that Emotion already.

In the rule “Missions”, change the text

Each Mission’s System is chosen at random, and its Team Size is a random integer between the number of Androids and Quorum, exclusive.

to

Each Mission’s System is chosen at random, and its Team Size is a random integer between the number of Androids and one plus half the number of non-Disabled Crewmembers, exclusive.

and the text

including votes from every member of the Responder Team

to

including votes from every non-Idle member of the Responder Team

As a subrule to “Missions”, add a rule “System Failure”:-

If the Energy System is Catastrophic, Subroutines may not be processed.

If the Life Support System is Catastrophic, Strenuous actions cannot be taken by Humans.

If the Propulsion System is Catastrophic, Unattended Missions increase the Severity of Systems by two levels instead of one.

If the Scanning System is Catastrophic, the determination of a new Mission’s System is made privately by the Computer, and is not revealed until the time at which the Mission is processed.

With a strobing orange light and a default low-priority alert noise, the Ship’s Computer draws your attention to the fact that carbon dioxide scrubber #3 is offline. Four crew are required to change the filters.

Databanks glitter and bleep as a L0GS subroutine is executed.

Remove the following text from the rule “Missions”:

Each System whose Severity is not “None” has a 50% chance of having its Severity incremented.

Add a new item to the list of subroutines inthe rule entitled “Subroutines”:

ASPX - Threshhold: 10. If the subject of this Subroutine has been the subject of this Subroutine a number of times equal to the current number of human Crewmembers who do not have the Injured emotion, with with each iteration of this subroutine Signed by a different Crewmember and with all iterations of this subroutine submitted to the Chip’s Computer within a single 48 hour period, then they gain the emotion Injured. Submitting this subroutine to the Ship’s Computer is a Strenuous act.

If any Crewmember holds the Command Role of Pilot or Doctor, set their Command Role to blank.

If the Mission titled “Alert: Training Drill” has been processed and has succeeded when this Proposal is enacted, use the GNDT command 1DICE4 to select one member of the Responder Team, with a result of 1 selecting the member of the Responder Team whose username is alphabetically first, a result of 2 selecting the member whose username is alphabetically second, and so on. Assign that Crewmember the Command Role of Pilot.

If the Mission titled “Alert: Training Drill” has not succeeded when this Proposal is enacted, assign the Command Role of Pilot to Brendan.

Of the Crewmembers whose EVC on this Proposal is FOR when it is enacted, select one at random, using the GNDT DICE command to choose one alphabetically as above. Assign that Crewmember the Command Role of Doctor.

Repeal the rule “Assimilation”. Rename the rule “Drugged” to “Drugs” and add the following paragraph to it:-

As a weekly action, the Doctor may Inject any Crewmember by sending a private message to the Ship’s Computer with the text “Inject XXX with YYY” where XXX is the Crewmember to be Injected and YYY is either Saline or Mercury. The Computer should process such a request as soon as it can, and as follows: if an Android is injected with Saline or a Human is injected with Mercury, that Crewmember gains the Emotion Injured; if an Android is injected with Mercury or a Human is injected with Saline, that Crewmember has a 50% chance of gaining the Emotion Injured. Injection is a Strenuous action.

Lights blink across the control consoles. Data banks whirr. Somebody’s earpiece whispers a report. The subroutine S33R has been processed.

I’d appreciate to be unidled, since this dynasty looks interesting and I finally will have some time on my hands soon.

Remove the following text from the rule “Missions”:

Each System whose Severity is not “None” has a 50% chance of having its Severity incremented.

If a majority of EVCs contain the word “weak”, replace it with the following:

A random other System has a 50% chance of having its Severity incremented if its Severity is not “None”.

In the rule Subroutines, change “an Emotion removed at random,” to “an Emotion other than Disabled removed at random,”

In the rule “Missions” amend the text

* If the Mission is Attended, and if an Android is among its Responder Team and has prepared to Sabotage the Mission, the Mission fails as if it were Unattended.

to read

* If the Mission is Attended, and if an Android is among its Responder Team and has prepared to Sabotage the Mission, the Severity of its System is incremented twice.

Remove the sentence “No Crewmember may have a Command Role before the 26th of January 2015.” from the rule “Command Roles.”

Assign the Command Role of Pilot to the Crewmember with the earliest timestamped EVC of FOR on this Proposal when it passes.

Assign the Command Role of Mediator to the Crewmember with the earliest timestamped EVC of AGAINST on this Proposal when it passes.

Assign the Command Role of Doctor to Brendan.

Remove the sentence “No Crewmember may have a Command Role before the 26th of January 2015.” from the rule “Command Roles.”

Assign the Command Role of Pilot to the Crewmember with the earliest timestamped EVC of FOR when this Proposal passes.

Assign the Command Role of Mediator to the Crewmember with the earliest timestamped EVC of AGAINST when this Proposal passes.

Assign the Command Role of Doctor to Brendan.

Four crew are required to run a level one diagnostic on the Scanning system, to verify that the Haniver is currently receiving no inbound signals from Earth or related stations.

In the rule “Drugged”, replace “An Android who has not done so may attempt to Drug another Crewmember as a weekly action.” with “An Android may attempt to Drug any Crewmember as a weekly action.” and “If the Target is an Android, drugging them has no effect.” with “If the Target is an Android and is not the Drugger, drugging them has no effect.”

I’m curious as to whether posting with my phone has to do with whether my posts have comment boxes.

EDIT: All the posts I have done without comment boxes, including this one, have come from my phone. Since the posts that I have made from my computer all had comment boxes, there seems to be a definite correlation.

In the rule “Androids” after the phrase “Each Crewmember may either be a Human or an Android” add the phrase

This is known as a Crewmember’s Type.

Create a new rule, “Assimilation”:-

As a weekly action, the doctor may Assimilate any Crewmember by sending a private message to the Ship’s Computer with the text “Assimilate XXX to become YYY” where XXX is the Crewmember to be Assimilated, known as the Subject, and YYY is a Type, known as the New Type. If the Subject is of the New Type, the Assimilation Fails. If the Subject is not of the New Type, there is a 50% chance the Assimilation Fails; otherwise, it Succeeds.

If the Assimilation Succeeds, the Ship’s Computer converts the Subject to the New Type and informs the Subject of this in a private message. If the Assimilation Fails, the Computer gives the Subject the Emotion Injured and posts in a GNDT comment that the Subject’s Assimilation has Failed.

Assimilation is a Strenuous action.

I’m too busy to play right now, but might play later on in the dynasty. It looks like the way the rules are going at the moment, getting in now is necessary to not upset things if I unidle later. So could an admin unidle me now please? I’ll likely idle out in a bit, but at least it’ll keep people guessing if I unidle again later on.

Add a new rule to the ruleset, entitled Protagonism:

Each Crewmember has a score, which is tracked in the GNDT, called Protagonisticity.

Every time a Crewmember carried out any action permitted under the Core or Dynastic rules, they may increase their Protagonisticity by 1.

If ever a class or category of Crewmembers is defined by the ruleset as being Ascendant, the Crewmember belonging to that class or category with the highest Protagonisticity has achieved Victory.

Add two new subroutines to the list in the rule “Subroutines”:

L0GS - Threshold: 9 OI.  If one of the four most recently processed subroutines was another L0GS, nothing happens.  Otherwise, the Subject is privately sent the names of the Crewmembers who Signed the five most recently processed subroutines, but not information about who signed which Subroutine.

SP0F - Threshold: 14 OI.  For the next seven subroutines, XP0S treats the Subject as Human regardless of whether they are Human or Android.

Add a new dynamic rule to the ruleset.  Call it “Drugged” and give it the following text:

An Android who has not done so may attempt to Drug another Crewmember as a weekly action.  To do so, they send a private message to the Ship Computer containing exactly one phrase of the form “Drugging XXX to feel YYY” where XXX is a Crewmember (the Target) and YYY is an Emotion other than Disabled. If the Target is an Android, drugging them has no effect.  Otherwise, the Ship Computer shall, within 24 hours of reading the message, make a blog post announcing that the Target has been Drugged, at which point the Target gains the named Emotion and loses all other Emotions with the same Nature.

Add a new subrule to “Androids” called “Demands”:-

Androids may submit Demands to the Ship’s Computer: Demands are drafts of Proposals. When the Computer receives a Demand, it should post it as a Proposal, marked with “[Demand]” in the title. Proposals posted in this way are known as Demand Proposals, do not count towards the Computer’s Proposal limit, and can be made even if the Computer has 2 Proposals pending or has made 3 that day. A Demand Proposal may not be made if another Demand Proposal is Pending.

In the rule “Missions”, replace “A new Mission may not share its System with any other Pending Mission. The Team Size must be an integer between Quorum and the number of Androids, exclusive.” with:-

Each Mission’s System is chosen at random, and its Team Size is a random integer between the number of Androids and Quorum, exclusive.

Replace the second paragraph with:-

The Responder Team for a Mission is a group of Crewmembers equal to the Team Size. When a Mission begins, the Computer should select a number of random Crewmembers equal to the Team Size (those who happen to be nearest to the problem), and announce it in a comment to the post: this is the Responder Team for the Mission. In comments to the post, Crewmembers may vote FOR or AGAINST the Responder Team. If the post has a Quorum of FOR votes, including votes from every member of the Responder Team, the Responder Team is approved: the Computer may process the Mission as Attended. If a Mission is more than 72 hours old and cannot be processed as Attended, the Computer may process it as Unattended.

At any time, the Pilot may post a comment (known as a “Roster Comment”) to the post listing a number of Crewmembers equal to the Team Size: if he or she does so, this group becomes the Responder Team for the Mission and all votes on that post made previously to that Roster Comment are ignored for the purposes of this rule.

To the “Sabotage” rule, add:-

An Android may prepare to Sabotage a specific Mission by sending a Private Message to the Ship’s Computer informing it of this intention.

Remove the paragraphs beginning “A Mission is Completed…” and “A Mission Fails…” and in the place they occupied add:-

When a Mission is processed, the following steps are taken in order:

• Each System whose Severity is not “None” has a 50% chance of having its Severity incremented.
• If the Mission is Attended, and if an Android is among its Responder Team and has prepared to Sabotage the Mission, the Mission fails as if it were Unattended.
• If the Mission is Attended and the previous condition was not met, then the Mission succeeds, and nothing happens.
• If the Mission is Unattended, the Severity of its System is incremented once.

The Mission is then over, and no further actions can be taken on it.

If the ruleset contains the text:

A Mission is Completed if all of its Team chooses Repair.

A Mission Fails if it is not Completed 72 hours after the time of the Alert’s posting, or if no less than two Team members have not chosen Repair. When a Mission Fails, and every 72 hours after that, the Severity of its System is incremented once.

Change it to:

A Mission is Completed if all of its Team chooses Repair. When a Mission is Completed, the Severity is decremented once..

A Mission Fails if it is not Completed 72 hours after the time of the Alert’s posting, or if at least 50% of the Team rounded down, and at least 1 Team member, has not chosen Repair. When a Mission Fails, and every 72 hours after that, the Severity of its System is incremented once.

Enact a new rule entitled “Missions”:

The ISV Jenny Haniver, under the Polaris protocol, requires Crewmember participation in the maintenance and operation of essential ship systems. The Computer may, not more than once every 48 hours, Alert the crew to a new Pending Mission through a blog entry that specifies the Mission’s System and Team Size and that has a unique title beginning with “Alert:”. A new Mission may not share its System with any other Pending Mission. The Team Size must be an integer between Quorum and the number of Androids, exclusive.

In a comment to the Alert post, the Pilot should suggest a Team of active Crewmembers of the specified size. All Crewmembers may then vote FOR or AGAINST the proposed Team through comments on the post. If a Quorum of FOR votes is reached, then the Team is approved and each of its members should send a private message to the Computer that indicates the Mission and one of the words “Repair” or “Sabotage”. Only the first such private message from each Team member is counted for the Mission.

A Mission is Completed if all of its Team chooses Repair.

A Mission Fails if it is not Completed 72 hours after the time of the Alert’s posting, or if no less than two Team members have not chosen Repair. When a Mission Fails, and every 72 hours after that, the Severity of its System is incremented once.

Each System has an associated Severity, tracked in this rule. Mission Systems and their current Severities are:
* Energy (None)
* Life Support (None)
* Propulsion (Moderate)
* Scanning (None)

Valid Severities are:
* None
* Minor
* Moderate
* Critical
* Catastrophic
When a System’s Severity is incremented, the Severity changes to the next one down on this list, if it exists.

I just went to enact “Request Denied” but couldn’t log into the wiki. (I tried capitalization.)
Could someone correct me or set up an account?

If the ruleset contains the text

The Subject is privately sent a copy of the current queue of Subroutines (including who had signed each Subroutine).

Change it to

The Subject is privately sent a copy of the current queue of Subroutines, not including who Signed each Subroutine.

Remove the text “No Crewmember may have a Command Role before the 26th of January 2015.” and “No Humans may be converted to Androids before the 26th of January 2015. The Ship’s Computer may repeal this paragraph on or after that date.” from the ruleset.

In the rule “Subroutines”, replace the paragraph beginning “If the Computer reads” with:-

If the Computer receives a Private Message containing only the text “EXECUTE SUBROUTINE XXXX YYYY” (where XXXX is the Designation of a Subroutine and YYYY is the name of a Crewmember), and if the Threshold of that Subroutine is less than or equal to the OI, and if the queue contains no Subroutines signed by the Crewmember who sent the message, then the Computer may add a Subroutine of that Designation to the end of its queue with the named Crewmember as its Subject, and signed by the Crewmember who sent the message.

After the first sentence of the second paragraph of that rule, add:

Each Subroutine in the queue is marked as being Signed by a particular Crewmember or idle Crewmember.

Reword the effect of B3LY to:

All Subroutines signed by the Subject are discarded from the queue.

Reword the effect of S33R to:

The Subject is privately sent a copy of the current queue of Subroutines (including who had signed each Subroutine).

Replace “naming the Subroutine but not its Subject” with “naming the Subroutine but not its Subject or the Crewmember who signed it”.

The Computer shall remove all subroutines from the queue when this proposal enacts.

In the rule “The Ship’s Computer” after the phrase “If an enacted Votable Matter would require the Ship’s Computer to reveal or change information that it is tracking privately,” add

and the Computer’s EVC contains the phrase ” request denied,”

If the rule titled “Emotions” and its subrule “Injuries” exist, add a new rule, “Trials”:

A Trial is a Votable Matter, and consists of a blog post with a title beginning with “Trial:” and the comments on that post. No Crewmember may post a Trial before the 27th of January 2015. No Crewmember may post a Trial if they have posted a Trial in the last 48 hours. No Crewmember may post a Trial unless the Atmosphere is Paranoid.

The Crewmember posting a Trial must accuse a single Crewmember of being an Android in the body of the post. A post that accuses no Crewmembers, or names multiple Crewmembers, is not a valid Trial.

The oldest pending Trial may be enacted if the following is true:

• It has been open for voting for at least 12 hours and has a number of FOR Votes that exceeds Quorum.

The oldest pending Trial may be failed if any of the following are true:

• It has been open for voting for at least 12 hours, and the number of Crewmembers who are voting AGAINST it exceeds or equals Quorum.
• It has been open for voting for at least 24 hours and cannot be Enacted.

If a Trial is enacted, the enacting Admin must give the Crewmember accused within it the “Disabled” Emotion.

Enact a new rule entitled “Systems”:

The ISV Jenny Haniver runs on numerous Systems, each of which has an integer Power Level between 0 and 10 kilovolts (kV), inclusive, and tracked in this rule. The Systems, their current Power Levels, and their effects are as follows:

* Energy (7 kV): The sum of all System’s Power Levels cannot exceed four times the Power Level of Energy. If Energy’s Power Level drops and violates that condition, Power Levels are subtracted one at a time, from the bottom to the top of this list of Systems, until the condition is met again.
* Life Support (8 kV): If Life Support drops below 6kV, all Crewmembers become Injured. If Life Support drops below 4kV, all Crewmembers cease to be Injured and become Disabled.
* Sensors (7 kV): If Sensors drop below 6kV, the Ship’s Computer cannot process any Subroutines. If Sensors drop below 4kV, the Computer cannot vote on any Proposals.
* Propulsion (3 kV)
* Communication (1 kV)

Add the following to the end of the last paragraph of the rule entitled “The Ship’s Computer”:

Any ruleset text affected by this clause must be rendered in italics.

When did the ruleset stop being numbered? Because the glossary defines rules as “Each individually numbered section of the ruleset”, potentially rendering the entire ruleset invalid.

Enact a new rule, “Subroutines”:-

The Ship’s Computer operates more effectively when the parameters of its operation are defined. The total number of Dynastic Rules (excluding Subrules) is referred to as the Ship Computer’s Organisation Index (or OI).

The Computer privately tracks a queue of Subroutines and corresponding Subjects, which may be empty. Possible Subroutines are listed below with the following Designations, Thresholds and effects.

• MD1C - Threshold: 6 OI. The Subject has an Emotion removed at random, if they have any.
• S33R - Threshold: 9 OI. The Subject is privately sent a copy of the current queue of Subroutines.
• B3LY - Threshold: 12 OI. All Subroutines with the Subject as their Subject are discarded from the queue.
• XP0S - Threshold: 15 OI. The Ship’s Computer picks a random Crewmember, and tells the Subject whether that Crewmember is Human or Android.

If the Computer reads the phrase “EXECUTE SUBROUTINE XXXX YYYY” in any written medium (where XXXX is the Designation of a Subroutine and YYYY is the name of a Crewmember), and it has not read that phrase in that exact place before, and if the Threshold of that Subroutine is less than or equal to the OI, and if the queue contains no Subroutines with that Crewmember as its Subject, then the Computer may add a Subroutine of that Designation to the end of its queue with the named Crewmember as its Subject.

As a daily action, the Computer may process the Subroutine at the start of its queue: it posts a blog entry naming the Subroutine but not its Subject, and then removes that Subroutine from the queue.

Add a new rule to the ruleset, entitled The Triumph of Reason:

The Ship’s Computer operates more effectively when the parameters of its operation are defined.

The total number of Dynastic Rules and sub-rules to Dynastic Rules can be referred to as the Ship Computer’s Organisation Index (or OI).The Ship’s Computer has a variety of subroutines that can be used when its OI exceeds certain thresholds. Any crew member may request that the Ship’s Computer may run a subroutine at any time. However, all subroutines are weekly actions for the Ship’s Computer. The Ship’s Computer should honour subroutine requests at their first opportunity, if they are able and if the OI threshold has been met, and should prioritise subroutine requests on the basis that more recent requests are honoured first.

These subroutines, their respective thresholds, and their effects are as follows:

• MD1C - Threshold: 8 OI. Upon confirmation from the Ships’s Computer that this subroutine has been successfully activated, the requester may change one of their Emotions to an Emotion adjacent in its Nature.
• S33R - Threshold: 12 OI. The Ship’s Computer must send the requester the most recent piece of communication they have received from an Android.
• DFND - Threshold: 15 OI. The Ship’s Computer must disregard any communications or orders received from Androids in the 24 hours following the commencement of this subroutine. The Ship’s Computer should notify the requester when this subroutine commences.
• XP0S - Threshold: 21 OI. The Ship’s Computer must pick a random Crewmember, and tell the requester whether that Crewmember is Human or Android.

Create a new field in the GNDT called Command Role. Set it to an empty string for all players.

Add a new rule, “Command Roles”:

Some Crewmembers have a Command Role, tracked in the GNDT as a text string and defaulting to blank. No more than one Crewmember at a time may be assigned a given Command Role. A Crewmember who has a Command Role may have special Daily Actions that only they can take, or other persistent effects related to their status in the game.

The valid Command Roles are Pilot, Doctor, and Mediator.

No Crewmember may have a Command Role before the 26th of January 2015. If there is a Command Role with no Crewmember assigned to it, and there are at least two active Crewmembers with no Command Role, the Ship’s Computer may pick a random Crewmember using the GNDT DICE function (where each Command Role-free Crewmember is assigned a number in a GNDT comment before DICE is called) and assign that Command Role to the Crewmember so selected.

Please activate me, thank you.

Hi. Could someone unidle me, please?

If there is a rule “Emotions”, add a new Nature with the emotions “Disabled” and “Injured” to the list of Emotions.

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

A Crewmember with the “Injured” Emotion may not take any action under a dynastic rule that a rule declares Strenuous.
A Crewmember with the “Disabled” Emotion may not take any action under a dynastic rule, except for actions that a rule declares to be Cerebral.

If an action would otherwise be declared both Cerebral and Strenuous, it is Strenuous but not Cerebral.

Unidle me

Add a new rule, “Emotions”:-

Each Crewmember has zero or more Emotions, tracked in the GNDT as a text string and defaulting to blank. Valid Emotions are listed below, grouped by their Nature, with each group listed progressively from High to Low.

• Angry, Stressed, Calm, Listless.
• Reckless, Careless, Cautious, Paranoid.
• Euphoric, Happy, Unhappy, Depressed.

A Crewmember may at any time give themselves any Emotion, so long as they do not already have an Emotion of that Nature, and that the new Emotion is neither the Highest nor the Lowest of that Nature. If a Crewmember has two Emotions of the same Nature, any Crewmember may remove the Highest of those two Emotions from that Crewmember.

If a single Emotion appears in more Crewmembers than any other Emotion, that Emotion is known as the Atmosphere; otherwise there is no Atmosphere.

In the rule “Androids”, replace “If there are fewer than two Androids” with:-

If there are more than five Crewmembers and fewer than two Androids

Neither Ayesdeeef nor Doctor29 have posted or commented in a couple of weeks. Per Rule 1.2.1, they are now idle. Quorum drops to 3.

Enact a new rule, “The Ship’s Computer”:-

The ISV Jenny Haniver is operated by the Ship’s Computer. It may be referred to as simply “the Computer”. For the purposes of all dynastic rules, the Ship’s Computer is not considered to be a Crewmember.

If an enacted Votable Matter would require the Ship’s Computer to reveal or change information that it is tracking privately, and if the Computer did not vote FOR that Votable Matter, then it may choose not to reveal or change that information.

Enact a new rule, “Androids”:-

Each Crewmember may either be a Human or an Android (defaulting to Human) and this is tracked privately by the Ship’s Computer. If there are fewer than two Androids, the Computer may convert a randomly-selected Human to an Android and privately inform that Crewmember that their sense of humanity had been simulated up to this point.

No Humans may be converted to Androids before the 26th of January 2015. The Ship’s Computer may repeal this paragraph on or after that date.

Add a subrule to “Androids” called “Sabotage”:-

An Android may Sabotage a Proposal by sending a Private Message to the Ship’s Computer informing it of this intention. A proposal can only become Sabotaged if it is pending, or if it enacted less than 24 hours previously. If a pending Proposal is Sabotaged, the Computer should veto it, stating that it has been Sabotaged. If an enacted Proposal is Sabotaged, the Computer should undo the effects of its enactment as it sees fit, and post a blog entry announcing this.

Somewhere between Jupiter’s moons, the ISV Jenny Haniver picks its autopiloted way through derelict shuttles and abandoned cargo debris, and slowly drifts clear of the giant planet’s shadow. Solar panels glint in the weak sunlight, awakening on the very edge of their operable range, and a crop of parabolic antennae whirr and track the dark sky, sifting for a signal from Earth.

A single greenscreen display chatters to itself on the unmanned flight console: no signal, retrying, no signal, retrying. After exactly an hour, it falls blank. One hour five seconds, and fluorescent striplights clunk into life, spreading from the bridge and down the corridors, flooding light through the ship. One hour ten, and machinery whirrs in the cryo-suspension bay as thick grey vapour begins to swirl and drain from the higher-ranking glass tubes.

“Good morning.” says a calm voice from hidden microphones. “Ship’s systems have been unable to contact Earth station or detect any outbound radio signals for one full hour. Under the Polaris protocol, the core flight crew have been reactivated. Please proceed to the command deck.”

(“Shuttle” becomes “Crewmember”, “Traffic Warden” becomes “Ship’s Computer”.)

I currently have 4 Flags orbiting Io in my name, 9 around Europa and 16 bleeping their way around Ganymede. Per the rule “Space Domination”, “If at least 29 Orbits have Flags whose owner is the same Shuttle, that Shuttle achieves victory.” Jupiter is mine.

Enact a new rule, “Final Orbit”:-

The Shuttle named Kevan has achieved victory.

I’ve deleted four samey spam entries this morning, I don’t know if we’ve had others. It looks like the default CAPTCHA isn’t keeping casual spammers out.

Rather than disabling signups again, I’ve switched to “Manual activation by an administrator” to see how that works. So far as I can see it adds the account to this admin list for processing, but doesn’t actually send an alert to anyone. (Or did it get sent to 75th Trombone, the server owner?)

It’ll do for now, as I and other admins can check the list periodically. But maybe it’s worth actually using manual activation as a longer-term solution. We could always ask new players to fill in a little human-proving “why do you want to play BlogNomic” survey which gets emailed to a bunch of admin addresses to alert them to the fact that there’s a new account in the queue. It could maybe be a Google Form, or a simple PHP script.

Create a new rule, “Aggregate Value”:

A Shuttle’s Aggregate Value (measured in $) is the sum of the Substances in their bay multiplied by each Substance’s Market Value on the Moon the Shuttle is in Orbit around. A Shuttle with an Aggregate Value of more than $70 achieves victory. If a Hivemind contains Shuttles with net Aggregate Value greater than $100, that Hivemind is awarded victory.

In “Numbers and Variables” in the Appendix, replace “If a game variable has no defined starting value for new Shuttles, or for existing Shuttles upon the variable’s creation, then that starting value is zero (for numerical variables) or blank (for a text string or list).” with:-

If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).

Neither Sprucial nor Teninten have made a post or comment so far this year, and both idle out. Quorum drops to 3.

In the rule “Substances”, replace “these are tracked privately by the Traffic Warden” with:-

these are tracked privately by the Traffic Warden (if a Minimum or Maximum Worth is undefined, the Traffic Warden may assign it any legal value)

In the rule “Hiveminds”, change the text

a daily action, if the new Hivemind’s Charter allows it.

to

a daily action, if the new Hivemind’s Charter allows it to join.

To “Local Maneuvering”, add a penultimate paragraph:-

A Shuttle may spend 1 Fuel and 1 Hydrogen from their Bay to Boost. This is the same as Maneuvering, except that instead of rolling dice, all of those dice are considered to have rolled their maximum values.

Add a Hydrogen column to the Market Value table in “Substances”, with values of “5” in each of its cells.

In the rule “Containers”, replace “3 Fuel, 3 Sulfur, 3 Ice or 10 Iron” with “3 Fuel, 3 Sulfur, 3 Ice, 3 Hydrogen or 10 Iron”.

In the rule “Fuel”, replace “each Shuttle with less than 15 Fuel gains 3 Fuel. The Traffic Warden gains the 3 Fuel even if it has 15 or more Fuel.” with:-

each Shuttle with less than 15 Fuel gains 7 Fuel. The Traffic Warden gains the 7 Fuel even if it has 15 or more Fuel.

If the proposal “A Day in Space” has been enacted, append the text “A Shuttle cannot both Maneuver and use a Magnetic Booster on the same day or in the same 10-hour period.” to the rule “Magnetic Boosters”.

In the rule “Hiveminds”, change the text

they have not left a Hivemind in the past 24 hours.

to

they have not left a Hivemind in the past 24 hours.  Also, Derelicts may leave their Hivemind and join a different one as a daily action, if the new Hivemind’s Charter allows it.

In the rule “Hiveminds,” after the bullet point “If the Hivemind is Awarded Victory, how to decide which of its members achieve victory,” add

• Any special rules for that Hivemind (if applicable).

Create a new Hivemind, “Shortwave Communicators,” with charter:

• Any Shuttle may join Shortwave Communicators at any time.
• A Shuttle in Shortwave Communicators may cause another Shuttle in that Hivemind to act if the first Shuttle and the second Shuttle share an Orbit Number.
• If Shortwave Communicators is awarded victory, all of its members achieve victory.
• Derelicts do not count in determining how many members are in Shortwave Communicators.
• A Derelict may leave Shortwave Communicators and join another Hivemind immediately as one GNDT action.

Put every derelict in the Hivemind Shortwave Communicators.

In the rule “Local Maneuvering”, replace “that they have not used to change Orbits in the last 20 hours” with:-

that they have not used to change Orbits earlier that day, or in the last 10 hours

And replace “A Shuttle may spend 2 Fuel to Hover, if it has not done so in the previous 20 hours.” with:-

As a daily action, a Shuttle may spend 2 Fuel to Hover.

In “Magnetic Boosters”, remove “They may not Maneuver for the next 24 hours after doing so.” and replace “may spend Fuel equal to” with:-

may, as a daily action, spend Fuel equal to

Add a new subrule to the rule “Local Maneuvering”.  Call it “Io Ordinance” and give it the following text:

Shuttles may not Hover in any Io orbit unless all their Thrusters are Overcharged.