Hi there, I’m new to this game. I’d like to play in this Dynasty.

...BUILDING SCHEMATICS FOR OPERATION TRIPSWITCH CONCEALED AT DEAD LETTER POINT SEVEN-NINE-FOUR…

Reword Rule 2.7, “Communications,” to read as follows:

As a weekly action, an Agent may send a message to any Agent who has a Codename by telephoning D-Ops with the subject line “ACTION: Message to CODENAMEA in SECTORA”, where CODENAMEA and SECTORA are the codename and sector of the intended recipient. If this information is valid, D-Ops should forward the message to the recipient Agent. If the information pertaining to the recipient is incorrect, the message is not forwarded to the recipient Agent, and D-Ops shall respond to the sending Agent indicating as much, but the Interception conditions still apply.

As a weekly action, an Agent may send a message to any Agent who has a Codename by telephoning D-Ops with the subject line “ACTION: Message from CODENAMEA in SECTORA to CODENAMEB”, where CODENAMEA is the Codename of an Imposter, SECTORA is Sector in which that Imposter is located, and CODENAMEB is the Codename of the intended recipient. If the information pertaining to the Imposter is incorrect, the message is not forwarded to the recipient Agent, and D-Ops shall respond to the sending Agent indicating as much, but the Interception conditions still apply.

...OZZOZOZOOZOZZZZOZZOOOZZOOZOOOZZOOZZOOZZOZZZOOZZOOZOOOZZOZOZOOZZOZOZOZOZO-
OZZZOZZOZOZOOZZOOOOZOZZOOZZOOZZOZZOOOZZOOZOOZZZOZZOZOZZOOZZOOOZOOZZOZZZO-
OOZOZZZOZOZOZZZOZZZOOZZOOZOOZZZOZOOOZZZOOZZOZOZOZOOOOZZOZOOZZOZOOZZOZZZO-
OOOOZZZOZOZOZZZOZZZOOZZOOZOOZZZOZOOOOZZOZZZZOZZOOZOOZZZOZOZOOZZOOOZOZZZO-
ZZZOOOZOZOZOOZZOOZZZOZZOOZZOZZZOZOOOOZZOOZZOOOZOZZZOOZZOOZZZOZZOZZZOOZZO-
OZZOZZZOOZOOOZZOZOOOOZZO…

...OPERATION GRIFFON CLEARED FOR STAGE FOUR…

In the Rule “List of Objectives”, change the text

D-Ops shall post the Name, Codename and Location of the Agent performing the Objective to the weblog.

to

D-Ops shall post the Name, Codename and Location of the Agent performing the Objective to the weblog.  Additionally, if the TARGET word was the Codename of another Agent with the same Allegience, the Agent performing the Objective is Decommissioned, with D-Ops posting a blog entry to this effect.

Enact a new rule, “The Signal”:-

D-Ops may trigger a Signal at any time with 48 hours of this rule being added to the ruleset. Upon doing so, he shall inform each Agent of the Codenames of any Impostors they share a District with. After this has happened, each Impostor will be relocated to a random District. After that, this rule shall be repealed.

...ATTN INTERCEPTOR THIS IS STATION RAIDER BLACKMAIL ATTEMPTS ARE UNWISE AS I HOLD EQUALLY DAMNING INFORMATION ON YOU…

Strike the item “All Agents in the list have the same Allegiance” from the requirements in Rule 2.8, “Final Report.”

In the same rule, change “The list contains at least three Codenames” to “The list contains at least four Codenames.”

...VHHNLQJXVDJHQW LZDQWWRGHIHFW SOHDVHUHVSRQGLQWKHUHYHUVHRIWKLVFBSKHU…

...ATTENTION STATION RAIDER I HAVE COME INTO POSSESSION OF YOUR IDENTITY IT IS WITHIN MY POWER TO MAKE THESE DETAILS KNOWN IT WOULD BE UNWISE TO CONTINUE ON YOUR CURRENT COURSE I WILL CONTINUE MONITORING THE SITUATION…

In the Rule “List of Objectives”, change the text

If all of the following conditions are met for a Final Report, then that Report is Confirmed:-

* The list contains at least three Codenames.
* Every Codename is paired with the name of the Agent who has that Codename.
* All Agents in the list have the same Allegiance.
* The Caller does not have the same Allegiance as any of the listed Agents.

to

If all of the following conditions are met for a Final Report, then that Report is Confirmed:-

* Every Codename is paired with the name of the Agent who has that Codename.
* All Agents in the list have the same Allegiance.
* The Caller does not have the same Allegiance as any of the listed Agents.
* The list contains at least three Codenames, or contains every Agent with the same Allegiance as the first Agent on the list.

Per this proposal, you all read in this morning’s Neues Deutschland that there are currently three Soviet Agents, two US Agents and four Independent Agents active in the Berlin theatre.

...OPERATION ANVIL TO PROCEED AS ARRANGED…

...TOSTF LCTOS TFLCW EYFSL MAMIY TQRLS KFTTF LCRLY KOSSR COS…

In the list in Rule 2.8, replace “All Agents in the list have the same Allegiance.” with:-

All Agents in the list have the same Allegiance, and the listed Agents are the only Agents to hold this Allegiance.

In Rule 2.3.1, replace “D-Ops will respond with a list of all of their Codenames” with:-

D-Ops will respond with a list of all of their Codenames and Nationalities

Add a Specialty to Rule 2.9 (Specialties):-

Plant. If a Plant appears on a Surveillance list, then the recipient of the list is given a disguised Nationality for that Plant, depending on the Sector in which the Plant is located. If they are in the US sector, their Nationality is given as American; if in the French sector, as French; if in the British sector, as British; and if in the Soviet sector, as Russian.

...ALERT FOR OPERATION COPERNICUS. NIGHT GUARD COULD NOT BE REPLACED. PROCEED WITH CAUTION…

In the objective “Station Raid”, change

D-Ops shall select a random Agent whose Allegiance matches the Allegiance of the raided Station (if any exist), and send both their name and Codename to the raiding Agent.

to

D-Ops shall select a random Agent whose Allegiance matches the Allegiance of the raided Station (if any exist), and send their Codename to the raiding Agent.

...THE BLACK GOOSE HAS FLOWN THE NEST, OPERATION ICEPICK BEGINS TONIGHT…

Add to 2.9 Specialties.

Rhetoric: Instead of walking and once a day, a Rhetoric may attempt to talk to an agent (which will be defined as “Target-Agent”) in their Location by telephoning the Director with Target-Agents Codename, in an email with the subject line “CODENAMEA talks to CODENAMEB”, where “CODENAMEA” is the Agent’s Codename, and “CODENAMEB” is the Target-Agent’s Codename. As soon as the D-Ops can, he will reply to this email with the subject line: “CODENAMEB is X”, where there is a:

40% chance that X is the afiliation of Target-Agent (in the format “afiliated to Y”, where Y is an afiliation)

30% chance that X will be ” an IMPOSTOR” if Target-Agent is an Impostor and “NOT an IMPOSTOR” if Target-Agent is not an impostor

30% chance that X is “an AGENT”.

If the Target-Agent isn’t in the same location as the agent, X is “SOMEWHERE THAT IS NOT THIS LOCATION”. This overrules any other possible values X can take.

Add to 2.9 Specialties.

Rhetoric: Instead of walking and once a day, a Rhetoric may talk to someone in their Location by telephoning the Director with their objectives Codename, in an email with the subject line “CODENAMEA talks to CODENAMEB”, where “CODENAMEA” is the Agent’s Codename, and “CODENAMEB” is the objective’s Codename. As soon as the D-Ops can, he will reply to this email with the subject line: “CODENAMEB is X”, where there is an 40% chance that X is the afiliation of that agent (in the format “afiliated to Y”, where Y is an afiliation), an 30% chance that it will be ” an IMPOSTOR” if the objective is an Impostor and “NOT an IMPOSTOR” if the objective is not an impostor. In the remaining percentage, X is “an AGENT”. If the objective isn’t in the same location as the agent, X is “SOMEWHERE THAT IS NOT THIS LOCATION”.

As soon as possible after the enactment of this proposal, D-Ops should create a post containing the following information:
-The number of agents whose Allegiance is US
-The number of agents whose Allegiance is Soviet
-The number of agents whose Allegiance is Independent

According to “The Director of Operations may be Telephoned by emailing .(JavaScript must be enabled to view this email address). The Director of Operations may also be referred to as “D-Ops” in rule 2.1

Replace in Rule 2.3 “Any Agent who does not have a Codename may Telephone the Director of Operations to request an identity.” with

Any Agent who does not have a Codename may make a telephone call to the D-Ops through the use of the Red Phone to request an identity.

This is Ujalu, requesting permission to go active.

In Rule 2.9, replace “Every Agent with a Codename has a Specialty, which is tracked in the GNDT. When an Agent is assigned a Codename, that Agent’s Specialty is set to Generalist.” with:-

Every Agent has a Specialty and a Clue, which are tracked in the GNDT. An Agent’s Specialty starts as Generalist, and their Clue starts as blank.

Replace “A Generalist may change Specialties at any time, without making a Story Post.” with:-

A Generalist who has a Codename may change their Specialty at any time, without updating their Clue.

Replace the final paragraph with:-

As a daily action, any Agent who has a Codename may change their Specialty by updating their Specialty in the GNDT and adding one letter of their Codename to their Clue. An Agent may add the same letter to their Clue multiple times, but only as many times as that letter actually appears in their Codename. If an Agent has already revealed all the letters of their Codename in this way, they may continue to change Specialties as a daily action without updating their Clue.

Lilomar and Sysiphus both idle out after a week of inactivity. Quorum drops to six.

...KJJOB5KAXDGWHTQHVOZRHJOEAELVXNIRPNGKPSNHYOAIGKKSOWWPKWSDPRV…

Add to the list of specialties:

Code Breaker. Whenever a message is sent, there is a 50% chance that its content is forwarded to all Code Breakers who share a Sector with the sender.

Move the last paragraph of rule 2.2.2 to rule 2.2.3, then delete rule 2.2.2.

Append the following to the list of Specialties in Rule 2.9:

• Inquisitor.  When an Inquisitor performs Surveillance, the D-Ops shall indicate which, if any, Codenames they discover at that time belong to Imposters.  The D-Ops shall then move any such Imposters to a new random Location as soon as it is legal to do so.
• Shoemaker.  When changing Specialties to Shoemaker, an Agent may set their Specialty in the GNDT to any other Specialty, and may list the same new Specialty in their Story Post if necessary; however, they must privately telephone D-Ops at the time of the change to record that their true Specialty is Shoemaker, and they are not legally considered to have any other Specialty.  When attempting to complete an Objective, a Shoemaker is treated as though they had whatever Allegiance is most advantageous for completion.

...EQUIPMENT AND ALIBI APPROVED FOR OPERATION BLACKJACK…

To Rule 2.8 (Surveillance Report), add:-

If a submitted Surveillance Report includes the Codename of an Impostor in its list of Codenames, the Agent who submitted it is Decommissioned, with D-Ops posting a blog entry to this effect. A Decommissioned Agent may not submit any further Surveillance Reports.

After “that Agent has achieved victory.” add:-

If D-Ops receives a Surveillance Report which is not valid, he must respond to the Agent who submitted it, telling them this.

In Rule 2.8 (Surveillance Report), replace “Surveillance” with “Final” and “valid” with “confirmed”.

In Rule 2.4 (Berlin 1946), after “Each Agent’s Location starts as Unknown.”, add:-

If an Agent’s Location has been Unknown for more than seven days, D-Ops may move the Agent to a random District, email the Agent to inform them of this and update the Agent’s Last Known Location to that District (prefixing it with an asterisk as if the Agent had updated it themselves).

To the bulleted list in Rule 2.9 (Specialties), add:-

Sandbagger. A Sandbagger ignores the restriction of only being assignable to a single Operation at a given time. If three Agents are Sandbaggers, further Agents cannot become Sandbaggers.

In Rule 2.5 (Objectives), replace “ignoring those who have been assigned the Objective since last requesting it” with:-

ignoring those who have been assigned the Objective since last requesting it, or who could not be assigned to the Operation

...SECURITY SYSTEMS DISABLED FOR OPERATION SKYLIGHT…

Create a new rule, “Specialties,” with the following text:

Every Agent with a Codename has a Specialty, which is tracked in the GNDT.  When an Agent is assigned a Codename, that Agent’s Specialty is set to Generalist.

The Specialties an Agent may have are as follows:

• Generalist.  A Generalist may change Specialties at any time, without making a Story Post.
• Lamplighter.  A Lamplighter may send messages as per “Communications” as a daily action rather than a weekly action.
• Pavement Artist.  As a weekly action, an Pavement Artist may Skulk to a new Location by telephoning the Director with their new Location, in an email with the subject line “CODENAME skulks to LOCATION”, where “CODENAME” is the Agent’s Codename, and “LOCATION” is their intended Location. If valid, the Location change is considered to occur as soon as the email reaches D-Ops.  A Pavement Artist may not both Skulk and Walk within a six-hour period.
• Scalphunter.  When attempting to Intercept another Agent on an Operation, a Scalphunter may use a Codename in place of that Agent’s name.  If the Interception is successful, the Scalphunter is then informed of the Agent’s name rather than their Codename.
• Burrower.  A Burrower may, as a daily action, perform Surveillance even if they have already done so in their current location.

As a daily action, any Agent may change Specialties by updating their Specialty in the GNDT and making a Story Post in which they announce this change and reveal one letter of their own Codename.  No agent may make a Story Post purporting to reveal a letter of their Codename unless that letter is in fact in their Codename.  An Agent may reveal the same letter in multiple Story Posts, but only as many times as that letter actually appears in their Codename.  If an Agent has already revealed all the letters of their Codename in this way, they may continue to change Specialties as a daily action without making further Story Posts.

Upon enacting this proposal, create a new column, Specialty, in the GNDT, and set every active Agent’s Specialty to Generalist.

Agent Blacky has either gone into deep cover, or just hasn’t posted anything for seven days. Quorum drops to seven.

Add a new Objective to Rule 2.5.1 (List of Objectives):-

Assassination
Time: 7 days
Maximum number of Agents: 1
An Agent with this Objective may telephone D-Ops with the subject line “ASSASSINATE [TARGET]”, where [TARGET] is any word. If, at the time of telephoning, an Imposter has the TARGET word as their Codename, and shares a Location with the Agent performing the Objective, then the Objective is completed - the Imposter is Eliminated, and the Agent shall be given the Codename of every Agent who shares an Allegiance with the Imposter. Otherwise, this Objective is failed. If this Objective is failed for any reason, the assassin is arrested - D-Ops shall post the Name, Codename and Location of the Agent performing the Objective to the weblog.

To Rule 2.2.1 (Imposters), add:-

Imposters may become Eliminated. If an Imposter has been Eliminated, its Location is always Unknown and it no longer counts as an Imposter for any rule other than this one.

I’m going to need to go idle for a week or two.

...FKAB MBKA BKQX DBKQ FKHM PBBH FKDQ LGLF KXCX ZQFLK…

This is FuzzyLogic requesting permission to go active.

Create a new rule, “Specialties,” with the following text:

Any Agent with a Codename may have a Specialty, which is tracked in the GNDT.  If an Agent’s Codename is not listed, that Agent is considered a Generalist.

The Specialties an Agent may have are as follows:

Add the following to the end of the rule “Surveillance Report”

If an Agent does not have a Valid Surveillance Report, then D-Ops shall tell the Agent how many pairings between Codenames and Agents are wrong, without stating which pairs are wrong, if any and how many pairs share the Agent who made the Surveillance Report Allegiance, again without stating which pairs.

...XYBIX QBATB IZLJB QLYBO IFKXD BKQYR ZHVFP BBVLR GRPQJ FPPBA QLAXV PKBTP MXMBO…

Mosby requesting acceptance as an Agent.

Per this proposal, today’s newspaper includes a list of Agents and Imposters currently active in Berlin theatre. (Idle Agents are not listed.)

• AIGRETTE
• ALUDEL
• BROWBAND
• BUTCHERBIRD
• CANZONET
• GROGRAM
• HARUSPEX
• KALEYARD
• KVASS
• OLEASTER
• VAPORETTO
• WHITLOW
• YELLOWTAIL

In Rule 2.5 (Operations), replace “As a daily action, D-Ops may select a random Objective, and assign it as an Operation to the maximum number of Agents who may be assigned to it, selecting them at random.” with:-

An Agent may telephone D-Ops at any time to request assignation to a particular Objective, with a subject line of “OPERATION REQUEST” and the name of an Objective in its body. As a daily action, D-Ops may select an Objective, and assign it as a single Operation to one or more Agents who have previously requested assignation to that Objective (selecting such Agents at random, and ignoring those who have been assigned the Objective since last requesting it).

Add a new Objective to Rule 2.5.1:-

Station Raid
Time: 7 days
Maximum number of Agents: 1
An Agent with this Objective may telephone D-Ops with the subject line “RAID [DISTRICT]”, where [DISTRICT] is either Steglitz (US Station), Heliersdorf (Soviet Station) or Spandau (Independent Station). If, at the time of telephoning, both the Agent’s Location and Last Known Location match that District, then the Objective is completed - D-Ops shall select a random Agent whose Allegiance matches the Allegiance of the raided Station (if any exist), and send both their name and Codename to the raiding Agent. Otherwise, this Objective is failed.

As soon as possible after the enactment of this propoal, D-Ops should post a list of all Codenames in use by any Agent or Impostor.

...ROADBLOCK LIFTED FOR OPERATION DOLOMITE…

EvilToaster and Ienpw III both idle out.

12 Agents. Quorum is 7.

In Rule 2.3.1 (Surveillance), replace “requesting the contact” with “performing the surveillance”.

...LONELYSOVAGENTFROGPOLEINSECTORFRPLEASEMSG…

Add to the third paragraph of rule “Objectives”:

When an Operation is failed, D-Ops shall add the codenames of all Agents who were assigned to it to the GNDT (unless they were already present).

This is Sysiphus requesting activation as a player.

Rename Rule 2.3.1 (Contacts) to “Surveillance”, and reword it to:-

An Agent may, if they have not yet done so when they had their current Location, telephone D-Ops announcing their intention to perform surveillance. D-Ops should respond to this email. Responses by D-Ops shall be determined in the following manner:-

• If the Agent performing surveillance has a Location of “Unknown,” D-Ops will refuse and cite this reason.
• Otherwise, if there existed any Agents or Imposters with the same Location as the Agent requesting the contact, at the time the Surveillance was announced, D-Ops will respond with a list of all of their Codenames.
• If neither of the above are true, D-Ops will respond that there were no suspicious characters in the District.

Add a new subrule to Rule 2.5 (Objectives), called “Interception”:-

As a daily action, an Agent who has a Codename (the “Interceptor”) may Intercept another Agent by telephoning D-Ops with the subject line “INTERCEPT [AGENT] ON [OPERATION]” where “AGENT” is the name of an Agent, and “OPERATION” is the name of an Operation in the Dossier which has neither been completed nor failed.

If, at the time the email was sent, the named Agent (the “Target”) had been assigned to the named Operation, then the Operation is failed and the Interceptor is privately informed of the Target’s Codename. Otherwise, the Operation is unaffected, the Interceptor is privately informed of their failure, and the Target is privately informed of the Interceptor’s Codename (but not their name).

...OPERATION FOOTFALL COMMENCES AT ZERO EIGHT THIRTY HOURS, CODE GREEN…

...RSMDL LN BMHCM NORDQMD GSSMD CMDOD CM HSNMDQ ZTNXEH RSDFQ ZSXRZ DDJ ZLKKHV CM ZRDMN DUHS BZMH DGSD ANSXKDJ HKDQZ RS MDFZ S MDCM DODCMH…

In Rule 2.5, replace “An Agent may only be assigned to a single Objective at a given time. An Agent without an Objective may telephone D-Ops to request one, but D-Ops is not obliged to grant this request.” with:-

An Agent may only be assigned to a single Objective at a given time, and an Agent without a Codename cannot be assigned to an Objective. As a daily action, D-Ops may select a random Objective, and assign it as an Operation to the maximum number of Agents who may be assigned to it, selecting them at random.

In Rule 2.5.1, replace “14 days” with “7 days”.

In Rule 2.5, replace “and add it to The Dossier” with “and add it to The Dossier as an Operation”.

Replace “Objective” with “Operation” throughout Rule 2.5, except in the phrases “contains a list of Objectives”, “D-Ops may select an Objective”, “An objective must specify the time”, “D-Ops may select a random Objective” and “the limit specified in the Objective”.

Add a new rule, “Surveillance Report”:-

As a weekly action, an Agent who has a Codename (the ‘Caller’) may Telephone D-Ops with a Surveillance Report - a list of Codenames, each of them different, and each paired with the name of an Agent.

If all of the following conditions are met for a Surveillance Report, then that Report is Valid:-

• The list contains at least three Codenames.
• Every Codename is paired with the name of the Agent who has that Codename.
• All Agents in the list have the same Allegiance.
• The Caller does not have the same Allegiance as any of the listed Agents.

If D-Ops has received a valid Surveillance Report from an Agent, then D-Ops shall confirm this in a public blog post, and that Agent has achieved victory.

Remove “If an Agent has a Codename but no Allegiance, the D-Ops shall set their Allegiance to Independent. As a Weekly Action, an Agent may Telephone the Director of Ops and request a change of Allegiance. The D-Ops may effect this change at their discretion, and will notify the Agent when done.” from Rule 2.2, and enact a new subrule to Rule 2.2 (Allegiances):-

If an Agent has a Codename but no Allegiance, the D-Ops shall set their Allegiance to Independent.

As a weekly action, an Agent (the “Defector”) may Telephone D-Ops with the Codename of an Agent they believe has recruited them. When D-Ops reads this Telephone message: if an Agent has the specified Codename and is in the same Location as the Defector, then the Defector’s Allegiance is altered to match that of the Agent with the specified Codename. If the Defector’s Allegiance changes as a result of this, the Defector shall be informed of this fact (although they will not be told their new Allegiance). If it does not, the Defector shall be told that the Defection failed to occur.

...BPCDW IJIKL OROXJ DMRLM ERKBO XRNBF SIGZZ GPRWZ WGUSY PTVFV JOWEG XYPZR JWEZB UJRXE WYPWV TNHOM KPLFU EKPAN HIEEA VOXVC KRQXK SQFNI JDITF…111012509314513085119305211404318450551861921245422015033311227761100649-
0518207911450519927112530894…

After having received no contact from either Agent in a while, Amnistar and Anonyman are both missing and presumed dead.

Quorum is 8 with 14 Agents.

Add to rule “Numbers and Variables”:

* If a number or other game variable is selected ‘at random’ or ‘randomly’ from a range of possible values, its value shall always be taken from a uniform probability distribution over the entire range of possible values, unless otherwise specified.

If the Proposal titled “Pankow prison blues” failed, this Proposal does nothing.

Add a subrule to Codenames, named “Officers”:

There are two non-Agent entities, the Officers, who have an Allegiance US of and Soviet, respecively, and have a Codename, Description and Location as though they were Agents; however, their Descriptions are tracked privately by D-Ops. As a weekly Action, D-Ops may change the location of the US Officer to a random District in West-Berlin. As a weekly action, D-Ops may change the Location of the Soviet Officer to a random District in East-Berlin.

Add to rule Contacts:

For the purposes of this rule, the US Officer is treated as if they had Soviet Allegiance and vice versa. If an Agent of Independent Allegiance requests a Contact, there is a 1/3 probability that both Officers are treated as though they had an Independent Allegiance instead. If an Agent is sent the Codename of an Officer through this rule, they are sent to prison.

Also, in the same rule, change

Otherwise, if there exists at least one other Agent or Imposter with the same Allegiance and Location as the Agent requesting the contact, D-Ops will respond with one of their Codenames.

to

Otherwise, if there exists at least one other Agent, Imposter or Officer with the same Allegiance and Location as the Agent requesting the contact, D-Ops will respond with one of their Codenames, selected at random.

Add a new rule, “Imprisonment”:

There exist two locations known as Prisons, denoted by EBPRIS and WBPRIS. When an Agent is “Imprisoned” or “sent to prison”, their Location is set to EBPRIS if they are in East-Berlin, or WBPRIS otherwise, unless otherwise specified.

Imprisoned Agents may not change their Location.

Add to the first paragraph of Interceptions:

When a message is sent to or from a Prison,  there is a 30% chance that it is broadcast and a 70% chance that nothing happens.

Congratulations to Thane Q for decrypting my code! Apparently it was a pain, but you succeded. =)

Now, for the Archives in question: I have managed to recover the old BlogNomic, from the time it was hosted at blognomic.blogspot.com . The whole site can be browsed from the Archive EXCEPT for the index.html page, which didn’t convert for some reason. You can start from one of the other pages and browse from there, though. The comments, sadly, are beyond my ability to recover. If someone else has an idea, however, I would be glad to hear it.

The Archive is uploaded here: http://www.mediafire.com/?a1f7cw16cswkqcn

Oh, and the site is 114 MB, but I compressed it to 2.22 MB using 7-Zip. If you have problems with the decompression, perhaps using the latest 7-Zip Beta Build would help, as it’s the version I used. However, AFAIK, WinRar works.

Have fun! =D
~ Roujo

In Rule 2.4, replace “As a weekly action, an Agent who has a Codename may change their Location” with:-

As a weekly action, an Agent who has a Codename may Walk to a new Location

And replace “CODENAME moves to LOCATION” with:-

CODENAME walks to LOCATION

Replace “As a Daily Action, any Agent may do one but not both of the following” with:-

As a daily action, any Agent may take a Taxi to a new Location, and do one but not both of the following

And replace “must then Telephone the D-Ops” with:-

must then Telephone D-Ops in an email with the subject line “ACTION: CODENAME takes a taxi to LOCATION” (where “CODENAME” is the Agent’s Codename, and “LOCATION” is their new Location),

Also replace “An Agent may change their own Last Known Location if they wish, but such an update must be truthful and must be prefixed by an asterisk.” with:-

If an Agent updates their own Last Known Location, this update must be prefixed by an asterisk. An Agent may update their own Last Known Location at any time, but such an update must be truthful.

...OZZOZOOOOZZZOZOOOZZZOZOOOZZZOOOOOOZZZOZOOOZOZZZZOOZOZZZZOZZZOOOOOZZOO-
OOZOZZZOOZZOZZZOZOOOZZOOZOZOZZOOOZOOZZOZOOZOZZOZZZOOOZOZZZOOZZOOOZZOZZOZ-
ZZZOZZOZZOZOOZOZZZZOZOOOZZOOZZOZOZOOZOZOZOZOZZOZOOZOZZOZZZOOZOOZOZOOOZZO-
ZZZOZZZOOOO…AAABCACCBCBCABCCCBABCBCACBACABAACABAABCAAABABCCAAABACACBAC-
ACBCCAAABAACCCBACACBAAAAABAACBCCCCCBAAACCBABACABCAAABACCBAACABACCABCCCCB-
AAAAABCCAAABAACBAAAAABACACBAAACCBCAAAABACCCBAACBCCAAABAACCCBCAAABCACCBCC-
ABAACCCBACACBCCACBACACBAACCCBACCCCBCCABCAAABABACACBAAAAABACACBCCAAABAACC-
CBACCCCBCCABAACCCBCAAABCCABAACCCBACACBCCACBACACBAACCCBACCCCBCCABCAAABA…ASKJD HOUIQ WEMNB ZXCKA SDIOQ WMZXJ ASHHS ADHQW EUYIU DASDK KBZXG…

...QEEEZEEQEZEQQEZQEZEZQEQQZEEEQZQQEEZQEZEQEZEQQEZEEQZQEEEZQEZQEQQZEEEZQ-
EZEEQEZEEEQZEQEZEZEZQEZQQEZQEZEQZQZQEEEZEQEZEQQEZEEQZQEEEZEZQEEEZQQEEZEQ-
EZQEEEZEQQQZEEQZEEEQZEEQEZQEEQZEQEZEQEEZQEZQEQQZEEEZQEZEQZQEEEZEEZEQEZQQ-
EEZQQQZEQEZEZQQEZQEZEQZQZQEEEZEEQEZEEEQZEQEZEZEZQEZQQEZQEZEQZQZQEEEZQEEE-
ZEEQEZEQQEZQEZEZQQEEZEEEQZQEEQZEQEZEQEZEQQEZEEQZQEEEZQEZQEQQZEEEZQEZQQEZ-
QEZEQZQZQEEEZEQQEZEEQZQEZEZQEQQZEEEQZEQEZQEQQZEEEQZQQEEZQEZEQEZEQQEZEEQZ-
QEEEZEEZEEEQZEQQEZQQEZQEEEZEZEQEZEQQEZEEQZQEEEZEZQEEEZQQEEZEQEZQEEEZQEZQ-
EQQZEEEZQEZQZQEEEZQEQQZEEEZEQEZEQQEZEEQZQEEEZEQZQEEEZEEZEQEZQQEEZQQQZEQE-
ZEZQQEZQEZEQZQZQEEEZEEQEZEEEQZEQEZEZEZQEZEEQEZEEEQZEQEZEZEZQEZQQEZQEZEQZ-
QZQEEEZQEEEZEEQEZEQQEZQEZEZQEQEZQEZQEQEZQEZQEQEZQEZQEQEZQEZQEQQZEEEQZQQE-
EZQEZEQEZEQQEZEEQZQEEEZQEZQEQQZEEEZQEZEEQEZEEEQZEQEZEZEZQEZEQEZEQQEZEEQZ-
QEEEZEZQEEEZQQEEZEQEZQEEEZEQEZEQQEZEEQZQEEEZEEQEZEEEQZEQEZEZEZQEZQEQEZQE-
ZQEQEZQEZQEEEZEEQEZEQQEZQEZEZEQZQEEEZEEZEQEZQQEEZQQQZEQEZEZQQEQZEQEZQEQQ-
ZQQEZQEZEEQEZEEEQZEQEZEZEZQEZQQEZQEZEQZQZQEEEZQEEEZEEQEZEQQEZQEZEZQEQEZQ-
EZQEQEZQE…WRRWYGJLCRQCLGJRQDG1059MHYSXSLOSAWMWQLPUTLHGTQJCLTUOLQSJC…

Move the second and third paragraphs of the rule entitled “Communications” into a new subrule of “Communications,” entitled “Interception.”

In the first paragraph of the rule entitled “Communications,” replace the text “but the following still applies.” with:

but the Interception conditions still apply.

Insert the following after the first paragraph of the rule entitled “Communications:”

As a weekly action, an Agent may send a message to another Agent who has a Codename by telephoning D-Ops with the subject line “ACTION: CODENAMEA in SECTORA sending a message to CODENAMEB in SECTORB”, where CODENAMEA is the Codename of an Imposter, SECTORA is Sector in which that Imposter is located, and CODENAMEB and SECTORB are the Codename and Sector of the intended recipient. If this information is valid, D-Ops should forward the message to the recipient Agent. If the information pertaining to the recipient is incorrect, the message is not forwarded to the recipient Agent, but the Interception conditions still apply.

...000X111X010X010X1011XXX000X011X00X1X1010X0000XXX1010X00X0110X0000X0X0-
10X000XXX1000X001X1XXX0010X00X010X000X1XXX1010X111X100X0XXX0000X01X000XX-
X1000X0X0X10XXX1010X111X11X0110X010X111X11X00X1100X0X100XXX000X1X111X011-
0XXX1000X010X111X01X100X1010X01X000X1XXX01X0100X0100X0X110X00X01X10X1010-
X0XXX0010X01X10X100XXX01X011X01X00X1XXX0010X001X010X1X0000X0X010XXX1010X-
111X10X1X01X1010X1XXX000X1X111X0110XXX1011X111X001XXX11X01X1011XXX011X00-
X000X0000XXX1X111XXX001X000X0XXX01XXX1010X00X0110X0000X0X010XXX01X000XXX-
011X0X0100X0100XXX01X000XXX11X111X010X000X0XXX000X1X111X0110XXX110X111X1-
11X100XXX0100X001X1010X101XXX000X1X111X0110…

In Rule 2.4 (Berlin 1946), replace “An Agent may change their own Last Known Location if they wish, but such an update must be truthful.” with:-

An Agent may change their own Last Known Location if they wish, but such an update must be truthful and must be prefixed by an asterisk.

Reword Rule 2.6 (Radio Transmissions) to:-

Various rules create Radio Transmissions, which are either Queued or Archived. If any Radio Transmissions are Queued, D-Ops may make a post with the title “Radio Transmissions”, and a body composed of any number of Queued Transmissions in the order they were created, separated by ellipses. D-Ops may insert hyphens and remove spaces at his discretion. (Upon doing so, all Radio Transmissions become Archived.)

An Agent may make a Broadcast by telephoning D-Ops in an e-mail with the subject line “Radio Transmission”. The e-mail’s body must contain the message that the Agent wishes to broadcast, which must be a string of spaces, numbers and/or upper-case letters with a length of 30 or more. When D-Ops receives such an email, a Queued Radio Transmission is created with the email’s body as its content.

In Rule 2.5, replace “D-Ops must assign it to a positive amount of Agents equal or lower to the limit specified in the Objective” with:-

D-Ops must assign it to a positive amount of Agents equal or lower to the limit specified in the Objective, and give it an Operation Name

In Rule 2.5, replace “When D-Ops creates one or more Objectives, he should make a Story Post to inform all Agents of this action.” with:-

When D-Ops creates one or more Objectives, he should also create a Radio Transmission which includes the Objective’s Operation Name.

In Rule 2.7, replace “If a message is broadcast, it has been intercepted by a local newspaper, and D-Ops shall make a post with the message in its body.” with:-

If a message is broadcast, it has been intercepted by a local radio station, and a Radio Transmission is created of the message (including all spacing and formatting, and surrounding by quotation marks).

...GIDRANTXNAZNACHENXTSELIXIXPROSITXVSTRETITSYAXSOYUZNIKOVXAGENTAXVXWUSS-
CXVOXVTORNIK…001X10XXX011X00X0100X0100X00X10X110XXX1X111XXX0110X111X00-
0X1XXX11X0010XXX1010X111X100X0X10X01X11X0XXX0000X0X010X0XXX000X1X111X011-
0XXX110X00X0001X0XXX11X0XXX0010X111X001X010XXX000X0X1010X1X111X010XXX000-
X1X111X0110X…72796466666HB66647A7871727A6C76787A717A6B6BH6F6B66647A787-
8716F6F6A6C6F66666B6B6B7876627A677072656466H617A67786C707066667472687466-
76706B73626B6H2656466617A6C7066756B7666H666B6B67716B70756B76786B66H647A7-
8…EMOCLEWLLAEILONEKACNAMREGHTIWGNIDDEWHCNERF…12JZKPYZNDASGZFKCDPGMQI-
CHBBZHZGNDWRDOHZRRAJZMJEIVWNOLEILPXBK…

If the Proposal titled “Puh puh puh puh puh puh, puh puh pok-uh face” passed, change all instances of the word “Dossier” in the rule that it created to “Portfolio,” and change all instances of the word “secret” or “secrets” in that rule to “file” or “files”.

An Objective has been assigned and added to the Dossier.

Add a new rule to the ruleset, entitled Dodgy Dossiers:

Each Agent has a Dossier in which they keep their secrets. A Dossier has room for no more than five secrets; if an Agent already has five secrets and acquires another then they must discard an existing secret if they wish to keep it. Dossiers are tracked privately by Agents but D-Ops must be informed of any changes to the composition of an Agent’s Dossier as soon as that change occurs. (D-Ops is not required to track each Agent’s Dossier but must keep an audit trail of changes for later validation if necessary.)

Secrets fall into eight categories, which are denoted by the colour of the binder in which they are kept (Red, Green, Blue, Yellow, Purple, Orange, Black and White, from most to least valuable in that order) and are allocated a clearance level between 1 and 20, with 20 being the most restrictive level. There is exactly one secret at each clearance level in each category, meaning that there are exactly 160 secrets available.

Secrets tend to be grouped thematically, and thus a Dossier of secrets is more valuable in centrain configurations than in others.

* Sequence. Secrets of consecutive clearance levels within the same category (a “sequence”, e.g. Red 5,6,7,8) are the most valuable. At least three secrets are required to make a sequence. Sequences containing a higher quantity of secrets are more valuable than those with less. In sequences with the same quantity of secrets, value is determined primarily by category; thereafter, sequences starting at higher clearance levels are more valuable.
* Group. Secrets of the same clearance level across several categories (a “group”, eg. Red 10, Blue 10, Orange 10) are the next most valuable. At least three secrets are required to make a group. Groups containing a higher quantity of secrets are more valuable than those with less. In groups with the same quantity of secrets, value is determined primarily by category; thereafter, groups starting at higher clearance levels are more valuable.
* Cluster. Less valuable than a group is a cluster, which is a collection of secrets from the same category but of non-consecutive values (e.g. a blue 3, 5 and 17). At least three secrets are required to make a cluster. Clusters containing a higher quantity of secrets are more valuable than those with less. In clusters with the same quantity of secrets, value is determined primarily by category; thereafter, clusters with a higher total when the clearance levels are added are more valuable. If this still results in a tie, the cluster with the secret with the highest individual clearance level is the most valuable.
* Scatter. Less valuable than a cluster is a scatter, which is three secrets of consecutive values across a variety of categories (e.g. blue 8, green 9, black 10). Two or more secrets may be a scatter. The value of a scatter is primarily determined by the cumulative total of the clearance levels of the secrets involved, with higher being more valuable. If this results in a tie, the scatter which contains the secret of the most valuable category wins; thereafter, the scatter with the highest individual clearance within the most valuable category is the most valuable.
* Overview. If an Agent cannot make any of the above configurations then they Dossier is considered to be an overview. An overview is less valuable than all other configurations. The value of an overview is determined in the same way as the value of a Scatter.

At a time of their chosing, D-Ops may make a story post entitled “Operational Review”, which should contain a date no later than one month after the date of that posting. Whoever has the most valuable Dossier on that date has achieved victory.

...FLOATINGINRIVERELZBACHPLEASELEAVEUNDERWATERGEARINSHADEANDTHEWILLOWUNDERS-
ECRETSANDCASTLE…100X001X000X1X1010X0100X111X1X0000XXX011X00X000X0000X0-
X000XXX1X111XXX1010X111X11X11X001X10X00X1010X01X1X0XXX011X00X1X0000XXX10-
10X0100X0X0001X0X010XXX01X110X0X10X1X000XXX000X1X111X0110XXX010X0X000X01-
10X111X10X100XXX00X10XXX101X00X10X100XXX000X1X111X0110XXX010X0X000X0110X-
111X10X100XXX011X00X1X0000XXX1010X111X100X0X10X01X11X0XXX01X10X100XXX000-
X0X1010X1X111X010XXX000X1X111X0110XXX010X0X000X0110X111X10X100XXX01X000X-
01X0110XXX000X1X111X0110X…

In rule Contacts, change

if they have not yet done so when they had their current Location

to

as a weekly action

Add the following to the list of objectives:

:Find local office
:Time: 14 days
:Maximum number of Agents: 3
:This Objective must be assigned to exactly three Agents, all three of which must have the same Allegiance. When this Objective is assigned, D-Ops must pick a Location, and privately send the Area of that location to one Agent, the first letter of the district code to the second Agent, and the second letter of the district code to the third. He shall not inform the assigned Agents of each other’s identities, and shall not tell either Agent with a district letter which position their letter holds. If all three of the assigned Agents simultaneously hold the correct location for more than 24 hours, and no more than 2 other Agents also hold that location for the same duration, the Objective succeeds, and D-Ops shall privately inform the assigned Agents of each other’s Codenames, as well as the Codename of one Imposter (listed seperately). If at least three Agents not assigned to this objective simultaneously hold the correct location for more than 24 hours, this Objective fails, and the Codename of a randomly chosen Agent who was assigned to this objective will be made public in a post. If at least two of the assigned Agents hold the correct location when this Objective expires, D-Ops shall privately inform them of each other’s Codenames.

To rule 1.5 append

If one part of an enacted proposal relies on the gamestate existing in a certain state to have effect, and the gamestate does not exist as required by that part of the proposal, then that part of the proposal has no effect, but the rest of the proposal takes effects as it normally would.

Add the following before the last paragraph of the rule called “Berlin 1946.”

As a Daily Action, any Agent may do one but not both of the following:

• Move to another Location within their current Area, and then truthfully update their own Last Known Location field in the GNDT to reflect this.  They must then Telephone the D-Ops to inform them of their new Location.
• Truthfully update their own Last Known Location field in the GNDT to their current Location, and then move to another Location within their current Sector.  They must then Telephone the D-Ops to inform them of their new Location.

Add the following before the last paragraph of the rule called “Berlin 1946.”

As a Daily Action, any Agent may do one but not both of the following:

• Move to another Location within their current Area, and then truthfully update their own Last Known Location field in the GNDT to reflect this.  They must then Telephone the D-Ops to inform them of their new Location.
• Truthfully update their own Last Known Location field in the GNDT to their current Location, and then move to another Location within their current Sector.  They must then Telephone the D-Ops to inform them of their new Location.

In Rule 2.2.1 (Impostors), replace “the Imposters, who have a Codename, Description and Allegiance” with:-

the Imposters, who have a Codename, Description, Location and Allegiance

And add:-

As a weekly Action, D-Ops may - for each Imposter - change that Imposter’s Location to a random District.

In Rule 2.6 (Radio Transmissions), replace “separated by ellipses” with:-

separated by ellipses, and broken with hyphens at the discretion of D-Ops

Add the following before the last paragraph of the rule called “Berlin 1946.”

As a Daily Action, any Agent may move to another Location within their current Area, and must truthfully update their own Last Known Location field in the GNDT to reflect this.  They must then Telephone the D-Ops to inform them of their new Location.

As a Daily Action, any Agent may truthfully update their own Last Known Location field in the GNDT to their current Location, and then move to another Location within their current Sector.  They must then Telephone the D-Ops to inform them of their new Location.

Add a new subrule to Rule 2.2.  Call it “Hints” and give it the following text:

A Hint about an Agent or Impostor consists of both of the following:
*A range of four consecutive legal Heights, one of which is truthful
*A Cover Job and a Nationality, at least one of which is true.

For example, “A French Tourist between 5’4” and 5’7” ” would be a valid Hint concerning an Agent whose Description is ” 5’5” French Diplomat”

Whenever the Rules call on D-Ops to generate a Hint, he should give truthful Cover Jobs and truthful Nationalities with approximately equal probabilities.

If the Proposal titled “Is this a secure line?” passed, revert its effects.

Create a new rule, “Communications”:

As a weekly action, an Agent who has a Codename may send a message to another Agent who has a Codename by telephoning D-Ops with the subject line “ACTION: CODENAMEA in SECTORA sending a message to CODENAMEB in SECTORB”, where CODENAMEA is their codename, SECTORA is their sector, and CODENAMEB and SECTORB are the codename and sector of the intended recipient. If this information is valid, D-Ops should forward the message to the recipient Agent. If the information pertaining to the recipient is incorrect, the message is not forwarded to the recipient Agent, but the following still applies.

When a message is sent within one Sector, there is a 5% chance that it is intercepted, and a 95% chance that nothing happens..
When a message is sent between two Sectors, there is a 10% chance that it is intercepted, a 5% chance that it is broadcast, and a 85% chance that nothing happens.
When a message is sent between East- and West-Berlin, instead there is a 20% chance that it is intercepted, a 10% chance that it is broadcast and a 70% chance that nothing happens.

If a message is intercepted, D-Ops shall also forward it to a randomly chosen Agent in SECTORA or SECTORB apart from the sender or recipient. If a message is broadcast, it has been intercepted by a local newspaper, and D-Ops shall make a post with the message in its body. Whenever a message is posted or sent to an Agent, all information in the original subject line shall be omitted.

Create a new rule entitled ‘Communications’, containing the following:

As a weekly action, an Agent who has a Codename may send a message to another Agent who has a Codename by telephoning D-Ops with the subject line “ACTION: CODENAME sending a message to CODENAME” where the first “CODENAME” is the Codename of the Agent sending the message, and the second “CODENAME” is the intended recipient. If valid, the D-Ops should forward the message alone to the recipient Agent.

The D-Ops may forward the message, with the Codename of either the sender or recipient, to any other single Agent.

If the Proposal “Making a connection.” fails, this Proposal does nothing.

Reword the rule entitled “Contacts” to the following:

An Agent may, if they have not yet done so when they had their current Location, telephone D-Ops requesting a contact. D-Ops should respond to this email.  Responses by D-Ops shall be determined in the following manner:

• If the Agent requesting a contact has a Location of “Unknown,” D-Ops will refuse and cite this reason.
• Otherwise, if there exists at least one other Agent or Imposter with the same Allegiance and Location as the Agent requesting the contact, D-Ops will respond with one of their Codenames.
• If neither of the above are true, D-Ops will respond that there are no contacts available.

If D-Ops does give the requesting Agent a contact, D-Ops will also inform the contact that they have been so assigned, and send them the Codename of the requesting Agent.

SANFURDHATHEWKWRCOOULMMUDLINICKETATIOCOONMOPEUSTRATUSEEWICIPTHCHERLEV4FRERAOMAGENG2KTSLEEPIKETHIYOUSQUALLIET

AMERICANJOURNALISTCONVENTIONINKNEUZBERGPLEASEATTEND

Rewrite the rule “Objectives” to the following:

There exists a wiki document known as The Dossier, which contains a list of Objectives. At any time, D-Ops may select an Objective from a subrule to this rule and add it to The Dossier.

An objective must specify the time in which it must be completed, the number of Agents that may be assigned to it and the conditions that must be met to complete it, and may include one or more conditions for failure. When an Objective is added to the Dossier, D-Ops must assign it to a positive amount of Agents equal or lower to the limit specified in the Objective. When he does so, he shall privately inform the Agent(s) of their Objective, and shall mark upon the wiki document how many Agents are assigned to the Objective. When D-Ops creates one or more Objectives, he should make a Story Post to inform all Agents of this action.

If an Objective is not completed in its alloted time, it is failed. When an Objective is completed or failed, it shall be marked as such in the Dossier, and all assignments to it are removed.

An Agent may only be assigned to a single Objective at a given time. An Agent without an Objective may telephone D-Ops to request one, but D-Ops is not obliged to grant this request.

Add a subrule to that rule, “List of Objectives”:

The Objectives that D-Ops may create are listed below:

:’‘'Meet fellow operative’‘’
:Time: 14 days
:Maximum number of Agents: 1
:An Agent with this Objective may telephone D-Ops with the subject line “MEET [AGENT]”, where [AGENT] is the name of another Agent. If, at the time of telephoning, both agents share a Location and Allegiance, this Objective is completed, and both Agents are informed of each other’s Codenames. If both Agents share a Location but not an Allegiance, this Objective is failed, and D-Ops shall privately inform [AGENT] of the codename of the Agent who had this Objective. Otherwise, this Objective is failed.

In the rule “Radio Transmissions”, replace “Upon receiving this request, D-Ops should, at their earliest convenience, make a post with the title “Radio Transmission #{N}”, where {N} is the chronological number of the posted transmission (ordered by the dates of posting), and the broadcasted message in its body.” in it with:-

If D-Ops has any unprocessed emails of this nature, he may make a post with the title “Radio Transmissions”, and a body composed of messages from any number of these emails in the order they were received, separated by ellipses. (Upon doing so, those emails are considered processed.)

Create a subrule to “Briefing”: “Contacts”, with the text:

An Agent may, if they have not yet done so when they had their current Location, telephone D-Ops requesting a contact. D-Ops should respond to this email.
Responses by D-Ops must be determined in the following manner:
If there are Agents or Impostors with a different Allegiance than the Agent requesting the contact, with the same Location as them, then there is a one in four chance that the response is one of their codenames.
Otherwise, the response is the codename of an Agent or Impostor with the same Allegiance and the same Location as the Agent requesting the contact, or “None” if no such Agent or Impostor exists.

Add a new subrule to the Rule entitled “Dossier”.  Call it “Hints” and give it the following text:

A Hint about an Agent or Impostor consists of both of the following:
*A range of four consecutive legal Heights, one of which is truthful
*A Cover Job and a Nationality, at least one of which is true.

For example, “A French Tourist between 5’4” and 5’7” ” would be a valid Hint concerning an Agent whose Description is ” 5’5” French Diplomat”

Whenever the Rules call on D-Ops to generate a Hint, he should give truthful Cover Jobs and truthful Nationalities with roughly equal probabilities.

Add a new subrule to the Rule entitled “Berlin 1946”.  Call it “Border Checkpoints” and give it the following text:

From time to time, but at least once each week, D-Ops shall publish a report to the blog whose title contains “Border Report”.  For each instance where an Agent changed their Location to one in a different Area since the last such report, that report shall contain the departure and destination Areas of that location change coupled with a Hint about that Agent.  For each Impostor, the report may also include departure and destination Areas and a Hint for that Impostor; the movements of Impostors in these reports should be consistent with older reports.

Rename rule 2.2 to “Codenames”.

Add a new rule, “Radio Transmissions”:

An Agent may broadcast a Radio Transmission by telephoning D-Ops in an e-mail with the subject line “Radio Transmission”. The e-mail’s body must contain the message that the Agent wishes to broadcast, which must be an unspaced string of numbers and/or upper-case letters with a length of 30 or more. Upon receiving this request, D-Ops should, at their earliest convenience, make a post with the title “Radio Transmission #{N}”, where {N} is the chronological number of the posted transmission (ordered by the dates of posting), and the broadcasted message in its body.

Could someone idle me, please?

Reword Rule 2.4 (Berlin 1946) to:-

A map of Berlin can be found at [[Berlin map]], divided into Areas, Sectors and Districts. This page may only be edited by D-Ops.

Each Agent has a Location, which is either a District on the map, or Unknown. Each Agent’s Location starts as Unknown.

Locations are notated as five-letter strings. The first letter of the string refers to which side of Berlin the Agent is in; the second and third letters refer to the sector occupied by the Agent; and the fourth and fifth letters refer to the district. A complete key to location information can be found at the same page as the map, linked to above. An Unknown Location is notated as “XXXXX”.

As a weekly action, an Agent who has a Codename may change their Location by telephoning the Director with their new Location, in an email with the subject line “ACTION: CODENAME moves to LOCATION”, where “CODENAME” is the Agent’s Codename, and “LOCATION” is their intended Location. If valid, the Location change is considered to occur as soon as the email reaches D-Ops.

Each Agent’s Last Known Location is tracked in the GNDT. This must consist of a valid Location (other than Unknown) and of a date at which it was believed to be true. Any Agent may update this at any time. An Agent may change their own Last Known Location if they wish, but such an update must be truthful.

If the Proposal titled “But This is Only Half the List” passed, remove the subrule entitled “Codename Tracking”.

Add a new rule entitled Codename: Gamestate:

For the purposes of the Eighth Dynasty of Kevan, the GNDT tracks only Codenames. Any rule that described data that should be ascribed to an Agent in the GNDT is instead ascribed to their Codename. Any Agent without a Codename may request one as per. rule 2.3; Agents without Codenames may not have values for any data usually tracked in the GNDT.

This rule may be removed by any Agent whenever a Declaration of Victory passes.

The GNDT may track up to twenty additional unassigned Codenames at any given time. Tracked unassigned Codenames may be assigned to new or unidling players. D-Ops may add or remove unassigned Codenames as needed.

D-Ops should make the necessary changes to the GNDT at the earliest opportunity, or may optionally set up an alternative GNDT for the purposes of this dynasty. Any Agent who already has a Description in the GNDT loses it and must request another from D-Ops.

In Rule 1.9, “Victory and Ascension,” replace this text:

The Hiatus continues until the new Director of Operations posts an Ascension Address to the BlogNomic weblog - this shall specify the Director of Operations’s chosen theme for the new Dynasty, and may optionally include a proclamation that any number of Dynastic Rules will be repealed, and/or that the words Agent and Director of Operations will be replaced with theme-specific terms throughout the entire ruleset.

With the following:

The Hiatus continues until the new Director of Operations posts an Ascension Address to the BlogNomic weblog - this should specify the Director of Operations’s chosen theme for the new Dynasty, and may optionally specify that the terms Agent and Director of Operations will be replaced with theme-specific terms throughout the entire ruleset, and/or a number of dynastic rules to keep. Upon posting such an Ascension Address, the ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed.

In the rule “Dynasties”, rewrite the first paragraph,

BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single Agent, known as the Director of Operations, and is named according to the number of Dynasties they have headed (eg. “The First Dynasty of Myke”).

to the following:

BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single Agent, known as the Director of Operations.

Add a new rule entitled Objectives:

There exists a wiki document known as The Dossier, which contains a list of all possible Objectives. As a weekly action, an Agent may telephone the Director of Operations to request assignment to an Objective. The Agent may request a specific Objective, but the Director of Operations is not obliged to respect this wish.

Upon receiving such a request, the Director of Operations may assign an Agent to a certain Objective, and if he does so, shall mark upon the wiki document the fact that the Objective has an assigned Agent. The Director of Operations should not compromise the Agent’s identity with this action.

An Agent may be unassigned from an Objective by the Director of Operations at any time, and may only be assigned to a single objective at a given time.

The Director of Operations may not assign Objectives to Agents, but he may remove this sentence from the rules by posting a Story Post stating that he is doing so.

J’espère que je peux rester plus d’une semaine cette fois. Quorum est neuf.

(This is a Core Proposal.)

In Rule 1.9, “Victory and Ascension,” replace this text:

The Hiatus continues until the new Director of Operations posts an Ascension Address to the BlogNomic weblog - this shall specify the Director of Operations’s chosen theme for the new Dynasty, and may optionally include a proclamation that any number of Dynastic Rules will be repealed, and/or that the words Agent and Director of Operations will be replaced with theme-specific terms throughout the entire ruleset.

With the following:

The Hiatus continues until the new Director of Operations posts an Ascension Address to the BlogNomic weblog - this shall specify the Director of Operations’s chosen theme for the new Dynasty, and may optionally specify that the words Agent and Director of Operations will be replaced with theme-specific terms throughout the entire ruleset.  At this time, unless otherwise specified in the Ascension Address, all Dynastic Rules are repealed.

Give Rule 2.2.1 the title “Imposters.”

Add a new Subrule to Rule 2.2, entitled “Codename Tracking,” and give it the following text:

Codenames may have their own entries in the GNDT, as if they were Agents.  Any Agent may update the Description or Last Known Location of a Codename at any time, but only the D-Ops may add new Codenames.

At any time, if a number of Agents greater than or equal to Quorum has confirmed Codenames, the D-Ops may add any number of these Codenames (including those assigned to Imposters, if they wish) to the GNDT.  At any time, if at least three Codenames are tracked in the GNDT but no longer assigned to any Agent or Imposter, the D-Ops may remove any number of these expired Codenames from the GNDT.

In addition, if “Fledgling Allegiance” passes, append the following paragraph to “Codename Tracking:”

Any time an Agent’s Allegiance changes, the D-Ops may secretly change the Codename assigned to an Imposter (if any) with the Agent’s previous Allegiance.

May I please be unidled?

If the Proposal titled “Red, White and Blue” failed, this Proposal does nothing.

In Rule 2.2, replace “If an Agent has a Codename but no Allegiance, D-Ops may assign them an Allegiance at random, and contact them privately to inform them of this fact.” with:-

If an Agent has a Codename but no Allegiance, the D-Ops shall set their Allegiance to Independent.

And add:-

As a Weekly Action, an Agent may Telephone the Director of Ops and request a change of Allegiance.  The D-Ops may effect this change at their discretion, and will notify the Agent when done.

The D-Ops shall set the Allegiance of each Agent with a Codename to Independent.

In addition, should the Proposal titled “The Adversaries” pass, replace “the Imposters, who have a Codename and Description as though they were Agents” with:

the Imposters, who have a Codename, Description and Allegiance as though they were Agents

and the D-Ops shall set the Allegiance of one Imposter to US, another to Soviet, and the third to Independent.

This proposal fails, if the proposal “Red, White and Blue” is not enacted.

Create a rule called “Diplomatic Conundrum” with the exact wording:

Each Nation (America, Britain, France, Russia, East Germany and West Germany) has a diplomacy value (DV), which is a whole number ranging from -5 to 5. The default DV for each value is 0. As an weekly event for each nation the D-Ops throws a DICE2. If the value on the dice is 1 he substracts 2 points from the DV of the respective nation if the value is 2 he adds 2 points to the DV of the respective nation. Values smaller than -5 are set to -5 and values greater 5 are set to 5.  The DV values are secretly tracked by the D-Ops.

In Rule 2.2, replace “An Agent’s Allegiance, if they have one, can be either US, Soviet or Independent. If an Agent has a Codename but no Allegiance, D-Ops may assign them an Allegiance at random, and contact them privately to inform them of this fact.”

with:

An Agent’s Allegiance is determined by his nationality and the DV of his nation.  There are three different Allegiances which are each formed by two nations. Nations form Allegiances according to their DV. The two nations with the highest DV form one Allegiance, so do the two nations with the lowest DV. The remaining two nations form the third Allegiance. If nations have equal DV they belong to the Allegiances according to alphabetical order. The allegiances are announced each week by the D-Ops.

Add a new subrule to the rule “Dossier”.  Give it the following text:

There are three non-Agent entities, the Imposters, who have a Codename and Description as though they were Agents; however, their Descriptions are tracked privately by D-Ops.  No Agent can be given an interim Description that is the same as an Imposter’s Description.

As soon as is practical after this proposal’s enactment, the D-Ops shall choose Codenames and Descriptions for the Imposters.

In Rule 2.2, replace “Each Agent may have a Codename and a Description.” with:-

Each Agent may have a Codename, a Description and an Allegiance.

And add:-

An Agent’s Allegiance, if they have one, can be either US, Soviet or Independent. If an Agent has a Codename but no Allegiance, D-Ops may assign them an Allegiance at random, and contact them privately to inform them of this fact.

Special Agent Amnistar has come back from an overseas trip and is ready to get back into the swing of things.

I’d unidle myself but it’s been awhile and I’m afraid I’ll break something :P

Having graduated from the farm agent Blacky is handing over his orders to join the active agents.

If necessary, revert the Berlin Map page to its 10:42, 1 Oct 2010 revision.

Add a new rule to the ruleset, entitled Berlin 1946:

A map of Berlin can be found here. This page may not be edited unless another rule or enacted proposal specifically allows it.

Each Agent has a Location. Locations are notated as five-letter strings. The first letter of the string refers to which side of Berlin the Agent is in; the second and third letters refer to the sector occupied by the Agent; and the fourth and fifth letters refer to the district. A complete key to location information can be found at the same page as the map, linked to above.

As a weekly action, an Agent may change their Location by telephoning the Director with their point of origin and destination. The list of Locations held by the Director is at all times considered to be definitive.

Each Agent’s Last Known Location is tracked in the GNDT. This must consist of a valid location and of a date at which it was believed to be true. Any Agent may update this at any time, provided that they possess information that is more recent that the information that exists in the GNDT. An Agent may change their own Last Known Location if they wish, but such an update must be truthful.

Add a link to the map to the sidebar and add a column for Last Known Location to the GNDT.

Repeal all Dynastic Rules, and keep the theme and the keywords as they are.