Tuesday, February 03, 2015

Proposal: Trust Modifier

Sabotaged. -RaichuKFM

Adminned at 04 Feb 2015 02:17:49 UTC

In the rule “Trust”, add a subrule “Trust Modifier”:

The Ship’s Computer will privately track a Trust Modifier for each Android. The Trust Modifier is an integer and can be negative. If the Trust Modifier has not been set for a specific Android, it defaults to zero. Each time an Android Sabotages a proposal, their Trust Modifier is lowered by one. Each time a Demand Proposal is enacted, the Android who submitted the Demand Proposal will have their Trust Modifier increased by one.

When determining the Android with the highest Trust, the Android with the highest total of Trust and Trust Modifier shall be considered to have the highest Trust.

Between 24 hours and 72 hours after the enactment of this rule the ship’s computer shall send a private message to each Android player informing them of the usernames of all other Androids and change:

Each Crewmember may either be a Human or an Android, defaulting to Human. This is tracked privately by the Ship’s Computer. If there are more than five Crewmembers and 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.

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. After the Computer Scans a Crewmember, it shall make a blog post saying it has done so.

to:

Each Crewmember may either be a Human or an Android, defaulting to Human. This is tracked privately by the Ship’s Computer. If there are more than five Crewmembers and 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 and inform them of the usernames of all other Androids. The computer shall then send a private message to each Android player informing them of the username of the new Android.

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 and informed of the usernames of all other Androids. The computer shall then send a private message to each Android player informing them of the username of the new Android. After the Computer Scans a Crewmember, it shall make a blog post saying it has done so.

 

Do you trust me?

Comments

Darknight: he/him

03-02-2015 04:04:32 UTC

imperial

Josh: he/they

03-02-2015 08:18:27 UTC

imperial

Kevan: City he/him

03-02-2015 09:24:39 UTC

veto Sabotaged.

Note that the “Between 24 hours and 72 hours after the enactment of this rule” clause wouldn’t have triggered anyway, per the final bullet of the Rules and Proposals glossary: proposals cannot have delayed effects.

Bucky:

03-02-2015 17:09:48 UTC

Yet we still allow ‘as soon as is practical after this is enacted’ clauses.

Kevan: City he/him

03-02-2015 17:19:16 UTC

Do we?

Kevan: City he/him

03-02-2015 17:28:57 UTC

Oh, I suppose we had “As soon as the Ship’s Computer enacts this proposal, or sees that it has been enacted” in a (failed) proposal recently. Although that’s asking a player to do something that they could have done anyway, rather than making a gamestate change which would otherwise be illegal.