I heard that Purplebeard recently stole JoshCorp’s trade secrets, driving it out of business in the process. Our Warden, Kevan, helped him to sell the information on the black market, or something.

I ask to become Idle

Tantusar was found with this crude escape map inked on the flyleaf of a fantasy novel from the prison library, and I resent the implication that this evidence has been planted.

Replace the final paragraph of “Grudges” with:-

When a Prisoner (the “Chump”) has their Sentence increased as a direct result of a Confession being resolved, then if the other Party of that Confession has a Grudge against the Chump, the Chump has their Sentence increased by a further year.

Quorum is unchanged.

If Proposal: Grudges 2 is enacted, restore the field ‘Grudges’ to the values it had at the moment of enactment of the proposal ‘SHIV Index’

Kevan, you forgot to add SHIV to GNTD when enacting SHIV index proposals

Add a new Rule to the Ruleset, called Grudges, with the following text:

Each Prisoner can have up to one Grudge, which is tracked in the GNDT. A Prisoner’s Grudge must be the name of one other Prisoner.

As a weekly action and so long as they are not Suspect in a Confession, a Prisoner may Change their Grudge. This stands for changing or clearing their Grudge.

Whenever a Prisoner’s is the Accomplice in a Confession in which their Grudge is a Suspect, and - as a result of that Confession - their Grudge’s Sentence increases, that Prisoner may Roll On their Grudge within 24 hours of the resolution of that Confession. A Prisoner Rolls On another Prisoner by increasing their Sentence by 1.

Add a new Rule to the Ruleset, called Grudge, with the following text:

Each Prisoner can have up to one Grudge, which is tracked in the GNDT. A Prisoner’s Grudge must be the name of one other Prisoner.

As a daily action and so long as they are not Party to a Confession, a Prisoner may Change their Grudge. This stands for changing or clearing their Grudge.

Whenever a Prisoner’s is the Accomplice in a Confession in which their Grudge is a Suspect, and - as a result of that Confession - their Grudge’s Sentence increases, that Prisoner may Roll On their Grudge within 24 hours of the resolution of that Confession. A Prisoner Rolls On another Prisoner by increasing their Sentence by 1.

In the Appendix, in the section Keywords, add a Keyword “Name of a Prisoner” with the text

Name of a Prisoner is their current Blognomic account name

Add a Keyword “Name of an Idle Prisoner” with the text

Name of an Idle Prisoner is their current Blognomic account name

Add a Keyword “Name of a Gamestate Tracking Entity” with the text

A value of GNTD field is considered to be a Name of a Gamestate Tracking Entity only if this field is explicitly described in the Ruleset as such.

In the Appendix, in the section “Clarifications” in the rule “Names”, reword

Within the ruleset, a word only refers to the name of a Prisoner if it is explicitly stated that it refers to a Prisoner’s name.

as

Within the ruleset, a word only refers to the name of a Prisoner or to the Name of a Gamestate Tracking Entity if it is explicitly stated that it refers to such name.

To the first paragraph of “Confessions”, add:-

Confession blog entries must be posted in the Votable Matters category, but are not considered to be Votable Matters for any other purpose.

Move all blog entries for current Confessions into the Votable Matters category.

The rainwater theft Lynx mentioned? He was there, smuggling the filled bottles across the border with me.

In the rule ‘Confessions’, reword:

A Crime’s Suspect or Accomplice may respond to its Confession with a Statement (if they have not already done so on that Confession), being a blog comment to that Confession which contains a single Hash.

as

A Crime’s Suspect or Accomplice may respond to its Confession with a Statement (if they have not already done so on that Confession), being a blog comment to that Confession which contains a single Hash. The Hashes in the Parties’ Statements shall be different.

I do remember the robbery of Hogwarts’ Broom Closet like it was yesterday: I was taking all Quiddich Supplies while Josh was breaking the wards to get us out.

In “Grudges”, replace “A Prisoner may change or clear their Grudge as a daily action.” with:-

A Prisoner may change or clear their Grudge so long as they are not Party to a Confession at the time of changing it, and have not been Party to a Confession during the previous 24 hours.

A mobile phone was discovered duct-taped to the sink in Winner‘s cell this morning. ShareDVI was seen briefly entering the cell during the inspections, by one of the guards. Explain yourselves.

If a rule entitled Shivving exists, repeal it.

Add a new rule to the ruleset, entitled Shivving:

Each Prisoner has a Standard Heuristic for Inmate Violence (SHIV) score, which is a non-negative integer number with the maximum of 99. It is tracked in the GNDT and defaults to zero. Each Prisoner’s SHIV score represents how unpopular they are within the Prison, and how likely they are to be the subject of violence.

As a daily action, each Prisoner may Walk the Yard by rolling DICE100 in the GNDT. If the result is lower than their SHIV score, they must reduce their Sentence by half (rounded up), set their SHIV score to 10, and set their Attitude to Injured.

Change the rule entitled Attitudes so that it reads as follows:

Each Prisoner has an Attitude, which may be either Withdrawn, Rebellious, Comfortable, Converted or Injured (defaulting to Withdrawn) and is tracked in the GNDT. The Warden’s Attitude can be only Converted or Injured, defaulting to Converted.

As a weekly action, a Prisoner may change their own Attitude, provided that their Attitude is not currently Injured.

Change the first sentence of the rule called Confessions to read as follows:

As a daily action, a Prisoner may confess to a Crime by increasing their SHIV score by 2, and then posting a blog entry to this effect, with “Crime:” in its title and naming a single other Prisoner as the Crime’s Accomplice in its body.

Change the bulleted list in the same rule to read as follows:

* If the Suspect and Accomplice both Cooperated, each has their Sentence increased by 1 year and their SHIV score increased by 3.
* If the Suspect Cooperated and the Accomplice Defected, the Suspect has their Sentence increased by 3 years and the Accomplice has their SHIV score increased by 2.
* If the Suspect Defected and the Accomplice Cooperated, the Accomplice has their Sentence increased by 3 years and the Suspect has their SHIV score increased by 2.
* If the Suspect and Accomplice both Defected, each has their Sentence increased by 2 years.

If in the rule called Rumours there is the following sentence, remove it:

Any Fish named within a Rumour may, within 24 hours of the posting of the Rumour, increase the SHIV of the Prisoner who posted the Rumour by 2.

Add the following to the end of the rule called Rumours:

Any Fish named within a Rumour may, within 24 hours of the posting of the Rumour, increase the SHIV of the Prisoner who posted the Rumour by 2, if they have not already done this for this Rumour.

Repeal the rule called Grudges, if it exists.

Reword the rule called The Don to read as follows:

The Prisoner with the greatest Sentence is known as the Don.

When The Don Confesses to a Crime, they may increase their SHIV by 4 and name another Prisoner to be the Suspect rather than themselves. Whenever the Don ceases to be the Don, they may once increase their SHIV by 10.

Add a new rule to the ruleset, entitled Shivving:

Each Prisoner has a Standard Heuristic for Inmate Violence (SHIV) score, which is tracked in the GNDT and defaults to zero. Each Prisoner’s SHIV shore represents how unpopular they are within the Prison, and how likely they are to be the subject of violence.

As a daily action, each Prisoner may Walk the Yard by rolling DICE100 in the GNDT. If the result is lower than their SHIV score, they must reduce their Sentence by half (rounded up), set their SHIV score to 10, and set their Attitude to Injured.

Change the rule entitled Attitudes so that it reads as follows:

Each Prisoner has an Attitude, which may be either Withdrawn, Rebellious, Comfortable, Converted or Injured (defaulting to Withdrawn) and is tracked in the GNDT. The Warden is always Converted.

As a weekly action, a Prisoner may change their own Attitude, provided that their Attitude is not currently Injured. An Injured Prisoner may never declare Victory.

Change the first sentence of the rule called Confessions to read as follows:

As a daily action, a Prisoner may confess to a Crime by increasing their SHIV score by 2, and then posting a blog entry to this effect, with “Crime:” in its title and naming a single other Prisoner as the Crime’s Accomplice in its body.

Change the bulleted list in the same rule to read as follows:

* If the Suspect and Accomplice both Cooperated, each has their Sentence increased by 1 year and their SHIV score increased by 3.
* If the Suspect Cooperated and the Accomplice Defected, the Suspect has their Sentence increased by 3 years and the Accomplice has their SHIV score increased by 2.
* If the Suspect Defected and the Accomplice Cooperated, the Accomplice has their Sentence increased by 3 years and the Suspect has their SHIV score increased by 2.
* If the Suspect and Accomplice both Defected, each has their Sentence increased by 2 years.

Add the following to the end of the rule called Rumours:

Any Fish named within a Rumour may, within 24 hours of the posting of the Rumour, increase the SHIV of the Prisoner who posted the Rumour by 2.

Repeal the rule called Grudges.

Reword the rule called The Don to read as follows:

The Prisoner with the greatest Sentence is known as the Don.

When The Don Confesses to a Crime, they may increase their SHIV by 4 and name another Prisoner to be the Suspect rather than themselves. Whenever the Don ceases to be the Don, they may once increase their SHIV by 10.

To “Confessions”, add a paragraph:-

If a Confession is more than 120 hours old, both of its Parties are considered to have Cooperated on it.

It also seems that Tantusar is the suspect of having stolen Hong Kong’s rainwater, with the help of his accomplice Aname.

Add a subrule to “Confessions” called “Snitching”:-

A Snitch is a type of Confession. When a Prisoner Confesses to a Crime, they may choose to make that Confession a Snitch, by using a title including “Snitch:” instead of “Crime:”.

After a Snitch Confession ceases to be considered a Confession in a way that increases the Sentence of either Party of that Confession, both of its Parties then lose one year from their Sentence (to a minimum of zero).

Add a new Rule to the Ruleset, entitled Miscellaneous Actions, with the following text:

A Prisoner may, as a daily action, Give Junk. This stands for decreasing their own Junk by 1, then increasing the Junk of any other Prisoner by 1.

A Prisoner with a RI less than 1 may, as a weekly action, Behave Well. This stands for decreasing their own Sentence by 1 year.

A Prisoner with a RI greater than 1 may, as a weekly action, Behave Bad. This stands for increasing their own Sentence by 1 year.

 

Add a new Rule to the Ruleset, entitled Alignment Actions, with the following text:

Each Prisoner has a Junk field in the GNDT.
Each Prisoner has a RI (Rebellion Index) field in the GNDT.

Non-Warden Prisoners are called Inmates.

The Junk field defaults to 0. It must be a natural number.
The RI field defaults to 1. It must be either 0 or a positive decimal number.

A Withdrawn may, as a weekly action, Withdraw. This stands for setting their own RI to 0.9. Doing so he foregoes every further daily actions in the current week.

A Rebel or Rebellious may, as a daily action, Cause Trouble. This stands for increasing the RI of themselves and any other Prisoner by 0.2.

A Colonizer or Comfortable may, as a daily action, Colonize. This stands for increasing the Junk of themselves and any other Prisoner by 1.

A Converted may, as a daily action, Help Guards. This stands for decreasing the RI of themselves and any other Prisoner by 0.3.

 

Add a new Rule to the Ruleset, entitled Alignment Actions, with the following text:

Each Prisoner has a Junk field in the GNDT.
Each Prisoner has a RI (Rebellion Index) field in the GNDT.

Non-Warden Prisoners are called Inmates.

The Junk field defaults to 0. It must be a natural number.
The RI field defaults to 1. It must be either 0 or a positive decimal number.

A Withdrawn may, as a weekly action, Withdraw. This stands for setting their own RI to 0.9. Doing so he foregoes every further daily actions in the current week.

A Rebel or Rebellious may, as a daily action, Cause Trouble. This stands for increasing the RI of themselves and any other Prisoner by 0.2.

A Colonizer or Comfortable may, as a daily action, Colonize. This stands for increasing the Junk of themselves and any other Prisoner by 1.

A Converted may, as a daily action, Help Guards. This stands for decreasing the RI of themselves and any other Prisoner by 0.3.

 

In “Confessions”, reword the paragraph beginning “Either Party of a Confession may Threaten the other” to:-

Either Party of a Confession may Threaten the other (the “Nerk”), if either of the following is true:

• The Threatening Party has either Defected or Cooperated on that Confession more than 24 hours previously, and the Nerk has neither Defected nor Cooperated on that Confession.
• The Threatening Party has made a Statement on that Confession more than 24 hours previously, and the Nerk has not made a Statement on that Confession.

When such a Threat is made, the Threatening Party may announce that the Nerk has either Defected or Cooperated, in a comment to that effect on that Confession; upon doing so, the Nerk is considered to have Defected or Cooperated, accordingly, on that Confession.

Evo hasn’t posted or commented in over a week, and goes idle. Quorum drops to 5.

The Hong Kong job? I have a perfect alibi. My right hand man Tantusar was there, though, as was his known accomplice Aname. Probably just a coincidence.

If a rule called “Total Institution” exists, repeal it.

Enact a new rule, “Attitudes”:-

Each Prisoner has an Attitude, which may be either Withdrawn, Rebellious, Comfortable or Converted (defaulting to Withdrawn) and is tracked in the GNDT. The Warden is always Converted.

As a weekly action, a Prisoner may change their own Attitude.

For every non-Warden Prisoner who had an Alignment before this proposal enacted, set their Attitude to the value which appears in the same position as their previous Alignment in the list of possible values.

Somebody has been sneaking drugs inro the Prison. I think that Lynx is the suspect, because there were no drugs here become, and Kevan is, in fact, his Accomplice, because he’s the Warden, that’s why.

Reword in the rule Confessions

Either Party of a Confession may Threaten the other (the “Nerk”), if the Confession has existed for more than 24 hours, and the Threatening Party has either Defected or Cooperated on that Confession more than 24 hours previously, and the Nerk has neither Defected nor Cooperated on that Confession.
When such a Threat is made, the Threatening Party may force the Nerk to either Defect or Cooperate on that Confession (this is the Threatening Party’s choice), by posting a comment to that effect on that Confession.

As

Either Party of a Confession may Threaten the other (the “Nerk”), if the Confession has existed for more than 24 hours, and the Threatening Party has made a Statement on that Confession more than 24 hours previously, and the Nerk has not made a Statement on that Confession.
When such a Threat is made, the Threatening Party must Sign their Statement on that confession, if they have not already done it, and then they may force the Nerk to either Defect or Cooperate on that Confession (this is the Threatening Party’s choice) without Signing the Nerk’s Statement, by posting a comment to that effect on that Confession.

Add a new Rule to the Ruleset, entitled Alignment Actions, with the following text:

Each Prisoner has a Junk field in the GNDT.
Each Prisoner has a RI (Rebellion Index) field in the GNDT.

The Junk field defaults to 0. It must be a natural number.
The RI field defaults to 1. It must be either 0 or a positive decimal number.

A Withdrawn may, as a weekly action, Withdraw. This stands for setting their own RI to 0.9. Doing so he foregoes every further daily actions this week.

A Rebel may, as a daily action, Cause Trouble. This stands for increasing the RI of them and any other Prisoner by 0.2.

A Colonizer may, as a daily action, Colonize. This stands for increasing their own Junk by 1, then increasing the Junk of any other Prisoner by 1.

A Converted may, as a daily action, Help Guards. This stands for decreasing the RI of them and any other Prisoner by 0.3.

 

Add a new Rule to the Ruleset, entitled Total Institution, with the following text:

Each Prisoner has an Alignment field in the GNDT.

The Alignment field of a Prisoner, except for the Warden, must be one of the following: Withdrawal; Rebellion; Colonization; Conversion. The Warden’s Alignment must be System.
A Prisoner whose Alignment is Withdrawal is called a Withdrawn; a Prisoner whose Alignment is Rebellion is called a Rebel; a Prisoner whose Alignment is Colonization is colled a Colonizer; a Prisoner whose Alignment is Conversion is called a Converted.
The Alignment field defaults to Withdrawal. Anyone may set the Alignment of an Idle Prisoner to Withdrawal.

As a weekly action, a Prisoner may Adapt. This stands for changing their own Alignment field to either: Withdrawal; Rebellion; Colonization; Conversion.

As a daily action, a Prisoner may Randomize-One’s-Own-Alignment. This stands for throwing 1DICE4 in the GNDT, then changing their own Alignment field according to the dice result:
if the result is 1, they must change their own Alignment to Withdrawal;
if the result is 2, they must change their own Alignment to Rebellion;
if the result is 3, they must change their own Alignment to Colonization;
if the result is 4, they must change their own Alignment to Conversion.
Anyway, if they are Withdrawn and would get the same Alignment, they must roll again.

A Withdrawn may not take any daily or weekly Action except for Randomize-Their-Own-Alignment, and daily or weekly actions which may explicitly be taken by a Withdrawn. Actions which are not explicitly described with the phrase daily or weekly don’t qualify as daily or weekly actions.

As a weekly action, the Warden may Mess-With-A-Prisoner. This stands for declaring any other Prisoner, then throwing 1DICE4 in the GNDT, then changing the declared Prisoner’s Alignment field according to the dice result:
if the result is 1, the Warden must change the declared Prisoner’s Alignment to Withdrawal;
if the result is 2, the Warden must change the declared Prisoner’s Alignment to Rebellion;
if the result is 3, the Warden must change the declared Prisoner’s Alignment to Colonization;
if the result is 4, the Warden must change the declared Prisoner’s Alignment to Conversion.

As a weekly action, an Admin or the Don may Mess-With-A-Newbie. This stands for declaring a non-Admin non-Warden non-Don Prisoner, then rolling 1DICE4 in the GNDT, then changing the declared Prisoner’s Alignment field according to the dice result:
if the result is 1, they must change the declared Prisoner’s Alignment to Withdrawal;
if the result is 2, they must change the declared Prisoner’s Alignment to Rebellion;
if the result is 3, they must change the declared Prisoner’s Alignment to Colonization;
if the result is 4, they must change the declared Prisoner’s Alignment to Conversion.

I was playing poker, and somebody sign-languaged me the other’s cards, and then bam! I was a Winner.

I confess, it was I and Winner who stole the Statue of Liberty.

The beginnings of a crude tunnel have been uncovered beneath the cracked tiles in the kitchen store room. The word in the exercise yard is that ShareDVI is the Suspect with the master plan, and Darknight their spoon-wielding Accomplice. Explain yourselves.

Add a new Rule to the Ruleset, called Alignment Actions.

Each Prisoner has a Junk field in the GNDT.
Each Prisoner has a RI (Rebellion Index) field in the GNDT.

The Junk field defaults to 0. It must be a natural number.
The RI field defaults to 1. It must be either 0 or a positive decimal number.

A Withdrawed may, as a weekly action, Withdraw. This stands for setting their own RI to 0.99. Doing so he foregoes every further weekly actions this week, except for Randomize-Their-Own-Alignment.

A Rebel may, as a weekly action, Cause Trouble. This stands for increasing their own RI by 0.1, then increasing the RI of any other Prisoner by 0.2.

A Colonizer may, as a weekly action, Colonize. This stands for increasing their own Junk by 1, then increasing the Junk of any other Prisoner by 1.

A Converted may, as a weekly action, Help Guards. This stands for decreasing their own RI by 0.15, then decreasing the RI of any other Prisoner by 0.25.

A Prisoner may, as a weekly action, Give Junk. This stands for decreasing their own Junk by 1, then modifying their own RI by 0.05 towards 1, then picking any other Prisoner, then increasing the picked Prisoner’s Junk by 1, then modifying the picked Prisoner’s RI by 0.05 towards 1. (If a RI is already 1, then modifying it towards 1 is equivalent to leaving it unchanged).

A Prisoner may, as a weekly action, Steal Junk. This stands for decresing the Junk of any other Prisoner by 1, then increasing their own Junk by 1. Then he may no more Give Junk to that Prisoner for the rest of the game.

A Prisoner may, as a weekly action, Trade Junk. This stands for picking a Prisoner whose Alignment is not Conversion, whose Junk is not 0 and whose Junk is the same as their own, then modifying the RI of both Prisoners by 0.15 towards 1. Then neither of the two Prisoners may Trade Junk with the other one for the rest of the game.

A Prisoner with RI less than 1 may, as a weekly action, Behave Well. This stands for decreasing their Sentence by 1 year.

A Prisoner with RI higher than 1 may, as a weekly action, Behave Bad. This stands for increasing their Sentence by 1 year.

Add a new Rule to the Ruleset, entitled Total Institution.

Each Prisoner has an Alignment field in the GNDT.

The Alignment field of a Prisoner, except for the Warden, must be one of the following: Withdrawal; Rebellion; Colonization; Conversion. The Warden’s Alignment must be blank. If a Rule does not provide instructions for the case in which a Prisoner has a blank Alignment, then the Warden is considered to have the Alignment Conversion.
A Prisoner whose Alignment is Withdrawal is called a Withdrawed; a Prisoner whose Alignment is Rebellion is called a Rebel; a Prisoner whose Alignment is Colonization is colled a Colonizer; a Prisoner whose Alignment is Conversion is called a Converted.
The Alignment field defaults to Withdrawal. Anyone may set the Alignment of an Idle Prisoner to Withdrawal.

As a weekly action, a Prisoner may Adapt. This stands for changing their own Alignment field to either: Withdrawal; Rebellion; Colonization; Conversion.

As a weekly action, a Prisoner may Randomize-Their-Own-Alignment. This stands for throwing 1DICE4 in the GNDT, then changing their own Alignment field according to the dice result:
if the result is 1, they must change their own Alignment to Withdrawal;
if the result is 2, they must change their own Alignment to Rebellion;
if the result is 3, they must change their own Alignment to Colonization;
if the result is 4, they must change their own Alignment to Conversion.
Anyway, if they would get the same Alignment they were before the roll, they must roll again.

A Withdrawed may not take any Action except for Randomize-Their-Own-Alignment, and actions which may explicitly be taken by a Withdrawed.

As a weekly action, the Warden may Mess-With-A-Prisoner. This stands for declaring any other Prisoner, then throwing 1DICE4 in the GNDT, then changing the declared Prisoner’s Alignment field according to the dice result:
if the result is 1, the Warden must change the declared Prisoner’s Alignment to Withdrawal;
if the result is 2, the Warden must change the declared Prisoner’s Alignment to Rebellion;
if the result is 3, the Warden must change the declared Prisoner’s Alignment to Colonization;
if the result is 4, the Warden must change the declared Prisoner’s Alignment to Conversion.

As a weekly action, an Admin or the Don may Mess-With-A-Newbie. This stands for declaring a non-Admin non-Warden non-Don Prisoner, then rolling 1DICE4 in the GNDT, then changing the declared Prisoner’s Alignment field according to the dice result:
if the result is 1, the enactor must change the declared Prisoner’s Alignment to Withdrawal;
if the result is 2, the enactor must change the declared Prisoner’s Alignment to Rebellion;
if the result is 3, the enactor must change the declared Prisoner’s Alignment to Colonization;
if the result is 4, the enactor must change the declared Prisoner’s Alignment to Conversion.

 

Hello, may I join the game?

Add a new rule to the ruleset, entitled The Don:

The Prisoner with the greatest Sentence is known as the Don.

When The Don Confesses to a Crime, they may increase their Sentence by 1 and name another Prisoner to be the Suspect rather than themselves.

In my long career as an international jewel thief, I was responsible for many marquee crimes. I was, for example, responsible for the theft of gemstones from the Vienna Opera House in 2007. I say that I was responsible. Of course, in reality, Purplebeard‘s support was essential in the conduct of this job.

Enact a subrule to “Confessions” titled “Rumours”:-

A Prisoner is a Fish if no other Prisoner has a lower Sentence than them.

As a daily communal action, any Prisoner may start a Rumour by posting a blog entry describing a Crime, with “Rumour:” in its title and naming two different Fish as the Crime’s Suspect and Accomplice in its body. Such a post is considered to be a Confession to the described Crime, with the two named Fish as its Suspect and Accomplice.

Formal request to join?

In “Confessions”, remove “If a Confession has existed for more than 72 hours, then any Prisoner who is its Crime’s Suspect or Accomplice is considered to have Cooperated on it, if they have not already Defected on it.”, then add a new paragraph:-

Either Party of a Confession may Threaten the other (the “Nerk”), if the Confession has existed for more than 24 hours, and the Threatening Party has either Defected or Cooperated on that Confession more than 24 hours previously, and the Nerk has neither Defected nor Cooperated on that Confession. When such a Threat is made, the Threatening Party may force the Nerk to either Defect or Cooperate on that Confession (this is the Threatening Party’s choice), by posting a comment to that effect on that Confession.

To the first paragraph of “Confessions”, add:-

The Suspect and Accomplice of a Confession are known as its Parties.

Add a new rule to the ruleset, entitled Grudges:

Each Prisoner can have up to one Grudge, which is tracked in the GNDT. A Prisoner’s Grudge must be the name of one other Prisoner.

A Prisoner may change or clear their Grudge as a daily action.

Whenever a Prisoner’s is the Suspect or Accomplice in a Confession in which their Grudge is also a Suspect or Accomplice, and - as a result of that Confession - their Grudge’s Sentence increases, that Prisoner may Roll On their Grudge within 24 hours of the resolution of that Confession. A Prisoner Rolls On another Prisoner by increasing their Sentence by 1 and setting their own Grudge to blank.

I give up, I confess, it was I what done it. I snuck in in the dead of night and switched the Duchess’ tiara for a fake, a cheap fake. I couldn’t have done it without Kevan‘s help though, he’s the best leg-man in the business.

I, and Darknight too, have stolen your precious time you spent reading this blog post.

To the rule “Sentences”, add:-

The Warden’s Sentence is considered to be a measure of Demerits against his employment record.

In the Appendix, in the section “Clarifications” in the rule “Names”, reword

Within the ruleset, a word only refers to the name of a Prisoner if it is explicitly stated that it refers to a Prisoner’s name.

as

Within the ruleset, a word only refers to the name of a Prisoner or to the name of a Gamestate Tracking Entity if it is explicitly stated that it refers to such name.

In the Appendix, in the section Keywords, add a Keyword “Name of a Prisoner” with the text

Name of a Prisoner is their current Blognomic account name

Add a Keyword “Name of an Idle Prisoner” with the text

Name of an Idle Prisoner is their current Blognomic account name

If Proposal: Sentence Structure is enacted, replace the rule “Sentences”

  Each Prisoner has a Sentence, being a number measured in years and defaulting to zero. This is tracked in the GNDT.

  When a Prisoner joins the game or unidles for the first time during this dynasty, their Sentence is instead set to the mean value of all other Prisoner’s Sentences (rounding down).

with

  Each Prisoner has a Sentence, being a number measured in years and defaulting to the mean value of all other Prisoner’s Sentences (rounding down). This is tracked in the GNDT.

Enact a new rule, “Confessions”:-

As a daily action, a Prisoner may confess to a Crime by posting a blog entry to this effect, with “Crime:” in its title and naming a single other Prisoner as the Crime’s Accomplice in its body. A post such as this is known as a Confession to that Crime, and the Prisoner who posted it is the Crime’s Suspect.

A Crime’s Suspect or Accomplice may respond to its Confession with a Statement (if they have not already done so on that Confession), being a blog comment to that Confession which contains a single Hash.

A Crime’s Suspect or Accomplice may Sign a Statement he or she has made by posting a follow-up comment on the same Confession which specifies a piece of text whose Hash is the same as the Hash in their Statement. Upon doing so: if that piece of text contains the word “defect” (with any capitalisation) then the Prisoner who wrote the Statement has Defected on that Confession, otherwise they have Cooperated.

If both Prisoners have either Cooperated or Defected on a Confession, then any Prisoner may update the gamestate as follows for that Confession, after which point the Confession is over and ceases to be a Confession:

• If the Suspect and Accomplice both Cooperated, each has their Sentence increased by 1 year.
• If the Suspect Cooperated and the Accomplice Defected, the Suspect has their Sentence increased by 3 years.
• If the Suspect Defected and the Accomplice Cooperated, the Accomplice has their Sentence increased by 3 years.
• If the Suspect and Accomplice both Defected, each has their Sentence increased by 2 years.

If a Confession has existed for more than 72 hours, then any Prisoner who is its Crime’s Suspect or Accomplice is considered to have Cooperated on it, if they have not already Defected on it. If a Criminal ceases to be a Criminal for any reason, then any Confession for whose Crime they are a Suspect or an Accomplice ceases to be a Confession.

Move the rule “Hashes” to the end of the dynastic ruleset, and reword it to:-

A string of 32 hexademical characters is known as a Hash. The Hash of a piece of text is the MD5 Hash generated for it at http://www.miraclesalad.com/webtools/md5.php.

Enact a new rule, “Sentences”:-

Each Prisoner has a Sentence, being a number measured in years and defaulting to zero. This is tracked in the GNDT.

When a Prisoner joins the game or unidles for the first time during this dynasty, their Sentence is instead set to the mean value of all other Prisoner’s Sentences (rounding down).

Retribution was swift after the massive leak of JoshCorp client data. Five million confidential profiles had appeared overnight on a public offshore server, without a single speck of a data trail. The tech teams were mystified, but corporate security saw no reason not to round up the usual suspects, skimming the background network traffic from the previous few weeks, kicking down a number of carefully-chosen doors, and dragging a group of protesting misfits along to the stark and separate concrete cells of Quandary State Penitentiary.

It would only be a matter of time.

Change “Hacker” to “Prisoner” and “Zero Cool” to “Warden”. Do not repeal the rule “Hashes” when blanking the dynastic rules.

Amend the part of Victory and Ascension which reads:

When a DoV is enacted, all other active DoVs are failed

To read:

When a DoV is enacted, all other active DoVs and any pending Proposals are failed

The CfJs on the legality of the Codename “:Corp Names” possessing five Secrets have both reached a quorum of supporters. I have now retired that Codename, and under the rule “Hack the Planet” I have achieved victory.

Add the following to the bulleted list in the core rule entitled “Fair Play”:

* An Admin should not use the powers conferred specifically upon Admins as a class by the ruleset to gain any gamestate advantage that a non-Admin would not be able to access, except in cases where a rule specifically states that it is conferring an award upon Admins for the fulfilment of their duties.

In the rule “Denizens” replace

As a weekly action, a Hacker may set up a new Codename by adding it as an NPC in the GNDT, with a unique name of their choosing that is preceded by a colon to denote that it is a Codename.

with

As a weekly action, a Hacker may set up a new Codename by adding it as an NPC in the GNDT, with a unique name of their choosing (not equal to any of the requested Codenames in valid :PROTO requests according to the rule “Ensuring Access”)  that is preceded by a colon to denote that it is a Codename.

A Codename has been created with the name :Corp Names, which exploits the wording in the ruleset that Secrets “for Corp Names… defaults to 5.”

However, rule 3.3.5 states that “within the ruleset, a word only refers to the name of a Hacker if it is explicitly stated that it refers to a Hacker’s name.” Codenames and Corp Names are both clearly types of “names of a Hacker” - ‘name’ is not a defined keyword, and a plain-English reading of both Corp Name and Codename would suggest that they are both subsets of ‘name’ in this regard. The Secrets rule does not specify that Corp Names refers to a name.

Furthermore, the Codename in question is :Corp Names, not Corp Names; the colon at the front cannot be elided from the name as a matter of convenience.

If this CfJ passes, set the Secrets of the Codename called :Corp Names to zero, and change its name to :ZZZYYY.

I have created a Codename “Corp Names” and set its Number of Secrets to 5 as per

Secrets

Each Corp Name and Codename has a number of Secrets, which is tracked in the GNDT. For Corp Names this defaults to 5; for Codenames it defaults to zero.

This rule

Names

  Within the ruleset, a word only refers to the name of a Hacker if it is explicitly stated that it refers to a Hacker’s name.

applies only to Hacker Names, neither to Codenames, nor to Corp Names

Each Hacker has a Corp Name and any number of Codenames. Their Corp Name is the same as their BlogNomic account name, and is public.

As a weekly action, a Hacker may set up a new Codename by adding it as an NPC in the GNDT, with a unique name of their choosing that is preceded by a colon to denote that it is a Codename.

Moreover,

If both contradicting parts are Core Rules, or if both of them are Dynastic Rules, the part with more limited scope applies. (e.g. if the rules “Hackers may Kick each other” and “Hackers may not kick each other on Tuesdays” exist, and it is Tuesday, Hackers may not Kick each other.)

I suggest that the number of secrets of the codename “Corp Names” should be set to 5.

In the definition for the keyword Slack, replace “Hackers” with “Anyone”, and remove “while logged in”. Append to the definition:

If a Hacker has an account on the Slack, their Slack username should be as close to their BlogNomic username as possible. Slack usernames are editable, and only need to be unique within the BlogNomic Slack.

In the definition for the keyword Slack, replace “Hackers” with “Any human”, and remove “while logged in”. Append to the definition:

If a Hacker has an account on the Slack, their Slack username should be as close to their BlogNomic username as possible. Slack usernames are editable, and only need to be unique within the BlogNomic Slack.

Add a paragraph after the first in “Corporate Defence”:-

As a weekly communal action, a Hacker may increase every Corp Name’s Defence Score by 3 (to a maximum of 10).

Add a new paragraph to “Corporate Defence”:-

When a Hacker Terminates a Codename as a result of an Investigation, they may give their Corp Name an amount of Defence Score equal to the amount expended by the Investigation’s Commencement plus one. If any Hacker is able to prove that an Investigation was Flawed (i.e. the Hacker specified as owning the Codename did not own that Codename), then they may (if nobody has already done so for that Investigation, and if the Investigation was resolved less than 48 hours ago) reduce the Defence Score of the Corp Name of the Hacker who initiated the Investigation by that Investigation’s Cost, plus one.

In “Denizens”, replace “As a daily action, a Hacker may set up a new Codename” with:-

As a weekly action, a Hacker may set up a new Codename

Add to the Keywords in the Appendix to the Rules:

Slack
  The BlogNomic Slack is located at blognomic.slack.com. Hackers may request an invite to the Slack while logged in by clicking the button in the sidebar.
  Slack Channel
    A Slack Channel is any channel on the BlogNomic Slack. To reference a Slack Channel, use a hash (#) followed by the name of that channel. (For example, #random.)

If a majority of EVCs on this Proposal do not contain the word REALLY in all caps, indent the Keywords (and respective definitions) “Daily Communal Action”, “May not” and “Weekly Communal Action” one step further.

If you’re logged in, it’s under the player list. Click “Get an invite!” to get an invite, or click the Slack logo to go to Slack.

To the end of the rule “Security”, add:-

If a Subroutine is “negated” by a Security Measure, then that instance of the Subroutine is not considered to be part of the Tool for the remainder of the Hack.

In “Tools of the Trade”, replace “then has the effects of any Valid Security Measures applied to it” with:

then has the effects of any Valid Security Measures applied to it in the order they are listed in the Corp Name’s GNDT field,

Add a paragraph after the first in “Corporate Defence”:-

As a weekly action, a Hacker may increase every Corp Name’s Defence Score by 3 (to a maximum of 10).

Add a new rule to the ruleset, entitled Hack the Planet:

If at any time a Hacker has their name in the Hacker field of any number of Retired Codenames that have, collectively, at least five secrets, that Hacker has achieved Victory.

BEGIN ENCRYPTED MESSAGE
——————————————————————

Uryyb Ynqvrf naq
Tragyrzra, V urneq bs Abzvp n tbbq znal qnlf ntb naq qrpvqrq gb svanyyl svaq n ehaavat tnzr gbqnl gb qvir vagb.

Zl anzr vf Rib naq V’z ernql gb cynl.

V fgvyy unir lrg gb tenfc rknpgyl ubj guvf Unpxre Qlanfgl Gurzr jbexf…

Ohg V ybir pbzchgref naq pelcgbtencul, fb V’z fher V jvyy yrnea fbba.

Gb fgneg bss ba gur evtug sbbg, V svtherq V jbhyq rapelcg zl vavgvny vagebqhpgbel cbfg…

Unpxref arire pbzzhavpngr va cynvagrkg! ;)

Purref, Rib

————————————————————-
END ENCRYPTED MESSAGE

In “Tools of the Trade”, reword the effect of the Amplifier from “If this is the leftmost Subroutine in the Tool, then the Hack Value of this Tool is doubled.” to:-

If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.

In “Corporate Defence”, replace the sentence beginning “They may then remove the Codename from the GNDT” with:-

They may then Terminate that Codename by blanking its Tool and Secrets and setting its Hacker field to “TERMINATED”. A Terminated Codename is not considered to be a Codename for any other dynastic rule unless explicitly stated.

If “Corps Need More Tool” passed, add “When a Hacker terminates a Codename, it may increase its Corp Name’s Secrets by 1.” to the end of that paragraph.

In “Ensuring Access”, replace “Any admin should create the requested Codename at their earliest opportunity” with:-

Any admin should create the requested Codename at their earliest opportunity, with a GNDT comment that repeats the Sign Hash of the creation request and contains no other Hashes

Add the following as a new rule, entitled Defence Generation, to the ruleset, as a subrule of the rule called “Corporate Defence”:

As a daily action, a Corp can sell one of its Secrets for a one-time increase of 2 to their Defence Score.

Add the following to the list of Valid Security Measures:

* = - Tracking Device - If a successful Hack is carried out against a Corp Name with this Valid Security Measure then the Corp Name may, once within 24 hours of the successful hack, remove this Valid Security Measure and increase their Secrets by 2.

In the rule entitled Corporate Defence, change “A Hacker may resolve an Investigation at any point” to “A Hacker may resolve an Investigation that they started at any point”. In the same rule, add “and may increase their own Secrets by 1” to the end of the last sentence.

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

* i - Infection - After a hack replace a Valid Security Measure of the target Corp Name of the Codename’s choosing with a Virus

Add the following to the list of Valid Security Measures in the subrule named “Security”:

* V - Virus - Subtracts ((the number of viruses of this Corp Name-1)*2) from the Defence Score of this Corp Name.

Amend the first paragraph in “Tools of the Trade” to read:

Each Codename has a Tool, which is tracked in the GNDT as a string of characters. Each character represents a subroutine in their Tool. When the Hack Value of a Tool is calculated by a Hacker, it starts at zero and then has the effects of any Valid Security Measures applied to it then of each of its Subroutines applied once in the order that they are listed in the Tool’s GNDT field.

If Proposal: Icing Up is enacted:

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

* i - Infection - After a hack replace a Valid Security Measure of the target Corp Name of the Codename’s choosing with a Virus

Add the following to the list of Valid Security Measures in the subrule named “Security”:

* V - Virus - Subtracts ((the number of viruses of this Corp Name-1)*2) from the Defence Score of this Corp Name.

Amend the first paragraph in “Tools of the Trade” to read:

Each Codename has a Tool, which is tracked in the GNDT as a string of alphanumeric characters. Each character represents a subroutine in their Tool. When the Hack Value of a Tool is calculated by a Hacker, it starts at zero and then has the effects of any Valid Security Measures applied to it then of each of its Subroutines applied once in the order that they are listed in the Tool’s GNDT field.

Replace “Each Hacker has a Corp Name and any number of Codenames. Their Corp Name is the same as their BlogNomic account name, and is public.” with:-

Each Hacker secretly funds the work of a number of Codenames.

Then, replace “Hacker” with “Corporation” throughout the ruleset.

Then, replace “Corp Name” with “Corporation” throughout the ruleset.

Then, replace “Codename” with “Hacker” throughout the ruleset.

Then replace “As a daily action, a Corporation may, on behalf of their Corporation, Investigate a Hacker” with “As a daily action, a Corporation may Investigate a Hacker”.

Then replace “own Corporation and no other Corporation” with “own name and the names of no other Corporations”.

Then replace “the Corporation must expend at least 1 from the Defence Score of their Corporation” with “the Corporation must expend at least 1 from their Defence Score”.

Then replace any sentence beginning “At any time, a Corporation may reduce its Corporations’s Defence Score” with “At any time, a Corporation may reduce its Defence Score or Secrets by 1 to gain any Security Measure.”

In the rule “Security”, replace “| - Firewall” with “/ - Firewall”.

Add rule “Sw33t t33rz of t3h PWNd”:

If the number of Secrets of all Corp Names is equal to 0, the Hackers who control the Codenames with the maximal amount of Secrets, win.

In the rule “Tools of the Trade”, replace

As a daily action, a Hacker may add a Subroutine to the Tool of any Codename.

with

As a daily action, a Hacker may add a Subroutine to the right of the Tool of any Codename.

.

Replace

& - Back Door - Replicates the effect of another Subroutine in this Tool, of the Codename’s choosing

with

& - Back Door - Replicates the effect of another Subroutine in this Tool to the right of this Back Door. The Subroutine to be replicated may be chosen before making a Hack by the Hacker who controls this Codename.

Replace

2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.

with

2 - Amplifier - If this is the leftmost Subroutine in the Tool, then the Hack Value of this Tool is doubled.

Replace

All Back Doors after a Root Access are removed.

with

After a Hack Attempt with this Tool, all Back Doors after a Root Access are removed.

If the proposal ‘Icing Up’ is enacted, replace in the rule “Corporate Defence”

At any time, a Hacker may reduce its Corp Name’s Defence Score or Secrets by 1 to add any Security Measure to that Corp Name.

with

At any time, a Hacker may reduce its Corp Name’s Defence Score or Secrets by 1 to add any Security Measure to the right of the Security Measures list of that Corp Name.

If the proposal ‘Icing Up’ is enacted, replace in the rule “Tools of the Trade”

@ - Blaster - Reduce the Defence Value of the target Corp Name by 1 permanently before carrying out a Hack with this Tool

with

@ - Blaster - Before carrying out a Hack with this Tool, permanently destroy the rightmost Security Measure of target Corp Name or, if target Corp Name has no Security Measures, reduce the defence Value of the target Corp Name by 1 permanently

If Proposal: Icing Up is enacted:

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

* / - Infection - After a hack replace a Valid Security Measure of the target Corp Name of the Codename’s choosing with a Virus

Add the following to the list of Valid Security Measures in the subrule named “Security”:

* % - Virus - Subtracts ((the number of viruses of this Corp Name-1)*2) from the Defence Score of this Corp Name.

Amend the first paragraph in “Tools of the Trade” to read:

Each Codename has a Tool, which is tracked in the GNDT as a string of alphanumeric characters. Each character represents a subroutine in their Tool. When the Hack Value of a Tool is calculated by a Hacker, it starts at zero and then has the effects of any Valid Security Measures applied to it then of each of its Subroutines applied once in the order that they are listed in the Tool’s GNDT field.

Replace “Each Codename has a Tool, which is tracked in the GNDT as a string of alphanumeric characters” with:-

Each Codename has a Tool, which is tracked in the GNDT as a string of characters

Any past addition of a non-alphanumeric character to a GNDT “Tool” field this dynasty, as well as Purplebeard’s Corp Name’s Defence Score being reduced by a Hack on the 10th of August, shall be considered illegal.

Set :Flatline’s Tool to “~”, :Faction’s Tool to “&”, :Enthalpy’s Tool to “2” and reduce Purplebeard Corp Name’s Defence Score by 2.

Replace “Each Codename has a Tool, which is tracked in the GNDT as a string of alphanumeric characters” with:-

Each Codename has a Tool, which is tracked in the GNDT as a string of characters

Update the gamestate to what it would have been if all non-alphanumeric characters added to Tools prior to this proposal being made, and all actions made as a result of such Tools existing, were considered legal.

Add a subrule to “Corporate Defence” called “Security”:

A Corp Name may have zero or more Security Measures, tracked as non-numeral characters in the Corp Name’s “Tool” field.

At any time, a Hacker may reduce its Corp Name’s Defence Score or Secrets by 1 to add any Security Measure to that Corp Name.

Valid Security Measures and their effects are:

• | - Firewall - Each Firewall a Corp Name has negates the rightmost Subroutine in the Hack Tool of any Codename which makes a Hack against that Corp Name.
• @ - Honeypot - Each Honeypot a Corp Name has negates the leftmost Subroutine in the Hack Tool of any Codename which makes a Hack against that Corp Name.
• ) - Shield - Adds +1 to the Defence Score of this Corp Name.

ShareDVI-Corp spends 1 Defence points to investigate Purplebeard‘s involvement in a recent hack by :Enthalpy

Add a new sub-rule to the rule called Denizens, entitled Ensuring Access:

Each Codename has a Hacker field in the GNDT. To ensure that equal access to GNDT functions is given to Hackers who are not admins, the password for each Codename account is publicly tracked in that Codename’s Hacker field.

At any time, there should be a Proto-Codename available in the GNDT, with the name :PROTO. If at any point there is no Proto-Codename account, any admin should create it. Proto-Codename accounts are not considered to be Codenames for the purposes of any rule apart from this one. Whenever a non-admin Hacker wishes to create a Codename, they may post a comment to the GNDT using a Proto-Codename Account, specifying their desired Codename and password, and Signing it. Any admin should create the requested Codename at their earliest opportunity; if this has not been completed within 24 hours of the request being made then the Zero Cool must create the requested Codename.

Rewrite the rule “Corporate Defence” to the following:

Each Corp Name has a Defence Score, which is a numerical value and defaults to 10.
Each Corp Name has a Defence Tool, which is a string of alphanumeric characters. Each character represents a subroutine in their Defence Tool. When the Actual Defence Score of a Tool is calculated by a Hacker, it starts at zero and then has the effects of each of its Subroutines applied once in the order that they are listed in the Tool’s GNDT field.

Defence Score and Defence Tool are tracked in the GNDT under the “Tool” field in the following order: Defence Score first, and then Defence Tool.

As a daily action, a Hacker may add a Subroutine to any Corp Name Defence Tool.
Subroutines that currently exist are as follows:
* | - Firewall - two consecutive Firewalls negate the rightmost Subroutine in the Hack Tool of the Codename, which makes a Hack against this Corp Name
* @ - Honeypot -  three consecutive Honeypots remove the leftmost and the rightmost Subroutine in the Hack Tool of the Codename, which makes a Hack against this Corp Name
* ) - Shield - adds +1 to the Defence Score of this Corp Name

In the Hacking rule, add:

If the Hack against a Corp Name is successful, remove the Defence Tool of that Corp Name.
If the Hack against a Corp Name is unsuccessful, remove the rightmost Subroutine from the Defence Tool of that Corp Name.

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

* # - Root Access - all non-Elevated Subroutines between two Root Accesses become Elevated. Elevated Subroutines gain +1 Hack Value. All Back Doors after a Root Access are removed.

I idle out; quorum drops to 4.

Add the following to the rule entitled Corporate Defence:

As a daily action, a Hacker may, on behalf of their Corp Name, Investigate a Codename, provided that they are not currently carrying out another such Investigation.

In order to commence an Investigation, the Hacker must expend at least 1 from the Defence Score of their Corp Name, and must then make a Story Post whose title starts with the word “Investigation:”, and which specifies a single Codename, and the Hacker who they believe owns that Codename.

A Hacker may resolve an Investigation at any point, provided that it is not sooner than 25 hours minus 1 hour for each point of Defence Score spent to initiate that Investigation after it has been initially posted. To resolve an Investigation, the Hacker must comment to the Investigation Post to the effect that the Investigation is complete. They may then remove the Codename from the GNDT; any subroutines it had in its Tool or Secrets it had accumulated are lost.

Add the following as a subrule to the rule called Denizens, entitled Retirement:

At any time, a Hacker may chose to Retire a Codename that they control. Retired Codenames are signified in the GNDT by having the name of the Hacker who controlled them in the “Hacker” field. A Retired Codename is not considered to be a Codename for any other dynastic rule unless explicitly stated.

I hereby officially ask to join BlogNomic. Woot woot!

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

* ? - Bug - -1 to the Hack Value of this Tool
* ~ - Workaround - +4 to the Hack Value of this Tool, then turns into a Bug (this Bug is not processed for the calculation during which it was created)

Also, in the description of the Back Door, change “of the Hacker’s choosing” to “of the Codename’s choosing”.

Hi, everyone. The old wiki has been up for several months now, but I’m starting to think of (at least temporarily) decommissioning the server it lives on. I’ll keep a backup, of course, but how confident do you guys feel that everything legitimate has been moved over to the new wiki? If everyone says it’s okay, I’ll probably take it down next weekend.

Add a new rule to the ruleset, entitled Secrets:

Each Corp Name and Codename has a number of Secrets, which is tracked in the GNDT. For Corp Names this defaults to 5; for Codenames it defaults to zero.

Change the last paragraph of the rule entitled “Hacking” to read as follows:

If the Hack is successful, the Codename may reduce the Secrets of the Corp Name by 1 and increase their own Secrets by 1, as a Covert Action. They must then make a GNDT comment detailing the target of the Hack and its outcome, as a Covert Action. If the Hack is unsuccessful, then the Codename must lose one Subroutine of its choice from its Tool, as a Covert Action.

Rewrite the rule named “Denizens” to the following:

Each Hacker has a Corp Name and any number of Codenames. A Hacker’s Corp Name is the same as their BlogNomic account name, and is public.

As a Daily Action, a Hacker may set up a new Codename by making an Anonymous post that contains a single unique name of their choosing that is preceded by a colon to denote that it is a Codename. This post must also contain the Hash of a grammatical English sentence of no more than 20 words which includes the Hacker’s own Corp Name and no other Corp Names, which will be that Codename’s Ident. The post may be processed once by any admin by adding the Codename and its Ident to the GNDT. If the chosen Codename and Ident are not unambiguously identifiable from such a post, it is invalid.

If ever the ownership of a Codename becomes the subject of a Call for Judgement and it is determined that ownership of that Codename cannot be definitively proved, any Hacker may remove that Codename from the GNDT.

Create an “Ident” column in the GNDT and add the Idents that were known immediately prior to this proposal’s passing.

Add the following to the Keywords section of the Appendix (maintaining alphabetical order):

Anonymous
  A Hacker may make an Anonymous Post by setting the author (under ‘Options’) to “Anonymous”. Anonymous posts have no effect on the Gamestate unless a Rule specifies otherwise.

After more than three years of being idle, I’m excited to return to the world of blognomic and I am requesting to deIdle. Glad to see so many familiar faces still here.

So far as I can tell the Codename “:Hacktivate” is invalid - its creation with that name predates the enactment of Colonic, and the act of creating an NPC with a colon in the name was not legally permitted at that time. It exists as an NPC in the GNDT, but it is not a Codename as recognised by the ruleset.

I’ve removed it from the GNDT.

In “Tools of the Trade”, replace “The Hack Value of a Tool is defined by its subroutines. Where a Tool contains multiple versions of the same subroutine, its effects are cumulative unless otherwise stated.” with:-

When the Hack Value of a Tool is calculated by a Hacker, it starts at zero and then has the effects of each of its Subroutines applied once in the order that they are listed in the Tool’s GNDT field.

Add a subroutine to the list:

• 2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.

In “Hacking”, replace “In order to do so, they must select a Codename to use for the attack and a Corp Name to be its target. They must then compare the Hack Value of the Tool of their chosen Codename against the Defence Score of the Corp that is the target.” with:-

In order to do so, they must select a Corp Name to be their target, and compare the Hack Value of their Tool against the Defence Score of the Corp that is their target.

If this proposal passes it has no effect.

In the rule entitled “Denizens”, change the text “followed by an asterisk” to “preceded by a colon”.

In “Denizens”, replace “Thereafter, it is the responsibility of each Hacker to keep their ownership of their Codenames both secret and provable, by whatever means they deem most secure.” with:-

The earliest md5 hash posted by a Codename in a GNDT comment is known as its Ident: if a Hacker demonstrates that a Codename’s Ident is identical to the Hash of a grammatical English sentence of no more than 20 words which includes the Hacker’s own Corp Name and no other Corp Names, then that Hacker is said to control that Codename.

Add a subrule to “Denizens” called “Covert Actions”:

If a Codename is able to take a Covert Action, any Hacker may take that Action on the Codename’s behalf (making any decisions required of it themselves) by updating the GNDT, while logged in as that Codename.

If a Covert Action is also Traceable, then the GNDT action corresponding to it must be Signed by the Hacker somewhere in its “Comments” field.

Replace “As a daily action, a Hacker can make a Hack against a Corp Name.” with:-

If it has not already done so during the current day, nor within the past 10 hours, a Codename can make a Hack against a Corp Name. This is a Covert, Traceable Action.

Replace “If the Hack is successful. the Hacker must make a Story Post detailing the target of the Hack and its outcome. If the Hack is unsuccessful then the Hacker must remove one Subroutine from the Tool of the Codename that they have used.” with:-

If the Hack is successful, the Codename must make a GNDT comment detailing the target of the Hack and its outcome, as a Covert Action. If the Hack is unsuccessful, then the Codename must lose one Subroutine of its choice from its Tool, as a Covert Action.

Add a new rule to the ruleset, entitled Hacking:

As a daily action, a Hacker can make a Hack against a Corp Name.

In order to do so, they must select a Codename to use for the attack and a Corp Name to be its target. They must then compare the Hack Value of the Tool of their chosen Codename against the Defence Score of the Corp that is the target. If the Hack Value of the Tool is greater than the Defence Value of the Corp then the Hack is successful. Otherwise, it is unsuccessful.

If the Hack is successful. the Hacker must make a Story Post detailing the target of the Hack and its outcome. If the Hack is unsuccessful then the Hacker must remove one Subroutine from the Tool of the Codename that they have used.

In the rule entitled “Tools of the Trade”, add the following to the end of the first paragraph: “The Hack Value of a Tool is defined by its subroutines. Where a Tool contains multiple versions of the same subroutine, its effects are cumulative unless otherwise stated.”

In the same rule, replace the bulleted list with the following:

• ^ - Slicer - +2 to the Hack Value of this Tool
• @ - Blaster - Reduce the Defence Value of the target Corp Name by 1 permanently before carrying out a Hack with this Tool
• & - Back Door - Replicates the effect of another Subroutine in this Tool, of the Hacker’s choosing

So I took note at the little brief description box that welcomes anyone who visits the site while not logged in and I must state that the current neon green on white for it is utter murder to the eye. By chance is that able to be a normal black on white while leaving the neon green for the main body of the site?

In “Tools of the Trade”, replace “As a daily action, a Hacker may add a Subroutine to the Tool of a Codename that they control.” with:-

As a daily action, a Hacker may add a Subroutine to the Tool of any Codename.

Enact a new rule, “Hashes”:-

The Hash of a Sentence is the MD5 Hash generated for it at http://www.miraclesalad.com/webtools/md5.php.

When a Hacker is required to Sign something, they should choose a grammatical English sentence of no more than 20 words which includes their own Corp Name and no other Corp Names, and then determine the Hash of that Sentence. This Hash should be written in full wherever the Hacker is required to Sign, and Hackers are encouraged to keep a private note of each sentence they choose and its Hash.

If Proposal: Hack the Planet did not pass, this proposal does nothing.

Add a new rule to the ruleset, entitled Tools of the Trade:

Each Codename has a Tool, which is tracked in the GNDT as a string of alphanumeric characters. Each character represents a subroutine in their Tool.

As a daily action, a Hacker may add a Subroutine to the Tool of a Codename that they control.

Subroutines that currently exist are as follows:

• ^
• &
• @

Each Corp Name has a Defence Score, which is a numerical value that is tracked in the GNDT under the “Tool” field, and which defaults to 10.

Add a new rule to the ruleset, entitled Denizens:

Each Hacker has a Corp Name and any number of Codenames. Their Corp Name is the same as their BlogNomic account name, and is public.

As a daily action, a Hacker may set up a new Codename by adding it as an NPC in the GNDT, with a unique name of their choosing that is followed by an asterisk to denote that it is a Codename. Thereafter, it is the responsibility of each Hacker to keep their ownership of their Codenames both secret and provable, by whatever means they deem most secure. If ever the ownership of a Codename becomes the subject of a Call for Judgement and it is determined that ownership of that Codename cannot be definitively proved, any Hacker may remove that Codename from the GNDT.

Idle Hackers may control Codenames. Any dynastic rule that affects Codenames is considered to affect Idle Hackers who control Codenames. Idle Hacker are not considered to be Hackers for any other rule.

“I am all-powerful Time which destroys all things, and I have come here to slay these men. Even if thou doest not fight, all the warriors facing thee shall die.”

Entire text of the NexusCorp website, June 5th 1997, 8.15am – 17.37pm GMT.

Repeal all dynastic rules. Replace “Rat” with “Hacker” and “Head Scientist” with “Zero Cool” throughout the ruleset.

Which is super relevant.

The Ascension Address will come within the next 24 hours. In the meanwhile, please do use this to discuss the last dynasty, any aspirations for the next, and any ideas you have about recruiting new members.

Repeal the rule “Classical Conditioning”.

The rule “Classical Conditioning” says that a Rat may carry out a Conditioned Action, which is “any action that they have successfully carried out at least five times prior to the Conditioned Action being carried out”. It also says that a Conditioned Action has no other preconditions.

Therefore, on the grounds that I have successfully achieved victory five times in the past, my Conditioned Action for today is to achieve victory again.

They’re now a complementary purple.

Add a new rule to the ruleset, entitled Classical Conditioning:

As a weekly action, a Rat may perform a Conditioned Action. A Conditioned Action is any action that they have successfully carried out at least five times prior to the Conditioned Action being carried out. A Conditioned Action has no other preconditions, regardless of what preconditions may exist for the action being imitated.

• Task: In the comment in which you Accepted the Test, write either A or B. Further instructions will be included in a Post titled “Revealing the Mystery Meat” within one hour of the Acceptance Deadline, the contents of which will then be considered part of the Task.
• Acceptance Deadline: 11:00, Wednesday 5 August, 2015
• Completion Deadline: 11:00, Sunday 9 August, 2015
• Reward: +10 Learning
• Punishment: -2 Cheese

A Hypothesis has been formed.

When voting FOR this proposal, the number of the option you prefer should be specified. The one/s with the most or tied for the most votes, should the Proposal as a whole be enacted, will be enacted as far as is legal, the rest will be discarded.

1. Add a Tranquilliser to Cell F2 and update the rule “Tranquillisers” and the wiki page “The Maze” accordingly.
2. Add a Tranquilliser to Cell F2 and update the rule “Tranquillisers” and the wiki page “The Maze” accordingly.
3. Add a Tranquilliser to Cell F2 and update the rule “Tranquillisers” and the wiki page “The Maze” accordingly.

Undeterred, a new Hypothesis is being tested.

Josh, Kevan and Purplebeard have all… passed… the Test, and gain 1 Learning apiece.

Cells nominated: F2, F2 and F2.

The hypothesis that I formed on 25/7 was that the Rat named Kevan would form exactly one hypothesis. This expectation was not met and as such my hypothesis was unsuccessful.

Replace:

A Pending CFJ may be Resolved by an Admin if it has a Quorum of FOR Votes, a Quorum of AGAINST Votes, or if it has been open for voting for more than 48 hours. When a CFJ is Resolved, it is to be Enacted if it has more FOR Votes than AGAINST Votes and Failed otherwise. When a CFJ is Enacted, the Admin Enacting it shall update the Gamestate and Ruleset, and correct the GNDT and other gamestate tracking entities, as specified in the CFJ.

With:

A Pending CFJ may be Resolved by an Admin if it has a Quorum of FOR Votes, a Quorum of AGAINST Votes, or if it has been open for voting for more than 48 hours. When a CFJ is Resolved, it is to be Enacted if it has more FOR Votes than AGAINST Votes and has more than one vote, and Failed otherwise. When a CFJ is Enacted, the Admin Enacting it shall update the Gamestate and Ruleset, and correct the GNDT and other gamestate tracking entities, as specified in the CFJ.

So last night I move to the active cheese spawner and yet today I somehow find myself moved back to a new tranq space. Unless there was a rule I missed,

If this passes, return DAR to his position at the active cheese spawner.

So last night I move to the active cheese spawner and yet today I somehow find myself moved back to a new tranq space. Unless there was a rule I missed,

If this passes, return DAR to his position at the active cheese spawner.

Replace:

If a Rat which has accepted a Test completes the Task before the Completion Deadline, it will receive the Reward, and must add 1 to their Success Rate. If a Rat which has accepted a Test fails to complete the Task before the Completion Deadline, it will receive the Punishment, and must subtract 1 from their Success Rate.

With:

If a Rat which has accepted a Test completes the Task before the Completion Deadline, it will receive the Reward, and gains 1 Success Rate. If a Rat which has accepted a Test fails to complete the Task before the Completion Deadline, it will receive the Punishment, and loses 1 Success Rate.

Within 24 hours of a Test having ended, the Head Scientist must Resolve it by:

• Making a Story Post with a title starting with “Test Resolution: ” followed by the name of the Test. This must include the results of the Test, which must state who has passed or failed, and may include commentary on the Test.
• Update the gamestate to reflect any Rewards and/or Punishments given.
• Close to comments the original Story Post which contained the Test.

Replace:

If a Rat which has accepted a Test completes the Task before the Completion Deadline, it will receive the Reward, and must add 1 to their Success Rate. If a Rat which has accepted a Test fails to complete the Task before the Completion Deadline, it will receive the Punishment, and must subtract 1 from their Success Rate.

With:

If a Rat which has accepted a Test completes the Task before the Completion Deadline, it will receive the Reward, and gains 1 Success Rate. If a Rat which has accepted a Test fails to complete the Task before the Completion Deadline, it will receive the Punishment, and loses 1 Success Rate.

• Task: In the same comment in which you Accepted the Task, nominate any one cell which can legally contain a Tranquilliser.
• Acceptance Deadline: 08:00:00, Sunday 2 August, 2015
• Completion Deadline: 08:00:01, Sunday 2 August, 2015
• Reward: +1 Learning, -1 Success Rate
• Punishment: +1 Success Rate

Add the following to the list of Progressions in the rule entitled Movement:

• Pilfer: Remove 1 Cheese from a Rat in the same position. This may only be carried out if the previous Progression has brought the acting Rat to a position occupied by another Rat, or if it if the first Progression in the action and there is already another Rat present.