BlogNomic Wiki - User contributions [en]

Ruleset

2015-10-12T08:23:23Z

Purplebeard: /* Dynastic Rules */ Enacting "1527 all over again", with minor corrections (adding full stops after sentences).

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Cardinals shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Cardinals may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Cardinals ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Cardinal'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Cardinal.

A Cardinal may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Cardinal may not rejoin the game within two weeks after having left. A Cardinal may only change their name as a result of a proposal approving the change.

Some Cardinals are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Cardinals who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Cardinals===

Some Cardinals are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Cardinals”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Cardinals are not counted as Cardinals.

If a Proposal contains a provision that targets a specifically named Idle Cardinal, then that Idle Cardinal is considered to be Unidle solely for the purposes of enacting that specific provision

When a Cardinal is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Cardinal Idled in a different dynasty), the Cardinal is given the default value for new Cardinal, if such a value exists.

An Admin may render a Cardinal Idle if that Cardinal has asked to become Idle in an entry or comment from the past four days, or if that Cardinal has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Cardinal if that Cardinal has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Cardinal who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Cardinal, known as the Pope. If there is no Pope, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Cardinals may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Cardinal may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Cardinal’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Cardinal never has a Vote, even if they were a Cardinal previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Cardinal may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Cardinal already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Cardinal casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Pope may use VETO as a voting icon to cast a Vote on a proposal; when the Pope casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Pope later changes their Vote.

If a Cardinal other than the Pope casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Pope. When the Pope has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Pope's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Cardinals who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Cardinals actively disagree as to the interpretation of the Ruleset, or if a Cardinal feels that an aspect of the game needs urgent attention, then any Cardinal may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Cardinal (other than the Pope) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Cardinals”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Cardinal may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Pope has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Cardinals who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Cardinal who made the DoV as its Pope. That Cardinal may pass this role to another Cardinal at this point by making a post to that effect, if they wish. The Hiatus continues until the new Pope makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Pope's chosen theme for the new Dynasty, and may optionally specify that the terms Cardinal and Pope 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Cardinal who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Cardinal's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Cardinal within BlogNomic.
* A Cardinal should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Cardinal should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Cardinal should not edit their own blog comments once posted, nor those of any other Cardinal.
* A Cardinal should not edit the "Entry Date" field of a blog post.
* A Cardinal should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Cardinal should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==Influence==
All Cardinals have Influence, a number tracked in the GNDT. The default value is 5. As a daily action, a Cardinal may make a Speech, increasing the Influence of three other Cardinals by 1. Any Cardinal except the Pope with Influence of 10 or greater is a Papabile.

Each Cardinal with four or more Benefices is a Landowning Cardinal. Whenever a Landowning Cardinal makes a speech, they decrease the Influence of two other Cardinals by one.

==Benefices==
All Cardinals have Benefices, a number tracked in the GNDT. The default value is 1. As a daily action, a Cardinal may reduce their Influence by 2 to increase their Benefices by 1. As a daily action, a Cardinal may reduce their Benefices by 1 to increase the Benefices of another Cardinal by 1.

==Buying Votes==
If a Proposal includes the capitalized phrase "QUID PRO QUO," it is a Paid Proposal. Upon enacting such a Proposal, the enacting admin must deduct from its creator an amount of Influence equal to the number of EVCs on that Proposal that are FOR, not including the EVC of the Cardinal who proposed it. They must then increase by one the Influence of each Cardinal with an EVC of FOR on that Proposal--again, not including the Cardinal who proposed it.

If the above actions would reduce the Proposal creator's Influence below 0, their Influence is instead set to 0, and none of the FOR-voting Cardinals receive an increase in Influence because of it.

==Conclaves==
A Cardinal may call a Conclave if no unresolved Conclave exists, by making a blog post entitled “Papal Conclave on the Day of [NAME]”, substituting for [NAME] a name or celebration that corresponds to the current date on [http://www.catholic.org/saints/calendar/october.php this website]. To be legal, a Conclave must name a number of Roles: X Scrutineers, X Infirmarii and X Revisers, where X is one third of the number of Cardinals, rounded down. The Roles for each Conclave must be determined randomly by the Cardinal calling the Conclave, such that no Cardinal has more than one Role in a Conclave.

If a Cardinal has posted a comment on a Conclave which consists of the single phrase "I elect as Supreme Pontiff X.", where X is the name of a Cardinal other than themselves, and does not already have a Ballot posted on that Conclave, then the comment is considered to be that Cardinal's Ballot for that Conclave, electing the named Cardinal.

If a Conclave is more than 96 hours old and a Cardinal has not posted a Ballot on it, then any Infirmarii with at least 1 Influence may - as a daily action - post a Ballot on that Cardinal's behalf by paying 1 Influence and posting a comment on that Conclave consisting of the phrase "X is unwell, but elects as Supreme Pontiff Y.", where X is the name of the Cardinal in question and Y is the name of any Cardinal.

If a Conclave has received a Ballot from every Cardinal, then any Scrutineer may resolve it: if more than two thirds of the Ballots on that Conclave named the same Cardinal, then the Scrutineer announces that white smoke has been released; otherwise the Scrutineer announces that dark smoke has been released.

==Vices==
Each Cardinal may have a Vice, which is tracked in the GNDT. Cardinals default to having no Vice. Some Vices allow the Cardinal to take actions that are otherwise not permitted, and some have restrictions on when a Cardinal may select them, or what other actions they can take. If a Cardinal has no Vice, they may set their own Vice to one of the options listed below at any time; this is called choosing a Vice.

* '''Superbia''' - A Cardinal may not choose Superbia as their Vice if they are a Papabile. Upon choosing Superbia, the Cardinal gains one Benefice.
* '''Acedia''' - A Cardinal whose Vice is Acedia may not make Speeches. Should another Cardinal make a Speech that would increase the Influence of a Cardinal whose Vice is Acedia, the Cardinal with Acedia gains 2 Influence thereby, instead of 1.
* '''Invidia''' - A Cardinal may not choose Invidia as their Vice if they have any Benefices. As a Daily Action, a Cardinal whose Vice is Invidia may target a Cardinal who does not currently have a Vice, and set that Cardinal’s Vice to any of the options in this list. They may not use this action to set a Vice that the targeted Cardinal would not normally be able to choose.
* '''Luxuria''' - A Cardinal may not choose Luxuria as their Vice if they are a Papabile or they have any Nepotism. Upon choosing Luxuria, the Cardinal gains one Nepotism.
* '''Ira''' - A Cardinal whose Vice is Ira is considered to have one additional Benefices for the purposes of the rule "Invasion".

As a Daily Action, if a Cardinal has not set their Vice within the last 24 hours, they may spend one Benefice to remove their current Vice.

==Loyalty==
Each Cardinal has a Loyalty, tracked in the GNDT. The default value is None.
Possible values for Loyalty are:

* None
* Colonna
* Orsini
* Florence
* Naples
* Venice
* France
* Spain

A Cardinal whose Loyalty is Colonna or Orsini is a Roman. A Cardinal whose Loyalty is France or Spain is a Foreigner.

As a weekly action, a Cardinal other than the Pope may change their Loyalty. If their Loyalty was not None, their Influence is halved.

==Curia==
Each Cardinal may have an Office, which is tracked in the GNDT. Cardinals default to having no Office. The Pope may not have an Office.

As a communal weekly action, a Cardinal may Appoint an office by posting an entry naming that Office. Any Cardinal may Bid on the Appointment by spending 1 Influence and posting a comment to that entry including the phrase “Bid: X” where X is the name of a Cardinal. After 48 hours, the Cardinal named in the most Bids wins the Office. If there is a tie, the Pope may select a Cardinal involved in that tie to win the Office by posting a comment declaring that they do so.
When a Cardinal wins an Office, their Office is set to that Office, and any other Cardinal with that Office loses it.

The Offices are
* '''Dean of the Sacred College'''. Whenever the Dean of the Sacred College makes a Speech, they gain 1 Influence.
* '''Chancellor'''. As a daily action, the Chancellor may increase the Benefices of another Cardinal by 1.
* '''Captain General of the Church'''. The Captain General of the Church is considered to have double the number of Benefices for the purposes of the rule "Invasion".

==Nepotism==
All Cardinals have Nepotism, a number tracked in the GNDT. It defaults to 0. As a weekly action, a Cardinal may spend 2 Benefices to gain 1 Nepotism. As a weekly action, a Cardinal may gain Influence equal to their Nepotism.

==Invastion==
As a weekly communal action, a Cardinal may begin an Invasion by making a blog post to that effect. This post must name the Invading Power, chosen from the list of possible Loyalty values in the rule "Loyalty". An Invasion is a Votable Matter.

The Attack Strength of an Invasion is equal to the sum of the Benefices of Cardinals whose Vote is FOR the invasion.<br>
The Defence Strength of an Invasion is equal to the sum of the Benefices of Cardinals whose Vote is AGAINST the invasion.

If the Pope is not a Roman, and the Invading Power is France or Spain, the Attack Strength is increased by 5.<br>
If the Pope is a Roman, and the Invading Power is Florence, Naples, or Venice, the Attack Strength is increased by 5.<br>
If the Pope is a Foreigner, and the Invading Power is Colonna or Orsini, the Attack Strength is increased by 5.

If an Invasion has been pending for more than 48 hours, and its Attack Strength is greater than or equal to its Defence Strength, it may be Enacted by any Admin. The Pope's Loyalty is changed to that of the Invading Power.
If an Invasion has been pending for more than 48 hours, and cannot be Enacted, it may be Failed by any Admin.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Cardinals.

;Daily Action
:If a game action is a Daily Action, each Cardinal able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Cardinal per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Cardinal’s Effective Vote Comment with respect to a given Votable Matter means that Cardinal’s Comment to that Votable Matter, if any, that contains that Cardinal’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Cardinal may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Cardinals is half the number of Cardinals in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Cardinals it is referring to, it is referring to a Quorum of all Cardinals.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Slack
:The BlogNomic Slack is located at blognomic.slack.com. Cardinals 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.)

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Cardinal able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Cardinal per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Cardinal may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Cardinal has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Cardinal may update any Cardinal's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Cardinal may correct the GNDT to comply with the Gamestate.

If a Cardinal feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Cardinals are encouraged to raise a Call for Judgement instead.
Cardinals shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Cardinal with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Cardinals to transfer a numeric value only allows them to transfer that value from themselves to another Cardinal (of their choice unless otherwise stated).
* A Cardinal who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Cardinal A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a Cardinal if it is explicitly stated that it refers to a Cardinal's name.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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 “Cardinals may Kick each other” and “Cardinals may not kick each other on Tuesdays” exist, and it is Tuesday, Cardinals may not Kick each other.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Cardinals may Punch a Spaceman on Friday” and “Cardinals may not Punch Spacemen on Friday”, then Cardinals may not Punch Spacemen on Friday.)

</div>

Ruleset

2015-10-10T12:30:04Z

Purplebeard: /* Conclaves */ Enacting "Guiding the Pen"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Cardinals shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Cardinals may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Cardinals ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Cardinal'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Cardinal.

A Cardinal may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Cardinal may not rejoin the game within two weeks after having left. A Cardinal may only change their name as a result of a proposal approving the change.

Some Cardinals are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Cardinals who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Cardinals===

Some Cardinals are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Cardinals”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Cardinals are not counted as Cardinals.

If a Proposal contains a provision that targets a specifically named Idle Cardinal, then that Idle Cardinal is considered to be Unidle solely for the purposes of enacting that specific provision

When a Cardinal is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Cardinal Idled in a different dynasty), the Cardinal is given the default value for new Cardinal, if such a value exists.

An Admin may render a Cardinal Idle if that Cardinal has asked to become Idle in an entry or comment from the past four days, or if that Cardinal has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Cardinal if that Cardinal has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Cardinal who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Cardinal, known as the Pope. If there is no Pope, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Cardinals may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Cardinal may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Cardinal’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Cardinal never has a Vote, even if they were a Cardinal previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Cardinal may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Cardinal already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Cardinal casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Pope may use VETO as a voting icon to cast a Vote on a proposal; when the Pope casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Pope later changes their Vote.

If a Cardinal other than the Pope casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Pope. When the Pope has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Pope's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Cardinals who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Cardinals actively disagree as to the interpretation of the Ruleset, or if a Cardinal feels that an aspect of the game needs urgent attention, then any Cardinal may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Cardinal (other than the Pope) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Cardinals”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Cardinal may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Pope has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Cardinals who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Cardinal who made the DoV as its Pope. That Cardinal may pass this role to another Cardinal at this point by making a post to that effect, if they wish. The Hiatus continues until the new Pope makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Pope's chosen theme for the new Dynasty, and may optionally specify that the terms Cardinal and Pope 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Cardinal who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Cardinal's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Cardinal within BlogNomic.
* A Cardinal should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Cardinal should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Cardinal should not edit their own blog comments once posted, nor those of any other Cardinal.
* A Cardinal should not edit the "Entry Date" field of a blog post.
* A Cardinal should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Cardinal should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==Influence==

All Cardinals have Influence, a number tracked in the GNDT. The default value is 5. As a daily action, a Cardinal may make a Speech, increasing the Influence of three other Cardinals by 1. Any Cardinal except the Pope with Influence of 10 or greater is a Papabile.

Each Cardinal with four or more Benefices is a Landowning Cardinal. Whenever a Landowning Cardinal makes a speech, they decrease the Influence of two other Cardinals by one.

==Benefices==

All Cardinals have Benefices, a number tracked in the GNDT. The default value is 1. As a daily action, a Cardinal may reduce their Influence by 2 to increase their Benefices by 1. As a daily action, a Cardinal by reduce their Benefices by 1 to increase the Benefices of another Cardinal by 1.

==Buying Votes==

If a Proposal includes the capitalized phrase "QUID PRO QUO," it is a Paid Proposal. Upon enacting such a Proposal, the enacting admin must deduct from its creator an amount of Influence equal to the number of EVCs on that Proposal that are FOR, not including the EVC of the Cardinal who proposed it. They must then increase by one the Influence of each Cardinal with an EVC of FOR on that Proposal--again, not including the Cardinal who proposed it.

If the above actions would reduce the Proposal creator's Influence below 0, their Influence is instead set to 0, and none of the FOR-voting Cardinals receive an increase in Influence because of it.

==Conclaves==

A Cardinal may call a Conclave if no unresolved Conclave exists, by making a blog post entitled “Papal Conclave on the Day of [NAME]”, substituting for [NAME] a name or celebration that corresponds to the current date on [http://www.catholic.org/saints/calendar/october.php this website]. To be legal, a Conclave must name a number of Roles: X Scrutineers, X Infirmarii and X Revisers, where X is one third of the number of Cardinals, rounded down. The Roles for each Conclave must be determined randomly by the Cardinal calling the Conclave, such that no Cardinal has more than one Role in a Conclave.

If a Cardinal has posted a comment on a Conclave which consists of the single phrase "I elect as Supreme Pontiff X.", where X is the name of a Cardinal other than themselves, and does not already have a Ballot posted on that Conclave, then the comment is considered to be that Cardinal's Ballot for that Conclave, electing the named Cardinal.

If a Conclave is more than 96 hours old and a Cardinal has not posted a Ballot on it, then any Infirmarii with at least 1 Influence may - as a daily action - post a Ballot on that Cardinal's behalf by paying 1 Influence and posting a comment on that Conclave consisting of the phrase "X is unwell, but elects as Supreme Pontiff Y.", where X is the name of the Cardinal in question and Y is the name of any Cardinal.

If a Conclave has received a Ballot from every Cardinal, then any Scrutineer may resolve it: if more than two thirds of the Ballots on that Conclave named the same Cardinal, then the Scrutineer announces that white smoke has been released; otherwise the Scrutineer announces that dark smoke has been released.

==Vices==

Each Cardinal may have a Vice, which is tracked in the GNDT. Cardinals default to having no Vice. Some Vices allow the Cardinal to take actions that are otherwise not permitted, and some have restrictions on when a Cardinal may select them, or what other actions they can take. If a Cardinal has no Vice, they may set their own Vice to one of the options listed below at any time; this is called choosing a Vice.

* '''Superbia''' - A Cardinal may not choose Superbia as their Vice if they are a Papabile. Upon choosing Superbia, the Cardinal gains one Benefice.
* '''Acedia''' - A Cardinal whose Vice is Acedia may not make Speeches. Should another Cardinal make a Speech that would increase the Influence of a Cardinal whose Vice is Acedia, the Cardinal with Acedia gains 2 Influence thereby, instead of 1.
* '''Invidia''' - A Cardinal may not choose Invidia as their Vice if they have any Benefices. As a Daily Action, a Cardinal whose Vice is Invidia may target a Cardinal who does not currently have a Vice, and set that Cardinal’s Vice to any of the options in this list. They may not use this action to set a Vice that the targeted Cardinal would not normally be able to choose.

As a Daily Action, if a Cardinal has not set their Vice within the last 24 hours, they may spend one Benefice to remove their current Vice.

==Loyalty==
Each Cardinal has a Loyalty, tracked in the GNDT. The default value is None.
Possible values for Loyalty are:

* None
* Colonna
* Orsini
* Florence
* Naples
* Venice
* France
* Spain

A Cardinal whose Loyalty is Colonna or Orsini is a Roman. A Cardinal whose Loyalty is France or Spain is a Foreigner.

As a weekly action, a Cardinal may change their Loyalty. If their Loyalty was not None, their Influence is halved.

==Curia==
Each Cardinal may have an Office, which is tracked in the GNDT. Cardinals default to having no Office. The Pope may not have an Office.

As a communal weekly action, a Cardinal may Appoint an office by posting an entry naming that Office. Any Cardinal may Bid on the Appointment by spending 1 Influence and posting a comment to that entry including the phrase “Bid: X” where X is the name of a Cardinal. After 48 hours, the Cardinal named in the most Bids wins the Office. If there is a tie, the Pope may select a Cardinal involved in that tie to win the Office by posting a comment declaring that they do so.
When a Cardinal wins an Office, their Office is set to that Office, and any other Cardinal with that Office loses it.

The Offices are
* '''Dean of the Sacred College'''. Whenever the Dean of the Sacred College makes a Speech, they gain 1 Influence.
* '''Chancellor'''. As a daily action, the Chancellor may increase the Benefices of another Cardinal by 1.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Cardinals.

;Daily Action
:If a game action is a Daily Action, each Cardinal able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Cardinal per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Cardinal’s Effective Vote Comment with respect to a given Votable Matter means that Cardinal’s Comment to that Votable Matter, if any, that contains that Cardinal’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Cardinal may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Cardinals is half the number of Cardinals in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Cardinals it is referring to, it is referring to a Quorum of all Cardinals.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Slack
:The BlogNomic Slack is located at blognomic.slack.com. Cardinals 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.)

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Cardinal able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Cardinal per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Cardinal may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Cardinal has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Cardinal may update any Cardinal's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Cardinal may correct the GNDT to comply with the Gamestate.

If a Cardinal feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Cardinals are encouraged to raise a Call for Judgement instead.
Cardinals shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Cardinal with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Cardinals to transfer a numeric value only allows them to transfer that value from themselves to another Cardinal (of their choice unless otherwise stated).
* A Cardinal who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Cardinal A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a Cardinal if it is explicitly stated that it refers to a Cardinal's name.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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 “Cardinals may Kick each other” and “Cardinals may not kick each other on Tuesdays” exist, and it is Tuesday, Cardinals may not Kick each other.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Cardinals may Punch a Spaceman on Friday” and “Cardinals may not Punch Spacemen on Friday”, then Cardinals may not Punch Spacemen on Friday.)

</div>

Laundry list

2015-08-19T15:39:34Z

Purplebeard: /* Not yet fixed */

This is a page for players to note possible ruleset problems which should probably be fixed at some point, because we tend to forget otherwise. It would be poor etiquette to scam any of these, but we would deserve it.

==Fixed==
* <strike>Idle players may still count as players for the purposes of proposals, as argued [http://blognomic.com/archive/automatic_for_the_people/ here]. (Rule 1.2.1 only excepts rules, not proposals.)</strike> [http://blognomic.com/archive/out_of_mind/ Fixed.]
* <strike>What happens if we vote through a proposal that says "two days after this proposal passes, Player X gains 1 point" (or more dramatically, "two years after this proposal passes, Player X may declare victory in whatever dynasty is being played at that time")? Is such an "invisible rule" legal?</strike> [http://blognomic.com/archive/a_distant_boomerang Fixed.]
* <strike>Dynasty #110 [http://blognomic.com/archive/no_silent_idles/ changed] admin idling so that if they fail to announce the idling, it's illegal. Given that not every admin rereads the core rules when unidling, this risks leaving dangerously quorum-changing ghosts if an admin idles themselves out without posting the required paperwork comment.</strike> Update: [http://blognomic.com/archive/this_was_thought_up_earlier/ it is now a 'should' clause]
* <strike>"When a DoV is failed, if it has a number of AGAINST Votes that exceed Quorum, the Apprentice who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed." - but DoVs can be failed when they reach a number of AGAINST votes that ''equal'' quorum. This should probably just lose the comma'd clause entirely.</strike>
* <strike>"Random" decisions are required to be "taken from a uniform probability distribution over the entire range of possible values", but there's only an implicit requirement that the GNDT be used for this. Apart from secret Imperial rolls, it'd help to make the GNDT compulsory here.</strike>
* <strike>"a wiki page shall be blanked when it becomes gamestate" ([http://blognomic.com/archive/fixes2/ enacted eluctantly in June 2013] as part of a wider fix) risks blanking the entire BlogNomic wiki if we accidentally do something to make all of it gamestate.</strike> [http://blognomic.com/archive/greyer_than_white/ Fixed]
* <strike>''"If a game variable has no defined starting value for new Shuttles, or for existing Shuttles upon the variable’s creation, then that starting value is zero (for numerical variables) or blank (for a text string or list)."'' - what if zero or blank are illegal values?</strike>

==Not yet fixed==
* ''"Each Believer may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon. [...] A Believer’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter."'' - this is a little opaque/redundant when an idle player makes a vote-icon comment before unidling.
* The Seasonal Hiatus is a bit of an activity roadblock - is it worse for the game than just continuing over Christmas would be? Is there a way of making it more responsive to periods when the game is active and the players want to continue?
* ''"A keyword defined by a rule supersedes the normal English usage of the word."'' - what exactly counts as being "defined"?
** Relatedly, we should define what constitutes a 'keyword' in the first place.
* Sometimes proposals are timestamped "incorrectly" - a player starts writing a proposal at 3pm, finishes at 6pm, and then posts it with a timestamp of 3pm. The ruleset blindly refers to "the oldest pending proposal" and how long it has been "open for voting" without referring to timestamps. We should probably find some way to make timestamps the authoritative age of a proposal, but in a way which can't be exploited.
* "If you make a GNDT dice roll, do you have to use it?" - if there's a rule of "a player may roll DICE4 once a week to gain that many victory points", can I roll DICE4 a few times in succession and use the last one for the action, explaining that the others were just for fun?
* If a player "must" perform a series of steps in sequence, is there an acceptable delay between steps? Can they interrupt those steps with other game actions?
* "Defaulting" could use further definition, when we say something like "players have Food, defaulting to 10". It's covered in the Idle Players rule, but nowhere else.
** (For anyone who doesn't know, this is Agora terminology (Rule 2126b) that people started using at BlogNomic out of Agoran habit, even though it wasn't defined over here; the default value gets set when the piece of gamestate is created, or if it would otherwise fail to have a determinate value (e.g. after being changed infinitely often in finite time). It probably works the way that people expect it to work even here, though.)
* When a rule says that a gamestate change just happens, we're usually implying that the person who initiated the action is responsible for making that change too - should probably codify that somewhere.
* The scope for simultaneous DoVs is strange. The rules presumably allow them because they deter "everyone wins" scams (which would otherwise always go to the scammer), but what actually happens if such a scam is pulled and everyone wins? Just an awkward "I think everyone won, and I'm going to just vote for my friend's DoV for now, and have a little break" voting race?

Ruleset

2015-08-18T07:13:43Z

Purplebeard: /* Dynastic Rules */ Enacting "Negative One"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

===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.

===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, with a GNDT comment that repeats the Sign Hash of the creation request and contains no other Hashes; if this has not been completed within 24 hours of the request being made then the Zero Cool must create the requested Codename.

==Tools of the Trade==
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 in the order they are listed in the Corp Name’s GNDT field, then of each of its Subroutines applied once in the order that they are listed in the Tool’s GNDT field.

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

Subroutines that currently exist are as follows:

*^ - Slicer - +2 to the Hack Value of this Tool
*@ - 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
*& - 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.
*2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.
*? - 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)
* # - Root Access - all non-Elevated Subroutines between two Root Accesses become Elevated. Elevated Subroutines gain +1 Hack Value. After a Hack Attempt with this Tool, all Back Doors after a Root Access are removed.
* i - Infection - After a hack replace a Valid Security Measure of the target Corp Name of the Codename’s choosing with a Virus

==Corporate Defence==
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.

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 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.

===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 the right of the Security Measures list of 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.
* V - Virus - Subtracts ((the number of viruses of this Corp Name-1)*2) from the Defence Score of this Corp Name.

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.

==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.

==Hacking==

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.

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 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 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.

==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.

==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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Ruleset

2015-08-18T07:05:59Z

Purplebeard: /* Dynastic Rules */ Enacting "Orienteering"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

===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.

===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, with a GNDT comment that repeats the Sign Hash of the creation request and contains no other Hashes; if this has not been completed within 24 hours of the request being made then the Zero Cool must create the requested Codename.

==Tools of the Trade==
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.

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

Subroutines that currently exist are as follows:

*^ - Slicer - +2 to the Hack Value of this Tool
*@ - 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
*& - 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.
*2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.
*? - 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)
* # - Root Access - all non-Elevated Subroutines between two Root Accesses become Elevated. Elevated Subroutines gain +1 Hack Value. After a Hack Attempt with this Tool, all Back Doors after a Root Access are removed.
* i - Infection - After a hack replace a Valid Security Measure of the target Corp Name of the Codename’s choosing with a Virus

==Corporate Defence==
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.

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 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.

===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 the right of the Security Measures list of 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.
* V - Virus - Subtracts ((the number of viruses of this Corp Name-1)*2) from the Defence Score of this Corp Name.

==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.

==Hacking==

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.

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 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 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.

==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.

==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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Ruleset

2015-08-11T07:00:07Z

Purplebeard: /* Dynastic Rules */ Enacting "The House Always Wins"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

===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.

==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. 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.

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

Subroutines that currently exist are as follows:

*^ - 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 Codename’s choosing
*2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.
*? - 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)

==Corporate Defence==
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.

==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.

==Hacking==

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.

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 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 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.

==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.

==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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Ruleset

2015-08-11T06:55:15Z

Purplebeard: /* Tools of the Trade */ Enacting "Friday Afternoon Patches"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

==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. 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.

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

Subroutines that currently exist are as follows:

*^ - 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 Codename’s choosing
*2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.
*? - 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)

==Corporate Defence==
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.

==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.

==Hacking==

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.

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 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 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.

==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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Ruleset

2015-08-11T06:50:49Z

Purplebeard: /* Hacking */ Enacting "Trust Inc"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

==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. 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.

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

Subroutines that currently exist are as follows:

*^ - 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
*2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.

==Corporate Defence==
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.

==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.

==Hacking==

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.

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 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 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.

==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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Main Page

2015-08-10T08:33:49Z

Purplebeard: /* Proposed Core Game Documents Substitutes */ Clarification

BlogNomic is a game of Nomic run as a communal weblog, that started in January 2003. Proposals are made as posts to the [http://blognomic.com BlogNomic blog], with votes made as comments on those posts, and the ruleset stored here on the wiki.

BlogNomic is played over a number of themed, pseudo-Imperial rounds (or "dynasties"), presided over by one player as its "Emperor" figure. The Emperor chooses the theme for the dynasty, and is regarded as its caretaker, with the power to veto proposals made during it - this is as close as BlogNomic gets to having anybody in charge. When somebody wins a dynasty, we wipe the ruleset (except for the basic mechanics of voting and proposing) and start a new one with that player as its Emperor.

==Current Game Documents==

*[[Ruleset]]

''(When moving document links to the Older Document section please remove the link from this section.)''

==General Reference==

===Gameplay===
*[[FAQ]]
*[[Newbie Guide]]
*[[Laundry list]]
*[[Admin Manual]]

===Writing===
*[[Essays|Player essays]]
*[[BlogNomic quotes file]]
*[[Blognomic Jargon]]
*[[Admin feedback]] for the technical side of BlogNomic

===History===
*[[Graphs of BlogNomic history]]
*[[BlogNomic Fun Survey]]
*[[Historical player names]]
*[[Site Changelog]]

===Useful Links===
*[https://greasyfork.org/en/scripts/7758-bnscript-blognomic-utility-script BN Greasemonkey Script], which gives links to new comments and automatically tallies votes.
*[http://blognomic.com/archive/automatic_vote_counter/ ais523's Automatic Vote Counter on IRC]
*[http://kevan.org/blognomic/whosidle.php Kevan's automatic idle-player checker]
*[http://blogspot.blognomic.com/ Blogspot archive] (2003-2005) recovered by Roujo and 75th Trombone, missing all comments
*[http://kevan.org/bnwiki.pl?HomePage The old wiki, including Dynastic Histories]
*[http://twitter.com/blognomic BlogNomic Twitter feed]
*[http://cemerick.github.com/jsdifflib/demo.html Javascript Diff] - compare two texts (useful for checking "reword this entire rule to:" proposals)

==Dynastic History==
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
#[[Round One]] - Pre-Dynasty
#[[The First Dynasty of Myke]] - The Kingdom Dynasty
#[[The First Dynasty of Lyndse]] - The Robin Hood Dynasty
#[[The First Dynasty of Geran / The Second Dynasty of Myke|The Second Dynasty of Myke]] - The Agricultural Dynasty
#[[The First Dynasty of Kevan]] - The Orwellian Dynasty
#[[The First Dynasty of Anthony]] - The Mad Emperor Dynasty
#[[The First Dynasty of est]] - The Robot Factory Dynasty
#[[The Second Dynasty of Kevan]] - The Moreau Dynasty
#[[The First Dynasty of Damanor]] - The Galactic Dynasty
#[[The Third Dynasty of Kevan]] - The Thing Dynasty
#[[The First Dynasty of Cayvie]] - The Elemental Dynasty
#[[The First Dynasty of Joranj]] - The Mob Dynasty
#[[The First Dynasty of Keitalia]] - The Superhero Dynasty
#[[The First Dynasty of SatyrEyes]] - The Odyssey Dynasty
#[[The First Metadynasty]] - The Hat Meta-Dynasty
#[[The Second Dynasty of Cayvie]] - The Crashed Spaceship Dynasty
#[[The First Dynasty of Brendan]] - The Office Dynasty
#[[The Fourth Dynasty of Kevan]] - The Petri-Dish Dynasty
#[[The First Dynasty of Knightking]] - The Warlord Dynasty
#[[The First Dynasty of Chronos Phaenon]] - The Democratic Dynasty
#[[The First Dynasty of TrumanCapote]] - The Family Dynasty
#[[The Second Dynasty of Knightking]] - The Zombie Dynasty
#[[The First Dynasty of Quazie]] - The Muffin Dynasty
#[[The First Dynasty of Simon]] - The Surfer Dynasty
#[[The First Dynasty of AngryGrasshopper]] - The Spaceship Dynasty
#[[The First Dynasty of Rodney]] - The Illuminati Dynasty
#[[The First Dynasty of Aaron]] - The Athenian Dynasty
#[[The Second Dynasty of Josh]] - The Gaming Dynasty
#[[The Second Metadynasty]] - The Switch Dynasty
#[[The Second Dynasty of Chronos Phaenon]] - The Hegemonic Dynasty
#[[The First Dynasty of Excalabur]] - The Deity Dynasty
#[[The Second Dynasty of Excalabur]] - The Schizophrenic Dynasty
#[[The First Dynasty of 75th Trombone]] - The Text Adventure Dynasty
#[[The First Dynasty of Elias IX]] - The Pirate Dynasty
#[[The Third Metadynasty]] - The Gostak Metadynasty
#[[The Second Dynasty of Angry Grasshopper]] - The Monastic Murder Mystery Dynasty
#[[The First Dynasty of Hix]] - The Time Travelling Dynasty
#[[The First Dynasty of Thelonious]] - The Musical Dynasty
#[[The Second Dynasty of Elias IX]] - The Vegetable Dynasty
#[[The Second Dynasty of Rodney]] - The Miskatonic Dynasty
#[[The First Dynasty of Clucky]] - The Olympic Dynasty
#[[The First Dynasty of Doremi]] - The Hollywood Dynasty
#[[The Third Dynasty of Chronos Phaenon]] - The Iudex Dynasty
#[[The First Dynasty of Amnistar]] - The Secret Agent Dynasty
#[[The Second Dynasty of Clucky]] - The Spore Dynasty
#[[The Second Dynasty of Amnistar]] - The Goldberg Factory Dynasty
#[[The First Dynasty of Bucky]] - The Corporate Dynasty
#[[The Third Dynasty of Clucky]] - The Monkey Dynasty
#[[The Third Dynasty of Josh]] - The Kaiju Dynasty
#[[The Fifth Dynasty of Kevan]] - The Werewolf Dynasty
#[[The Second Dynasty of Hix]] - The Valkyrie Dynasty
#[[The First Dynasty of spikebrennan]] - The Wild West Poker Dynasty
#[[The First Dynasty of Jack]] - The Pirate vs Ninja Dynasty
#[[The First Dynasty of Purplebeard]] - The Evil Dynasty
#[[The First Dynasty of Rodlen]] - The Multi-Dimensional (and still evil) Dynasty
#[[The First Dynasty of Yoda]] - The RPG Dynasty
#[[The Third Dynasty of Amnistar]] - The Political Dynasty
#[[The First Dynasty of Darknight]] - The Dragon Dynasty
#[[The Second Dynasty of Bucky]] - The Barbarian Dynasty
#[[The Second Dynasty of Yoda]] - The Deja Vu Dynasty
#[[The Fourth Metadynasty]] - The First Metadynasty of Rodlen (Blo vs Gno vs Mic)
#[[The First Dynasty of arthexis]] - The Guess the Theme (Gourmet Drag Racing on Mars) Dynasty
#[[The Fourth Dynasty of Amnistar]] - The Military Dynasty
#[[The First Dynasty of Devenger]] - The Movie Body Count Dynasty
#[[The First Dynasty of ais523]] - The Reality TV Dynasty
#[[The First Dynasty of yuri_dragon_17]] - The Caribbean Vacation Dynasty
#[[The First Dynasty of Qwazukee]] - The Groundhog Day Dynasty
#[[The First Dynasty of Darth Cliche]] - The Post-Apocalyptic Dynasty
#[[The Fifth Metadynasty]] - The Original Game of Nomic Metadynasty
#[[The Third Dynasty of Bucky]] - The Runic Dynasty
#[[The First Dynasty of Wakukee]] - The Djinn Djinasty
#[[The Sixth Dynasty of Kevan]] - The Mansion Murder Dynasty
#[[The Second Dynasty of ais523]] - The Steampunk Dynasty
#[[The Fourth Dynasty of Josh]] - The April Fools Dynasty
#[[The Second Dynasty of Purplebeard]] - The Mining Camp Dynasty
#[[The Third Dynasty of ais523]] - The Election Dynasty
#[[The Second Dynasty of Ienpw III]] - The Undefined Term Dynasty
#[[The Second Dynasty of Darth Cliche]] - The NetHack Dynasty
#[[The First Dynasty of lilomar]] - The Paranoia Dynasty
#[[The First Dynasty of coppro]] - The Futurama Dynasty
#[[The Fourth Dynasty of ais523]] - The IQ Dynasty
#[[The Seventh Dynasty of Kevan]] - The Cold War Spy Dynasty
#[[The Second Dynasty of Brendan]] - The School of Witchcraft Dynasty
#[[The First Dynasty of Alecto]] - The Roman Gods Dynasty
#[[The Fifth Dynasty of Josh]] - The LEGO® Dynasty
#[[The Fourth Dynasty of Clucky]] - The Ant Dynasty
#[[The Third Dynasty of Purplebeard]] - The Prehistoric Dynasty
#[[The Eighth Dynasty of Kevan]] - The Mornington Crescent Dynasty
#[[The Fifth Dynasty of ais523]] - The Sheep Dynasty
#[[The Fourth Dynasty of Purplebeard]] - The Stock Market Dynasty
#[[The Third Dynasty of Yoda]] - The Plants vs Zombies Dynasty
#[[The Fourth Dynasty of Bucky]] - The ClingBoom Arena Dynasty
#[[The Ninth Dynasty of Kevan]] - The Lifeboat Dynasty
#[[The First Dynasty of Bateleur]] - The Art Dynasty
#[[The Sixth Metadynasty]] - The Today's Economy Dynasty
#[[The Second Dynasty of coppro]] - The Taxicab Dynasty
#[[The Sixth Dynasty of ais523]] - The Petty Crime Dynasty
#[[The First Dynasty of Cpt_Koen]] - The Band Dynasty
#[[The First Dynasty of southpointingchariot]] - The Ansible Dynasty
#[[The Sixth Dynasty of Josh]] - The Visiting the Past Dynasty
#[[The Third Machine of scshunt]] - The Factory Machine Dynasty
#[[The First Dynasty of Quirck]] - The Manul Dynasty
#[[The Fifth Dynasty of Clucky]] - The Pie Dynasty
#[[The Fifth Dynasty of Bucky]] - The Nomic School Dynasty
#[[The Tenth Dynasty of Kevan]] - The Newspaper Dynasty
#[[The Seventh Dynasty of Josh]] - The Heist Dynasty
#[[The Eleventh Dynasty of Kevan]] - The Doomsday Cult Dynasty
#[[The Fourth Dynasty of scshunt]] - The Dynasty of the Commons
#[[The First Dynasty of RaichuKFM]] - The Interstellar Fleet Dynasty
#[[The First Dynasty of Larrytheturtle]] - The Noble Families Dynasty
#[[The First Dynasty of Skju]] - The Principia Blognomica Dynasty
#[[The Seventh Metadynasty]]
#[[The Fifth Dynasty of Purplebeard]] - The Magical Apprentice Dynasty
#[[The First Dynasty of Spitemaster]] - The Government Shutdown Dynasty
#[[The Eighth Dynasty of Josh]] - The Despot Dynasty
#[[The Second Dynasty of RaichuKFM]] - The Marooned Dynasty
#[[The First Dynasty of The Alien]] - The Alien NPC Dynasty
#[[The First Dynasty of Benzene]] - The Chemistry Dynasty
#[[The Third Dynasty of RaichuKFM]] - The Chivalric Dynasty
#[[The Sixth Dynasty of Purplebeard]] - The Assassin Dynasty
#[[The Twelfth Dynasty of Kevan]] - The Attic Clearance Dynasty
#[[The First Dynasty of Ayesdeeef]] - The Soccer Dynasty
#[[The Sixth Dynasty of Bucky]] - The Jupiter Shuttle Dynasty
#[[The Thirteenth Dynasty of Kevan]] - The Android Dynasty
#[[The Ninth Dynasty of Josh]] - The Seasonal Dynasty
#[[The First Dynasty of Mideg]] - The Restaurant Dynasty
#[[The Fourteenth Dynasty of Kevan]] - The Shapeshifter Dynasty
#[[The Third Dynasty of Brendan]] - The Kaiju Court Dynasty
#[[The Fifteenth Dynasty of Kevan]] - The Mad Max Diplomacy Dynasty
#[[The First Dynasty of Tantusar]] - The Lab Rat Dynasty
#[[The Tenth Dynasty of Josh]] - The Cyberpunk Dynasty
</div>

==Archive==

===Older Core Game Documents===

''Add new Documents to the top of the list at the end of each dynasty.''

[[The Maze]], [[The Wasteland]], [[Cooking Equipment]], [[Orbit Contents]], [[Hivemind Charters]], [[Market Values]], [[Second-Hand Goods]], [[Space]], [[Reagents]], [[Sequester]], [[Spellbook]], [[Question]], [[Truths]], [[Peerage]], [[Feuds]], [[Tournaments]], [[Galaxy Map]], [[The Hangar]], [[Garage]], [[Fence]], [[The Whiteboard]], [[Factory Floor]], [[Machines]], [[Routes]], [[The Arena]], [[Garden Patch]], [[Gardening Compendium]], [[Species Compendium]], [[BN Index]], [[Check before you travel]], [[Photo Albums]], [[Research projects]], [[Trails]], [[Toybox]], [[Mortals]], [[Teachers]], [[Berlin map]], [[The Dossier]], [[Trading Post]], [[Inventions]], [[County Activity]], [[Wodehouse surnames]], [[Corporations]], [[List of forms]], [[Code of Conduct]], [[I|Inventory]], [[Loot]], [[My dynasty]], [[Stockpile]], [[Settlement]] ([http://blognomic.appspot.com/purplebeard-2/settlement Script version]), [[Inventions]], [[Trading Post]], [[County Activity]], [[Universe]], [[Inventory Items]], [[City]], [[Good Deeds]], [[Parallel Ruleset]], [[Rewards]], [[Diary Entries]], [[:Category:Acts of Dynasty 64]], [[Action Props]], [[List of American film actors]], [[Bonus Features]], [[Theme Hints]], [[Ingredients]], [[The Table]], [[Recipes]], [[Vehicles]], [[Solar Map]], [[Faction BLO Ruleset]], [[Faction GNO Ruleset]], [[Faction MIC Ruleset]], [[Gnomish Scrolls]], [[Plot Summary]], [[Locations]], [[Occupations]], [[Backpack]], [[Dragon Eggs]], [[Candidate Agendas]], [[Planar Entities]], [[Space Tech]], [[Spacecraft Register]], [[Member Dossiers]], [[Earth]], [[Storage Zone]], [[Doomsday Device]], [[Treasures Page]], [[Sea Monsters]], [[Wanted Poster|Wanted Posters]], [[Poker Hands]], [[Old Rulesets]], [[The Creature Page]], [[List of Traits]], [[List of Events]], [[Filmographies]], [[Threads]], [[Deity Wiki]], [[Cities]], [[Monastery of St. Passignano Map]], [[Timeline|The Timeline]], [[Zodiac Wiki]], [[The Lost List]], [[Events Page]], [[Events_Page]], [[Motions]], [[Mystical Chant]], [[Chant Regulations]], [[List of Gadgets]], [[Missions]], [[Gadget Requests]], [[List of Approved Gadgets]], [[List of In-play Gadgets]], [http://blognomic.com/archive/cant_see_map/ The Map], [[Legend]], [[Inventory]], [[Monkey Dynasty Gamestate Documents]], [[The City]], [[The Media Circus]], [[Monster Roster]], [[Book of the Kaiju]], [[Einherjar]], [[About non-metallic mineral resources in China]], [[Character Sheets]], [[Quest Journal]], [[Item List]]

===Proposed Core Game Documents Substitutes (2006-2008)===
*[[Ruleset Draft]]
*[[Ruleset Draft, Take Two]]
*[[Ruleset Draft, the Third]]

=== Switch to blognomic.com (2005) ===

*[[Switch suggestions]]
*[[Switch plans]]
*[[Switch guidebook]]

Ruleset

2015-08-10T08:03:59Z

Purplebeard: /* Tools of the Trade */ Enacting "Turing Zest"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

==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. 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.

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

Subroutines that currently exist are as follows:

*^ - 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
*2 - Amplifier - If this is the leftmost Amplifier in the Tool, then the Hack Value of this Tool is doubled.

==Corporate Defence==
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.

==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.

==Hacking==

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.

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 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 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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Ruleset

2015-08-10T08:00:56Z

Purplebeard: /* Hacking */ Enacting "Identity Crisis"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

==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. 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.

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

Subroutines that currently exist are as follows:

*^ - 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

==Corporate Defence==
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.

==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.

==Hacking==

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.

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 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 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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Ruleset

2015-08-09T09:07:54Z

Purplebeard: Correcting the amusing results of the keyword update at the start of the dynasty

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Hackers shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Hackers may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Hackers ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Hacker'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Hacker.

A Hacker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Hacker may not rejoin the game within two weeks after having left. A Hacker may only change their name as a result of a proposal approving the change.

Some Hackers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Hackers who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Hackers===

Some Hackers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Hackers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Hackers are not counted as Hackers.

If a Proposal contains a provision that targets a specifically named Idle Hacker, then that Idle Hacker is considered to be Unidle solely for the purposes of enacting that specific provision

When a Hacker is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Hacker Idled in a different dynasty), the Hacker is given the default value for new Hacker, if such a value exists.

An Admin may render a Hacker Idle if that Hacker has asked to become Idle in an entry or comment from the past four days, or if that Hacker has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Hacker if that Hacker has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Hacker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Hacker, known as the Zero Cool. If there is no Zero Cool, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Hackers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Hacker may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Hacker’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Hacker never has a Vote, even if they were a Hacker previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Hacker may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Hacker already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Hacker casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Zero Cool may use VETO as a voting icon to cast a Vote on a proposal; when the Zero Cool casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Zero Cool later changes their Vote.

If a Hacker other than the Zero Cool casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Zero Cool. When the Zero Cool has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Zero Cool's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Hackers actively disagree as to the interpretation of the Ruleset, or if a Hacker feels that an aspect of the game needs urgent attention, then any Hacker may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Hacker (other than the Zero Cool) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Hackers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Hacker may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Zero Cool has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Hackers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Hacker who made the DoV as its Zero Cool. That Hacker may pass this role to another Hacker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Zero Cool makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Zero Cool's chosen theme for the new Dynasty, and may optionally specify that the terms Hacker and Zero Cool 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Hacker who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Hacker's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Hacker within BlogNomic.
* A Hacker should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Hacker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Hacker should not edit their own blog comments once posted, nor those of any other Hacker.
* A Hacker should not edit the "Entry Date" field of a blog post.
* A Hacker should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Hacker should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==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 preceded by a colon to denote that it is a Codename. 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. 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.

===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.

==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. 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.

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

Subroutines that currently exist are as follows:

*^ - 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

==Corporate Defence==
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.

==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.

==Hacking==

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.

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 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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Hackers.

;Daily Action
:If a game action is a Daily Action, each Hacker able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Hacker per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Hacker’s Effective Vote Comment with respect to a given Votable Matter means that Hacker’s Comment to that Votable Matter, if any, that contains that Hacker’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Hacker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Hackers is half the number of Hackers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Hackers it is referring to, it is referring to a Quorum of all Hackers.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Hacker able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Hacker per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Hacker may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Hacker has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Hacker may update any Hacker's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Hacker may correct the GNDT to comply with the Gamestate.

If a Hacker feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Hackers are encouraged to raise a Call for Judgement instead.
Hackers shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Hacker with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Hackers to transfer a numeric value only allows them to transfer that value from themselves to another Hacker (of their choice unless otherwise stated).
* A Hacker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Hacker A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===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.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Hackers may Punch a Spaceman on Friday” and “Hackers may not Punch Spacemen on Friday”, then Hackers may not Punch Spacemen on Friday.)

</div>

Main Page

2015-08-05T11:39:04Z

Purplebeard: Begone, Maze!

BlogNomic is a game of Nomic run as a communal weblog, that started in January 2003. Proposals are made as posts to the [http://blognomic.com BlogNomic blog], with votes made as comments on those posts, and the ruleset stored here on the wiki.

BlogNomic is played over a number of themed, pseudo-Imperial rounds (or "dynasties"), presided over by one player as its "Emperor" figure. The Emperor chooses the theme for the dynasty, and is regarded as its caretaker, with the power to veto proposals made during it - this is as close as BlogNomic gets to having anybody in charge. When somebody wins a dynasty, we wipe the ruleset (except for the basic mechanics of voting and proposing) and start a new one with that player as its Emperor.

==Current Game Documents==

*[[Ruleset]]

''(When moving document links to the Older Document section please remove the link from this section.)''

==General Reference==

===Gameplay===
*[[FAQ]]
*[[Newbie Guide]]
*[[Laundry list]]
*[[Admin Manual]]

===Writing===
*[[Essays|Player essays]]
*[[BlogNomic quotes file]]
*[[Blognomic Jargon]]
*[[Admin feedback]] for the technical side of BlogNomic

===History===
*[[Graphs of BlogNomic history]]
*[[BlogNomic Fun Survey]]
*[[Historical player names]]
*[[Site Changelog]]

===Useful Links===
*[https://greasyfork.org/en/scripts/7758-bnscript-blognomic-utility-script BN Greasemonkey Script], which gives links to new comments and automatically tallies votes.
*[http://blognomic.com/archive/automatic_vote_counter/ ais523's Automatic Vote Counter on IRC]
*[http://kevan.org/blognomic/whosidle.php Kevan's automatic idle-player checker]
*[http://blogspot.blognomic.com/ Blogspot archive] (2003-2005) recovered by Roujo and 75th Trombone, missing all comments
*[http://kevan.org/bnwiki.pl?HomePage The old wiki, including Dynastic Histories]
*[http://twitter.com/blognomic BlogNomic Twitter feed]
*[http://cemerick.github.com/jsdifflib/demo.html Javascript Diff] - compare two texts (useful for checking "reword this entire rule to:" proposals)

==Dynastic History==
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
#[[Round One]] - Pre-Dynasty
#[[The First Dynasty of Myke]] - The Kingdom Dynasty
#[[The First Dynasty of Lyndse]] - The Robin Hood Dynasty
#[[The First Dynasty of Geran / The Second Dynasty of Myke|The Second Dynasty of Myke]] - The Agricultural Dynasty
#[[The First Dynasty of Kevan]] - The Orwellian Dynasty
#[[The First Dynasty of Anthony]] - The Mad Emperor Dynasty
#[[The First Dynasty of est]] - The Robot Factory Dynasty
#[[The Second Dynasty of Kevan]] - The Moreau Dynasty
#[[The First Dynasty of Damanor]] - The Galactic Dynasty
#[[The Third Dynasty of Kevan]] - The Thing Dynasty
#[[The First Dynasty of Cayvie]] - The Elemental Dynasty
#[[The First Dynasty of Joranj]] - The Mob Dynasty
#[[The First Dynasty of Keitalia]] - The Superhero Dynasty
#[[The First Dynasty of SatyrEyes]] - The Odyssey Dynasty
#[[The First Metadynasty]] - The Hat Meta-Dynasty
#[[The Second Dynasty of Cayvie]] - The Crashed Spaceship Dynasty
#[[The First Dynasty of Brendan]] - The Office Dynasty
#[[The Fourth Dynasty of Kevan]] - The Petri-Dish Dynasty
#[[The First Dynasty of Knightking]] - The Warlord Dynasty
#[[The First Dynasty of Chronos Phaenon]] - The Democratic Dynasty
#[[The First Dynasty of TrumanCapote]] - The Family Dynasty
#[[The Second Dynasty of Knightking]] - The Zombie Dynasty
#[[The First Dynasty of Quazie]] - The Muffin Dynasty
#[[The First Dynasty of Simon]] - The Surfer Dynasty
#[[The First Dynasty of AngryGrasshopper]] - The Spaceship Dynasty
#[[The First Dynasty of Rodney]] - The Illuminati Dynasty
#[[The First Dynasty of Aaron]] - The Athenian Dynasty
#[[The Second Dynasty of Josh]] - The Gaming Dynasty
#[[The Second Metadynasty]] - The Switch Dynasty
#[[The Second Dynasty of Chronos Phaenon]] - The Hegemonic Dynasty
#[[The First Dynasty of Excalabur]] - The Deity Dynasty
#[[The Second Dynasty of Excalabur]] - The Schizophrenic Dynasty
#[[The First Dynasty of 75th Trombone]] - The Text Adventure Dynasty
#[[The First Dynasty of Elias IX]] - The Pirate Dynasty
#[[The Third Metadynasty]] - The Gostak Metadynasty
#[[The Second Dynasty of Angry Grasshopper]] - The Monastic Murder Mystery Dynasty
#[[The First Dynasty of Hix]] - The Time Travelling Dynasty
#[[The First Dynasty of Thelonious]] - The Musical Dynasty
#[[The Second Dynasty of Elias IX]] - The Vegetable Dynasty
#[[The Second Dynasty of Rodney]] - The Miskatonic Dynasty
#[[The First Dynasty of Clucky]] - The Olympic Dynasty
#[[The First Dynasty of Doremi]] - The Hollywood Dynasty
#[[The Third Dynasty of Chronos Phaenon]] - The Iudex Dynasty
#[[The First Dynasty of Amnistar]] - The Secret Agent Dynasty
#[[The Second Dynasty of Clucky]] - The Spore Dynasty
#[[The Second Dynasty of Amnistar]] - The Goldberg Factory Dynasty
#[[The First Dynasty of Bucky]] - The Corporate Dynasty
#[[The Third Dynasty of Clucky]] - The Monkey Dynasty
#[[The Third Dynasty of Josh]] - The Kaiju Dynasty
#[[The Fifth Dynasty of Kevan]] - The Werewolf Dynasty
#[[The Second Dynasty of Hix]] - The Valkyrie Dynasty
#[[The First Dynasty of spikebrennan]] - The Wild West Poker Dynasty
#[[The First Dynasty of Jack]] - The Pirate vs Ninja Dynasty
#[[The First Dynasty of Purplebeard]] - The Evil Dynasty
#[[The First Dynasty of Rodlen]] - The Multi-Dimensional (and still evil) Dynasty
#[[The First Dynasty of Yoda]] - The RPG Dynasty
#[[The Third Dynasty of Amnistar]] - The Political Dynasty
#[[The First Dynasty of Darknight]] - The Dragon Dynasty
#[[The Second Dynasty of Bucky]] - The Barbarian Dynasty
#[[The Second Dynasty of Yoda]] - The Deja Vu Dynasty
#[[The Fourth Metadynasty]] - The First Metadynasty of Rodlen (Blo vs Gno vs Mic)
#[[The First Dynasty of arthexis]] - The Guess the Theme (Gourmet Drag Racing on Mars) Dynasty
#[[The Fourth Dynasty of Amnistar]] - The Military Dynasty
#[[The First Dynasty of Devenger]] - The Movie Body Count Dynasty
#[[The First Dynasty of ais523]] - The Reality TV Dynasty
#[[The First Dynasty of yuri_dragon_17]] - The Caribbean Vacation Dynasty
#[[The First Dynasty of Qwazukee]] - The Groundhog Day Dynasty
#[[The First Dynasty of Darth Cliche]] - The Post-Apocalyptic Dynasty
#[[The Fifth Metadynasty]] - The Original Game of Nomic Metadynasty
#[[The Third Dynasty of Bucky]] - The Runic Dynasty
#[[The First Dynasty of Wakukee]] - The Djinn Djinasty
#[[The Sixth Dynasty of Kevan]] - The Mansion Murder Dynasty
#[[The Second Dynasty of ais523]] - The Steampunk Dynasty
#[[The Fourth Dynasty of Josh]] - The April Fools Dynasty
#[[The Second Dynasty of Purplebeard]] - The Mining Camp Dynasty
#[[The Third Dynasty of ais523]] - The Election Dynasty
#[[The Second Dynasty of Ienpw III]] - The Undefined Term Dynasty
#[[The Second Dynasty of Darth Cliche]] - The NetHack Dynasty
#[[The First Dynasty of lilomar]] - The Paranoia Dynasty
#[[The First Dynasty of coppro]] - The Futurama Dynasty
#[[The Fourth Dynasty of ais523]] - The IQ Dynasty
#[[The Seventh Dynasty of Kevan]] - The Cold War Spy Dynasty
#[[The Second Dynasty of Brendan]] - The School of Witchcraft Dynasty
#[[The First Dynasty of Alecto]] - The Roman Gods Dynasty
#[[The Fifth Dynasty of Josh]] - The LEGO® Dynasty
#[[The Fourth Dynasty of Clucky]] - The Ant Dynasty
#[[The Third Dynasty of Purplebeard]] - The Prehistoric Dynasty
#[[The Eighth Dynasty of Kevan]] - The Mornington Crescent Dynasty
#[[The Fifth Dynasty of ais523]] - The Sheep Dynasty
#[[The Fourth Dynasty of Purplebeard]] - The Stock Market Dynasty
#[[The Third Dynasty of Yoda]] - The Plants vs Zombies Dynasty
#[[The Fourth Dynasty of Bucky]] - The ClingBoom Arena Dynasty
#[[The Ninth Dynasty of Kevan]] - The Lifeboat Dynasty
#[[The First Dynasty of Bateleur]] - The Art Dynasty
#[[The Sixth Metadynasty]] - The Today's Economy Dynasty
#[[The Second Dynasty of coppro]] - The Taxicab Dynasty
#[[The Sixth Dynasty of ais523]] - The Petty Crime Dynasty
#[[The First Dynasty of Cpt_Koen]] - The Band Dynasty
#[[The First Dynasty of southpointingchariot]] - The Ansible Dynasty
#[[The Sixth Dynasty of Josh]] - The Visiting the Past Dynasty
#[[The Third Machine of scshunt]] - The Factory Machine Dynasty
#[[The First Dynasty of Quirck]] - The Manul Dynasty
#[[The Fifth Dynasty of Clucky]] - The Pie Dynasty
#[[The Fifth Dynasty of Bucky]] - The Nomic School Dynasty
#[[The Tenth Dynasty of Kevan]] - The Newspaper Dynasty
#[[The Seventh Dynasty of Josh]] - The Heist Dynasty
#[[The Eleventh Dynasty of Kevan]] - The Doomsday Cult Dynasty
#[[The Fourth Dynasty of scshunt]] - The Dynasty of the Commons
#[[The First Dynasty of RaichuKFM]] - The Interstellar Fleet Dynasty
#[[The First Dynasty of Larrytheturtle]] - The Noble Families Dynasty
#[[The First Dynasty of Skju]] - The Principia Blognomica Dynasty
#[[The Seventh Metadynasty]]
#[[The Fifth Dynasty of Purplebeard]] - The Magical Apprentice Dynasty
#[[The First Dynasty of Spitemaster]] - The Government Shutdown Dynasty
#[[The Eighth Dynasty of Josh]] - The Despot Dynasty
#[[The Second Dynasty of RaichuKFM]] - The Marooned Dynasty
#[[The First Dynasty of The Alien]] - The Alien NPC Dynasty
#[[The First Dynasty of Benzene]] - The Chemistry Dynasty
#[[The Third Dynasty of RaichuKFM]] - The Chivalric Dynasty
#[[The Sixth Dynasty of Purplebeard]] - The Assassin Dynasty
#[[The Twelfth Dynasty of Kevan]] - The Attic Clearance Dynasty
#[[The First Dynasty of Ayesdeeef]] - The Soccer Dynasty
#[[The Sixth Dynasty of Bucky]] - The Jupiter Shuttle Dynasty
#[[The Thirteenth Dynasty of Kevan]] - The Android Dynasty
#[[The Ninth Dynasty of Josh]] - The Seasonal Dynasty
#[[The First Dynasty of Mideg]] - The Restaurant Dynasty
#[[The Fourteenth Dynasty of Kevan]] - The Shapeshifter Dynasty
#[[The Third Dynasty of Brendan]] - The Kaiju Court Dynasty
#[[The Fifteenth Dynasty of Kevan]] - The Mad Max Diplomacy Dynasty
#[[The First Dynasty of Tantusar]] - The Lab Rat Dynasty
</div>

==Archive==

===Older Core Game Documents===

''Add new Documents to the top of the list at the end of each dynasty.''

[[The Maze]], [[The Wasteland]], [[Cooking Equipment]], [[Orbit Contents]], [[Hivemind Charters]], [[Market Values]], [[Second-Hand Goods]], [[Space]], [[Reagents]], [[Sequester]], [[Spellbook]], [[Question]], [[Truths]], [[Peerage]], [[Feuds]], [[Tournaments]], [[Galaxy Map]], [[The Hangar]], [[Garage]], [[Fence]], [[The Whiteboard]], [[Factory Floor]], [[Machines]], [[Routes]], [[The Arena]], [[Garden Patch]], [[Gardening Compendium]], [[Species Compendium]], [[BN Index]], [[Check before you travel]], [[Photo Albums]], [[Research projects]], [[Trails]], [[Toybox]], [[Mortals]], [[Teachers]], [[Berlin map]], [[The Dossier]], [[Trading Post]], [[Inventions]], [[County Activity]], [[Wodehouse surnames]], [[Corporations]], [[List of forms]], [[Code of Conduct]], [[I|Inventory]], [[Loot]], [[My dynasty]], [[Stockpile]], [[Settlement]] ([http://blognomic.appspot.com/purplebeard-2/settlement Script version]), [[Inventions]], [[Trading Post]], [[County Activity]], [[Universe]], [[Inventory Items]], [[City]], [[Good Deeds]], [[Parallel Ruleset]], [[Rewards]], [[Diary Entries]], [[:Category:Acts of Dynasty 64]], [[Action Props]], [[List of American film actors]], [[Bonus Features]], [[Theme Hints]], [[Ingredients]], [[The Table]], [[Recipes]], [[Vehicles]], [[Solar Map]], [[Faction BLO Ruleset]], [[Faction GNO Ruleset]], [[Faction MIC Ruleset]], [[Gnomish Scrolls]], [[Plot Summary]], [[Locations]], [[Occupations]], [[Backpack]], [[Dragon Eggs]], [[Candidate Agendas]], [[Planar Entities]], [[Space Tech]], [[Spacecraft Register]], [[Member Dossiers]], [[Earth]], [[Storage Zone]], [[Doomsday Device]], [[Treasures Page]], [[Sea Monsters]], [[Wanted Poster|Wanted Posters]], [[Poker Hands]], [[Old Rulesets]], [[The Creature Page]], [[List of Traits]], [[List of Events]], [[Filmographies]], [[Threads]], [[Deity Wiki]], [[Cities]], [[Monastery of St. Passignano Map]], [[Timeline|The Timeline]], [[Zodiac Wiki]], [[The Lost List]], [[Events Page]], [[Events_Page]], [[Motions]], [[Mystical Chant]], [[Chant Regulations]], [[List of Gadgets]], [[Missions]], [[Gadget Requests]], [[List of Approved Gadgets]], [[List of In-play Gadgets]], [http://blognomic.com/archive/cant_see_map/ The Map], [[Legend]], [[Inventory]], [[Monkey Dynasty Gamestate Documents]], [[The City]], [[The Media Circus]], [[Monster Roster]], [[Book of the Kaiju]], [[Einherjar]], [[About non-metallic mineral resources in China]], [[Character Sheets]], [[Quest Journal]], [[Item List]]

===Proposed Core Game Documents Substitutes===
*[[Ruleset Draft]]
*[[Talk:Ruleset Draft]]
*[[Ruleset Draft, Take Two]]
*[[Ruleset Draft, the Third]]

=== Switch to blognomic.com (2005) ===

*[[Switch suggestions]]
*[[Switch plans]]
*[[Switch guidebook]]

The Maze

2015-07-31T11:57:08Z

Purplebeard: Reverting Cheese Spawn (cannot be completed without setting Josh's Cheese to an illegal value)

[[File:Maze.png]]

{| class="wikitable" style="text-align:center; vertical-align:middle;"
|-
|style="width:20px; height:20px"| ||style="width:100px;"| '''A''' ||style="width:100px;"| '''B''' ||style="width:100px;"| '''C''' ||style="width:100px;"| '''D''' ||style="width:100px;"| '''E''' ||style="width:100px;"| '''F''' ||style="width:100px;"| '''G'''
|-
| style="height:100px;" |'''1'''|| Cheese Spawner, PUP || Empty || Empty || Empty || DAR || Empty || Cheese Spawner, EVA
|-
| style="height:100px;" |'''2'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''3'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''4'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''5'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''6'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''7'''|| [[File:For_icon.jpg]] Cheese Spawner, JOS || Empty || Empty || Empty || Empty || Empty || Cheese Spawner
|}

Ruleset

2015-07-30T07:06:38Z

Purplebeard: /* Movement */ Enacting "Back and Forth"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Rats shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Rats may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Rats ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Rat'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Rat.

A Rat may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Rat may not rejoin the game within two weeks after having left. A Rat may only change their name as a result of a proposal approving the change.

Some Rats are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Rats who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Rats===

Some Rats are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Rats”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Rats are not counted as Rats.

If a Proposal contains a provision that targets a specifically named Idle Rat, then that Idle Rat is considered to be Unidle solely for the purposes of enacting that specific provision

When a Rat is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Rat Idled in a different dynasty), the Rat is given the default value for new Rat, if such a value exists.

An Admin may render a Rat Idle if that Rat has asked to become Idle in an entry or comment from the past four days, or if that Rat has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Rat if that Rat has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Rat who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Rat, known as the Head Scientist. If there is no Head Scientist, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Rats may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Rat may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Rat’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Rat never has a Vote, even if they were a Rat previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Rat may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Rat already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Rat casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Head Scientist may use VETO as a voting icon to cast a Vote on a proposal; when the Head Scientist casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Head Scientist later changes their Vote.

If a Rat other than the Head Scientist casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Head Scientist. When the Head Scientist has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Head Scientist's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Rats who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Rats actively disagree as to the interpretation of the Ruleset, or if a Rat feels that an aspect of the game needs urgent attention, then any Rat may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Rat (other than the Head Scientist) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Rats”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Rat may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Head Scientist has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Rats who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Rat who made the DoV as its Head Scientist. That Rat may pass this role to another Rat at this point by making a post to that effect, if they wish. The Hiatus continues until the new Head Scientist makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Head Scientist's chosen theme for the new Dynasty, and may optionally specify that the terms Rat and Head Scientist 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Rat who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Rat's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Rat within BlogNomic.
* A Rat should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Rat should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Rat should not edit their own blog comments once posted, nor those of any other Rat.
* A Rat should not edit the "Entry Date" field of a blog post.
* A Rat should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Rat should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

== Test Conditions ==

Unless explicitly stated, the Head Scientist does not count as a Rat for the purposes of the Dynastic Rules.

Each Rat has a Code, that they may set at any time, consisting of any three letters of their name, in all-caps, tracked in the GNDT. Their Code must be unique among other existing Codes. If they do not have a Code, they may not perform any other actions as defined by the Dynastic Rules. When a Rat sets their Code for the first time, they must add it to Cell D4.

Each Rat has an amount of Cheese, tracked in the GNDT, which defaults to 3, and must be a number between 1 and 5, inclusive.

== The Maze ==

The Great Test takes place in The Maze, which is tracked on the wiki page [[The Maze]].

The Maze is a maze of dimensions 7 Cells by 7 Cells. Each Cell has a set of coordinates with the letters A through G representing the Column and the numbers 1 through 7 representing the Row, with the top left Cell being Cell A1, and the bottom right Cell being Cell G7.

Each Rat has a Position in The Maze, tracked on the wiki page [[The Maze]] in the table after the image of The Maze using their Code, which defaults to Cell D4.

The black lines on the map of the Maze are Walls. The blue and red lines are Conduits, which are a type of Wall.

===Movement===

As a Daily Action, a Rat may Progress exactly X times, where X is the amount of Cheese that Rat has. When a Rat Progresses, it may either:-

*'''Scamper''': move any number of Cells in a cardinal direction, so long as this move does not pass through any walls.
*'''Crawl''': move from A4 to G4 (or vice versa) or from D1 to D7 (or vice versa).

== Scientist's Notes ==

Any Rat, including the Head Scientist, may include a Scientist’s Note in a Proposed Rule, prefaced as such and in italics, which may include an example or other explanatory text. When the containing Proposal is enacted, the Scientist’s Note should be included, verbatim, in the relevant part of the Dynastic Rules. A Scientist’s Note should not contain flavour justifications or any other text irrelevant to the Rule it is in. While a Scientist’s Note does not have any actual bearing on the Rules, it may be used in the case that the intended meaning of a Rule is brought into question.

''Scientist’s Note: This is an example of a correctly formatted Scientist’s Note''

== Learning ==

Each Rat has an amount of Learning, which is tracked in the GNDT and is an integer that defaults to zero.

== Hypothesis ==

A Hypothesis is a prediction about the behaviour of Rats in the coming week. A Hypothesis must be specific and measurable - it must contain one or more behaviours or actions that all Rats or a specific subset of Rats can carry out, and the number of times (or range of numbers of times) that each behaviour is Hypothesised to occur. A Rat may never be the subject of its own Hypothesis, and Rats are not considered to be Rats or part of any subset of Rats for the purposes of a Hypothesis that they have made.

As a weekly action, any Rat can make a Hypothesis by sending a PM to the Head Scientist detailing their Hypothesis and by making a story post to the blog announcing that a Hypothesis has been formed (but not detailing its specifics). The Head Scientist should, as soon as possible thereafter, respond to that Rat with a Significance for their Hypothesis. The Significance of a Hypothesis is a value reflecting how likely the Head Scientist thinks it is to come about, on a scale of 0 to 10, where 0 is “certain” and 10 is “impossible”.

As soon as possible thereafter, but not sooner than 7 days after the posting of the relevant story post, a Rat who formed a Hypothesis may Evaluate it by making a further story post with the detailed terms of their Hypothesis and the results of their Evaluation. A Hypothesis may be Evaluated as Successful if the terms of that Hypothesis have been met completely and in their entirety. Otherwise, it is Unsuccessful. If a Hypothesis is Evaluated to be Successful, the Hypothesising Rat may once increase their Learning by the Significance of their Hypothesis.

== Spawners ==

===Cheese Spawners===

There are Cheese Spawners in Cells A1, A7, G7 and G1. When a Rat is in the same Cell as an Active Cheese Spawner, they may complete all or none of the following actions:

* Add 1 Cheese to their total Cheese
* Deactivate the Cheese Spawner in the Cell they are in
* Activate the next Cheese Spawner in clockwise order
''Scientist’s Note: In other words, the activation order is A1, A7, G7, G1, and then repeats.''

The position of the current Active Cheese Spawner is marked using [[File:For icon.jpg]] in the table on the page [[The Maze]].

==Tests==

Each Rat has a Success Rate, tracked in the GNDT, which defaults to 5, and must be a number between 0 and 10, inclusive.

At any time, the Head Scientist may set a '''Test''', by making a Story Post with “Test: ” at the start of its title. This post should include:

* A Task
* A Reward
* A Punishment
* An Acceptance Deadline
* A Completion Deadline

Any Rat may accept a Test by commenting on its post with an ARROW before the Acceptance Deadline.

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.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Rats.

;Daily Action
:If a game action is a Daily Action, each Rat able to perform it may take that action once each day, but not more than once every ten hours.

;Daily Communal Action
:A Daily Communal Action is a Daily Action that can only be performed by one Rat per day.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Rat’s Effective Vote Comment with respect to a given Votable Matter means that Rat’s Comment to that Votable Matter, if any, that contains that Rat’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Rat may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Rats is half the number of Rats in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Rats it is referring to, it is referring to a Quorum of all Rats.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Rat able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Rat per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Rat may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Rat has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Rat may update any Rat's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Rat may correct the GNDT to comply with the Gamestate.

If a Rat feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Rats are encouraged to raise a Call for Judgement instead.
Rats shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Rat with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Rats to transfer a numeric value only allows them to transfer that value from themselves to another Rat (of their choice unless otherwise stated).
* A Rat who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Rat A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a Rat if it is explicitly stated that it refers to a Rat's name.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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 “Rats may Kick each other” and “Rats may not kick each other on Tuesdays” exist, and it is Tuesday, Rats may not Kick each other.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Rats may Punch a Spaceman on Friday” and “Rats may not Punch Spacemen on Friday”, then Rats may not Punch Spacemen on Friday.)

</div>

The Maze

2015-07-30T07:03:51Z

Purplebeard: Scamperx4, take Cheese

[[File:Maze.png]]

{| class="wikitable" style="text-align:center; vertical-align:middle;"
|-
|style="width:20px; height:20px"| ||style="width:100px;"| '''A''' ||style="width:100px;"| '''B''' ||style="width:100px;"| '''C''' ||style="width:100px;"| '''D''' ||style="width:100px;"| '''E''' ||style="width:100px;"| '''F''' ||style="width:100px;"| '''G'''
|-
| style="height:100px;" |'''1'''|| Cheese Spawner, PUP || Empty || Empty || Empty || EVA,DAR || Empty || [[File:For_icon.jpg]] Cheese Spawner
|-
| style="height:100px;" |'''2'''|| Empty || Empty || JOS || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''3'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''4'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''5'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''6'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''7'''|| Cheese Spawner || Empty || Empty || Empty || Empty || Empty || Cheese Spawner
|}

The Maze

2015-07-28T20:11:25Z

Purplebeard:

[[File:Maze.png]]

{| class="wikitable" style="text-align:center; vertical-align:middle;"
|-
|style="width:20px; height:20px"| ||style="width:100px;"| '''A''' ||style="width:100px;"| '''B''' ||style="width:100px;"| '''C''' ||style="width:100px;"| '''D''' ||style="width:100px;"| '''E''' ||style="width:100px;"| '''F''' ||style="width:100px;"| '''G'''
|-
| style="height:100px;" |'''1'''|| [[File:For_icon.jpg]] Cheese Spawner || Empty || Empty || Empty || EVA || Empty || Cheese Spawner
|-
| style="height:100px;" |'''2'''|| Empty || Empty || JOS,PUP || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''3'''|| Empty || Empty || Empty || Empty || DAR || Empty || Empty
|-
| style="height:100px;" |'''4'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''5'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''6'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''7'''|| Cheese Spawner || Empty || Empty || Empty || Empty || Empty || Cheese Spawner
|}

The Maze

2015-07-27T07:54:10Z

Purplebeard: Entering, and Scampering three times

[[File:Maze.png]]

{| class="wikitable" style="text-align:center; vertical-align:middle;"
|-
|style="width:20px; height:20px"| ||style="width:100px;"| '''A''' ||style="width:100px;"| '''B''' ||style="width:100px;"| '''C''' ||style="width:100px;"| '''D''' ||style="width:100px;"| '''E''' ||style="width:100px;"| '''F''' ||style="width:100px;"| '''G'''
|-
| style="height:100px;" |'''1'''|| [[File:For_icon.jpg]] Cheese Spawner || Empty || Empty || Empty || EVA,PUP || Empty || Cheese Spawner
|-
| style="height:100px;" |'''2'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''3'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''4'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''5'''|| Empty || Empty || Empty || Empty || Empty || Empty || Empty
|-
| style="height:100px;" |'''6'''|| Empty || Empty || Empty || JOS,DAR || Empty || Empty || Empty
|-
| style="height:100px;" |'''7'''|| Cheese Spawner || Empty || Empty || Empty || Empty || Empty || Cheese Spawner
|}

Ruleset

2015-07-03T08:04:37Z

Purplebeard: /* Tribes */ Removing errant blockquote tag.

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Tribes shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Tribes may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Tribes ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Tribe'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Tribe.

A Tribe may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Tribe may not rejoin the game within two weeks after having left. A Tribe may only change their name as a result of a proposal approving the change.

Some Tribes are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Tribes who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Tribes===

Some Tribes are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Tribes”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Tribes are not counted as Tribes.

If a Proposal contains a provision that targets a specifically named Idle Tribe, then that Idle Tribe is considered to be Unidle solely for the purposes of enacting that specific provision

When a Tribe is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Tribe Idled in a different dynasty), the Tribe is given the default value for new Tribe, if such a value exists.

An Admin may render a Tribe Idle if that Tribe has asked to become Idle in an entry or comment from the past four days, or if that Tribe has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Tribe if that Tribe has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Tribe who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first EVC following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Tribe, known as the Nomad. If there is no Nomad, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Tribes may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Tribe may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Tribe’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Tribe never has a Vote, even if they were a Tribe previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Tribe may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Tribe already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Tribe casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Nomad may use VETO as a voting icon to cast a Vote on a proposal; when the Nomad casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Nomad later changes their Vote.

If a Tribe other than the Nomad casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Nomad. When the Nomad has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Nomad's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Tribes who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Tribes actively disagree as to the interpretation of the Ruleset, or if a Tribe feels that an aspect of the game needs urgent attention, then any Tribe may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Tribe (other than the Nomad) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Tribes”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Tribe may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Nomad has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Tribes who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Tribe who made the DoV as its Nomad. That Tribe may pass this role to another Tribe at this point by making a post to that effect, if they wish. The Hiatus continues until the new Nomad makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Nomad's chosen theme for the new Dynasty, and may optionally specify that the terms Tribe and Nomad 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Tribe who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Tribe's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Tribe within BlogNomic.
* A Tribe should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Tribe should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Tribe should not edit their own blog comments once posted, nor those of any other Tribe.
* A Tribe should not edit the "Entry Date" field of a blog post.
* A Tribe should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Tribe should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==Tribes==

A number of Tribes populate the desolate wasteland. Each Tribe has a Name, tracked in the GNDT. If a Tribe has no Name, it may give itself one at any time. A Tribe without a Name may not take any actions outside of this rule in the dynastic ruleset.

==Zones of the Wasteland==

A number of Zones exist in the Wasteland, each of which has a name and which may be occupied by a single Tribe. This is tracked as a grid in the wiki page [[The Wasteland]]. Zones which are orthogonally adjacent on the grid of that page are considered to be "adjacent".

If a Tribe has no Zones, it may choose any unoccupied Zone and occupy it, by updating the wiki page to this effect.

==Convoys==

A Tribe may start a Convoy by posting a blog entry whose title begins “Convoy:”, if that Tribe does not already have an active Convoy. This is known as a Convoy Post, the Tribe who posted it is its Driver, and the entity it describes is a Convoy, which becomes active when posted.

A Convoy Post must contain an ordered list of three or more different Zones. This is known as its Convoy’s Route. The first Zone in the Route must belong to the Tribe that made the post. Each active Convoy has a Position, which defaults to the second Zone on its Route.

If the Position of a Convoy is an unoccupied Zone, the Driver of that Convoy may change its Position to the next Zone on its Route, by posting a comment to this effect.

If the Position of a Convoy is a Zone occupied by a Tribe, that Tribe may change the Convoy’s Position to the next Zone on its Route, by posting a comment to this effect.

If a Convoy’s Position is the final Zone of its Route, it ceases to be active.

<br/>
<div style="padding:8px;background:#ddd;">

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Tribes.

;Daily Action
:If a game action is a Daily Action, each Tribe able to perform it may take that action once each day, but not more than once every ten hours.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Tribe’s Effective Vote Comment with respect to a given Votable Matter means that Tribe’s Comment to that Votable Matter, if any, that contains that Tribe’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Tribe may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Tribes is half the number of Tribes in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Tribes it is referring to, it is referring to a Quorum of all Tribes.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Tribe able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Tribe per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Tribe may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Tribe has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Tribe may update any Tribe's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Tribe may correct the GNDT to comply with the Gamestate.

If a Tribe feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Tribes are encouraged to raise a Call for Judgement instead.
Tribes shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Tribe with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Tribes to transfer a numeric value only allows them to transfer that value from themselves to another Tribe (of their choice unless otherwise stated).
* A Tribe who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Tribe A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a Tribe if it is explicitly stated that it refers to a Tribe's name.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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 “Tribes may Kick each other” and “Tribes may not kick each other on Tuesdays” exist, and it is Tuesday, Tribes may not Kick each other.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Tribes may Punch a Spaceman on Friday” and “Tribes may not Punch Spacemen on Friday”, then Tribes may not Punch Spacemen on Friday.)

</div>

Template:Dynastic Histories

2014-06-14T11:09:15Z

Purplebeard:

{| cellpadding="4" align = "center" style="margin:24px 8px 8px 8px; border:2px solid #006;border-collapse: collapse; width: 75%;"
|-
|style="background-color:#006; text-align:center; width:5%; color: #FFF;" | <h3 style="border: none; color: #FFF;">Dynastic Histories</h3>
|-
|style="background-color:#fff; text-align:center; width:95%; color:#006; font-size: 8pt;" |
[[Round One]] -
[[The First Dynasty of Myke]] -
[[The First Dynasty of Lyndse]] -
[[The First Dynasty of Geran / The Second Dynasty of Myke|The Second Dynasty of Myke]] -
[[The First Dynasty of Kevan]] -
[[The First Dynasty of Anthony]] -
[[The First Dynasty of est]] -
[[The Second Dynasty of Kevan]] -
[[The First Dynasty of Damanor]] -
[[The Third Dynasty of Kevan]] -
[[The First Dynasty of Cayvie]] -
[[The First Dynasty of Joranj]] -
[[The First Dynasty of Keitalia]] -
[[The First Dynasty of SatyrEyes]] -
[[The First Metadynasty]] -
[[The Second Dynasty of Cayvie]] -
[[The First Dynasty of Brendan]] -
[[The Fourth Dynasty of Kevan]] -
[[The First Dynasty of Knightking]] -
[[The First Dynasty of Chronos Phaenon]] -
[[The First Dynasty of TrumanCapote]] -
[[The Second Dynasty of Knightking]] -
[[The First Dynasty of Quazie]] -
[[The First Dynasty of Simon]] -
[[The First Dynasty of AngryGrasshopper]] -
[[The First Dynasty of Rodney]] -
[[The First Dynasty of Aaron]] -
[[The Second Dynasty of Josh]] -
[[The Second Metadynasty]] -
[[The Second Dynasty of Chronos Phaenon]] -
[[The First Dynasty of Excalabur]] -
[[The Second Dynasty of Excalabur]] -
[[The First Dynasty of 75th Trombone]] -
[[The First Dynasty of Elias IX]] -
[[The Third Metadynasty]] -
[[The Second Dynasty of Angry Grasshopper]] -
[[The First Dynasty of Hix]] -
[[The First Dynasty of Thelonious]] -
[[The Second Dynasty of Elias IX]] -
[[The Second Dynasty of Rodney]] -
[[The First Dynasty of Clucky]] -
[[The First Dynasty of Doremi]] -
[[The Third Dynasty of Chronos Phaenon]] -
[[The First Dynasty of Amnistar]] -
[[The Second Dynasty of Clucky]] -
[[The Second Dynasty of Amnistar]] -
[[The First Dynasty of Bucky]] -
[[The Third Dynasty of Clucky]] -
[[The Third Dynasty of Josh]] -
[[The Fifth Dynasty of Kevan]] -
[[The Second Dynasty of Hix]] -
[[The First Dynasty of spikebrennan]] -
[[The First Dynasty of Jack]] -
[[The First Dynasty of Purplebeard]] -
[[The First Dynasty of Rodlen]] -
[[The First Dynasty of Yoda]] -
[[The Third Dynasty of Amnistar]] -
[[The First Dynasty of Darknight]] -
[[The Second Dynasty of Bucky]] -
[[The Second Dynasty of Yoda]] -
[[The Fourth Metadynasty]] -
[[The First Dynasty of arthexis]] -
[[The Fourth Dynasty of Amnistar]] -
[[The First Dynasty of Devenger]] -
[[The First Dynasty of ais523]] -
[[The First Dynasty of yuri_dragon_17]] -
[[The First Dynasty of Qwazukee]] -
[[The First Dynasty of Darth Cliche]] -
[[The Fifth Metadynasty]] -
[[The Third Dynasty of Bucky]] -
[[The First Dynasty of Wakukee]] -
[[The Sixth Dynasty of Kevan]] -
[[The Second Dynasty of ais523]] -
[[The Fourth Dynasty of Josh]] -
[[The Second Dynasty of Purplebeard]] -
[[The Third Dynasty of ais523]] -
[[The Second Dynasty of Ienpw III]] -
[[The Second Dynasty of Darth Cliche]] -
[[The First Dynasty of lilomar]] -
[[The First Dynasty of coppro]] -
[[The Fourth Dynasty of ais523]] -
[[The Seventh Dynasty of Kevan]] -
[[The Second Dynasty of Brendan]] -
[[The First Dynasty of Alecto]] -
[[The Fifth Dynasty of Josh]] -
[[The Fourth Dynasty of Clucky]] -
[[The Third Dynasty of Purplebeard]] -
[[The Eighth Dynasty of Kevan]] -
[[The Fifth Dynasty of ais523]] -
[[The Fourth Dynasty of Purplebeard]] -
[[The Third Dynasty of Yoda]] -
[[The Fourth Dynasty of Bucky]] -
[[The Ninth Dynasty of Kevan]] -
[[The First Dynasty of Bateleur]] -
[[The Sixth Metadynasty]] -
[[The Second Dynasty of coppro]] -
[[The Sixth Dynasty of ais523]] -
[[The First Dynasty of Cpt_Koen]] -
[[The First Dynasty of southpointingchariot]] -
[[The Sixth Dynasty of Josh]] -
[[The Third Machine of scshunt]] -
[[The First Dynasty of Quirck]] -
[[The Fifth Dynasty of Clucky]] -
[[The Fifth Dynasty of Bucky]] -
[[The Tenth Dynasty of Kevan]] -
[[The Seventh Dynasty of Josh]] -
[[The Eleventh Dynasty of Kevan]] -
[[The Fourth Dynasty of scshunt]] -
[[The First Dynasty of RaichuKFM]] -
[[The First Dynasty of Larrytheturtle]] -
[[The First Dynasty of Skju]] -
[[The Seventh Metadynasty]] -
[[The Fifth Dynasty of Purplebeard]] -
[[The First Dynasty of Spitemaster]] -
[[The Eighth Dynasty of Josh]] -
[[The Second Dynasty of RaichuKFM]] -
[[The First Dynasty of The Alien]] -
[[The First Dynasty of Benzene]] -
[[The Sixth Dynasty of Purplebeard]] -
|}

The Third Dynasty of RaichuKFM

2014-06-14T11:06:32Z

Purplebeard:

'''May 6, 2014 - June 14, 2014'''

== Ascension Address ==
A lone flask sits bubbling, but something pans out, leaving a wrecked lab, up through a hole in a crashed ship, past an assortment of odd creatures, now through the layers of clouds and gas swaddling a lone planet, further out, past a giant flare, zooming further out until its view is of a large milky spiral. And now it tips downward, and alights on the eyes of a stargazer staring at the field of lights. Suddenly the view is obscured by a great beast swooping down from the sky, and the viewer runs to shelter as sounds of marching boots emanate from the near castle. A barrage of arrows emerge from various points on the ground, and the creature turns and flees, projectiles trailing behind it, roaring all the time. Several figures in rusting chainmail breathe sighs of relief, and head back to inform their ailing lord of the news.

==Players==
The following players were active at the end of the Dynasty:

ayesdeeef, Excalabur*, IceFromHell, Kevan*, Larrytheturtle*, Purplebeard*, PTSnoop_, RaichuKFM*, rainbowkitten408, Rodney*, TheChosenOne, Sfarbs

==Final Ruleset==
[[Ruleset 119]]

==Posts of Interest==

==Ascension==

{{Dynastic Histories}}

Ruleset 119

2014-06-14T10:19:31Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Knights shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Knights may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Knights ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be an '''Knight'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Knight.

A Knight may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Knight may not rejoin the game within two weeks after having left. A Knight may only change their name as a result of a proposal approving the change.

Some Knights are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Knights who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Knights===

Some Knights are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Knights”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Knights are not counted as Knights.

If a Proposal contains a provision that targets a specifically named Idle Knight, then that Idle Knight is considered to be Unidle solely for the purposes of enacting that specific provision

When a Knight is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Knight Idled in a different dynasty), the Knight is given the default value for new Knight, if such a value exists.

An Admin may render a Knight Idle if that Knight has asked to become Idle in an entry or comment from the past four days, or if that Knight has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Knight if that Knight has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Knight who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Admins who are unidling themselves should, in their first EVC following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Knight, known as the Baron. If there is no Baron, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Knights may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Knight may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Knight’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Knight never has a Vote, even if they were a Knight previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Knight may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Knight already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Knight casts an explicit vote AGAINST their own Proposal, this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Baron may use VETO as a voting icon to cast a Vote on a proposal; when the Baron casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Baron later changes their Vote.

If a Knight other than the Baron casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Baron. When the Baron has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Baron's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Knights who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Knights actively disagree as to the interpretation of the Ruleset, or if a Knight feels that an aspect of the game needs urgent attention, then any Knight may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Knight (other than the Baron) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Knights”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Knight may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Baron has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Knights who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Knight who made the DoV as its Baron. That Knight may pass this role to another Knight at this point by making a post to that effect, if they wish. The Hiatus continues until the new Baron makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Baron's chosen theme for the new Dynasty, and may optionally specify that the terms Knight and Baron 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, the Knight who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Knight's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Knight within BlogNomic.
* A Knight should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Knight should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Knight should not edit their own blog comments once posted, nor those of any other Knight.
* A Knight should not edit the "Entry Date" field of a blog post.
* A Knight should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Knight should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==Currency==
Every Knight has an amount of Gold, tracked in the GNDT and defaulting to 40.

==Equipment==
A Knight may Wield Items, tracked in the GNDT under ‘Wielding’. A Knight may Wield up to two one-handed Items, or may Wield one two-handed Item, but may not Wield both a one-handed and a two-handed Item. Items that are neither one-handed nor two-handed may not be Wielded.

Knights may possess other Items, listed in the GNDT under ‘Inventory’. Valid Items are listed as the names of subrules to this rule, with the number in brackets after their name being that item’s Cost. At any time, a Knight may stop Wielding an Item to move it to their Inventory, or may remove an Item from their Inventory to Wield it. If a Knight has four or more Items in their Inventory, then they may neither Purchase Items nor move any Wielded Item to their Inventory. A Knight may discard an Item from their Inventory at any time.

New Knights start out Wielding a Shortsword and with an empty Inventory.

Some Items are Unique, signified by adding “(Unique)” after their name instead of a Cost. Unique Items have no Cost and may not be Purchased or Sold. Only one instance of each Unique Item may exist. Unique Items may be possessed by Beasts as well as Knights; if a Unique Item is held by a Beast, its status is tracked in the rule corresponding to that Beast.

===Shortsword (8)===
The Shortsword is a one-handed Swift Weapon.

===Mace (12)===
The Mace is a one-handed Blunt Weapon.

===Buckler (25)===

The Buckler is a one-handed Shield.

===Bow (18)===

The Bow is two-handed. If a Knight Wielding a Bow also has a Quiver in their Inventory, the Bow is a Ranged Weapon.

===Quiver (28)===

===Battle Axe(16)===

The Battle Axe is a two-handed Heavy Weapon.

===Runehammer (Unique)===

The Runehammer is a one-handed Heavy Blunt Weapon.

===Standard (Unique)===

The Standard of Nomicshire is a symbol of the Baron’s authority over the land. The Standard is one-handed.

If the Knight who Wields the Standard has cast a vote (the "Standard Vote") on a Proposal which the Baron has not cast a vote, then the Baron's vote on that Proposal is considered to be the same as that of the Proposal's Standard Vote.

===Dragonsteel Plate (Unique)===

A Knight who holds the Dragonsteel Plate in their Inventory is treated as if they were Wielding a Shield.

===Great Crossbow (Unique)===

The Great Crossbow is a two-handed Heavy Ranged Weapon.

===Dagger (10)===

The Dagger is a one-handed Swift, Ranged Weapon. At the end of any Skirmish whose result would have been different if Daggers were not Ranged, all Wielded Daggers are removed from play. At the end of any Attack whose result would have been different if Daggers were not Ranged, all Daggers Wielded by Attacking Knights in that Attack are removed from play.

===Steed (10)===
A Knight who has a Steed in their Inventory is Mounted.

===Lance (10)===

The Lance is one-handed. If a Knight who Wields a Lance is Mounted, that Lance is a Heavy Weapon and is counted as two Weapons for the purposes of Approach posts.

===Cursed Flail (Unique)===

The Cursed Flail is a one-handed, Swift, Heavy, Blunt Weapon. A Knight who is Wielding the Cursed Flail may not take an action that would move it to their Inventory.

==Beasts==

Various Beasts stalk the land, and are described in subrules of this rule. Each Beast has a Motive, a Behaviour and an amount of Fortitude. If no Assault has taken place in the last 24 hours, any Knight may resolve an Assault by selecting a non-Slain Beast at random and, if its Motive is not currently met, applying the effects of its Behaviour, once.

===Dragon===

The Dragon’s Motive is to amass a Hoard of 1000 Gold. The Dragon’s Hoard is tracked in this sentence, and is currently 637 Gold.

The Dragon’s Behaviour is to select a non-Slain Beast at random (excluding itself) and to reduce that Beast’s Fortitude by DICE6. If this would reduce the Beast’s Fortitude to zero or lower, that Beast is instead Slain, any Unique Items it holds are moved to the Dragon and ‘Slain by Dragon’ is added to that Beast’s Rule. Otherwise the Dragon’s Hoard is increased by the result of the die roll multiplied by quorum. If there are no non-Slain Beasts other than the Dragon, this Behaviour has no effect.

The Dragon’s Fortitude is 25.

Slain by: Purplebeard, IceFromHell, Rodney, rainbowkitten408, TheChosenOne (attack) and Kevan (scout).

===Gryphon===

The Gryphon’s Motive is to hold four or more Unique Items.

The Gryphon’s Behaviour is to select a random Knight who possesses at least one Unique Item and, if that Knight is not Wielding a Ranged Weapon and/or a Shield, moving a random Unique Item from that Knight’s possession to the Gryphon. If no Unique Items are possessed by Knights, the Gryphon’s Behaviour has no effect.

The Gryphon’s Fortitude is 10.

Slain by: Kevan, Purplebeard, Rodney, IceFromHell.

===Minotaur===

The Minotaur’s Motive is for the Knights to Lose ten Skirmishes. The number of Skirmishes Lost by the Knights is tracked in this sentence, and is currently 3.

The Minotaur’s Behaviour is to Initiate a Skirmish; this is treated as if a Knight had performed this action, but does not count towards the weekly limit. If the Knights Lose a Skirmish Initiated by the Minotaur, each Knight without a Shield loses up to 3 Gold.

The Minotaur’s Fortitude is 13.

Slain by: TheChosenOne, Rodney, Purplebeard, ayesdeeef and IceFromHell (attack) and Kevan (scout).

===Lady of the Lake===

The Lady of the Lake's Motive is to obtain a Unique Item named Excalibur.

The Lady of the Lake's Behaviour is to place a Shortsword in the Inventory of a random Knight.

The Lady of the Lake's Fortitude is 10.

Slain by: Kevan, Purplebeard, Rodney, IceFromHell.

===Questing Beast===

The Questing Beast's Motive is for there to be no Knight whose name is Kevan.

The Questing Beast's Behaviour is to reduce the Gold of any Knight whose name is Kevan by 3.

The Questing Beast's Fortitude is 15. If an Approach to the Questing Beast does not include an ATTACK Tactic from a Knight whose name is Kevan, and there is a Knight whose name is Kevan, then the Questing Beast's cannot be Slain during that Approach.

Slain by: Kevan, Rodney, Larrytheturtle, IceFromHell (attack) and Purplebeard (scout).

===The Green Knight===

The Green Knight's Motive is to have no Enemies. The Green Knight's Enemies (if any) are listed in this sentence, and are currently: the Dragon, ayesdeef, TheChosenOne, Kevan, Larrytheturtle, rainbowkitten408 and Purplebeard.

The Green Knight’s Behaviour is to reduce the Gold of each Knight who is his Enemy by 5, and reduce the Fortitude of each Beast who is his Enemy by 5. (If this would reduce a Beast’s Fortitude to zero or lower, that Beast is instead Slain, any Unique Items it holds are moved to the Green Knight and ‘Slain by the Green Knight’ is added to that Beast’s Rule.)

Immediately after an Approach against the Green Knight has been resolved, all Attacking Knights become Enemies of the Green Knight. If the Dragon reduces the Green Knight's Fortitude, the Dragon becomes an Enemy of the Green Knight. If the Green Knight would become Slain while having no Enemies, he is instead not Slain.

The Green Knight’s Fortitude is 11.

Slain by: ayesdeef, TheChosenOne, Kevan, Larrytheturtle, rainbowkitten408 and Purplebeard.

===The Necromancer===

The Necromancer’s Motive is for the Dragon to be Undead.

The Necromancer’s Behaviour is to perform the following two actions in order:
#Select a random Slain Beast that is not Undead (if one exists) and make it Undead by appending “(Undead)” to the name of the Rule corresponding to that Beast.
#Carry out the Behaviour of each Undead Beast in the order in which they appear in the Ruleset.

The Necromancer’s Fortitude is 25.

Slain by Kevan, Rodney, Purplebeard, Ayesdeef, TheChosenOne, RainbowKitten408, Larrytheturtle and IceFromHell.

==Merchants==

As a daily action, each Knight may Visit the Merchant.

When they do so, they may either:

* Purchase exactly one item, by subtracting its Cost from their Gold and adding a copy of that item to their Inventory; or,
* Sell exactly one item that is in their Inventory, by removing it from their Inventory and adding half of that item’s Cost (rounded up) to their Gold.
* Choose a non-Unique Item to haggle over. If no Knights are Wielding or Possess that Item, then the Knight may reduce its Cost by DICE6 (to a minimum of 1); otherwise the Knight may increase its Cost by DICE6.

==Approaching Beasts==

If there is no active Approach post for a particular Beast, and that Beast has already been not Slain, a Knight may Approach that Beast by posting a blog entry with the title “Approaching [beast]”, where “[beast]” is the name of the Beast. The blog entry may contain any content. Such a blog entry is known as an Approach post, and starts as active.

Tactics that can be used against Beasts are ATTACK, SCOUT, TAME and HIDE. If a comment on an active Approach post contains any of these words in capital letters, the Knight who made that comment is considered to be taking that Tactic against the Beast for this Approach; they can be referred to by a corresponding adjective such as “Attacking Knight” or “Taming Knight”. (If a Knight makes more than one such comment, only the most recent comment is considered.)

If a quorum of Knights have taken Tactics for an active Approach, any Knight may resolve that Approach as follows (with all adjectival references to Knights referring only to the Knights who took a Tactic on this Approach):-

* If a majority of Knights who have taken a Tactic on the Approach are Attacking Knights, then the Beast is attacked: the resolving Knight rolls DICE6 for each Weapon wielded by an Attacking Knight, then adds DICE4 for each Scouting Knight. If the total exceeds the Beast's Fortitude, the Beast is Slain. If this happens, “Slain by” is added to the Beast’s Rule, followed by a list of the names of the Knights who took a Tactic on this Approach, and their corresponding Tactics, and each Attacking Knight and each Scouting Knight gains Gold equal to the Beast’s Fortitude. Each Unique Item held by the Beast is then moved to the Inventory of a random Attacking Knight (determined separately for each Item).Otherwise, each Attacking Knight loses 5 Gold (or all of their Gold if they have less than 5 Gold) and the effects of the Beast’s Behaviour are applied once.
* Otherwise, nothing happens.

When an Approach has been resolved, it ceases to be active.

==Skirmishes==

The Knights regularly fight minor monsters to safeguard the land. Every Monster Group has a Vulnerability and a Reward.

As a Weekly Communal Action, a Knight may Initiate a Skirmish by selecting a random Monster Group and counting the number of Knights who are Equipped to Fight that Monster Group. If this number is two or greater, the Knights Win the Skirmish. Otherwise, the Knights Lose the Skirmish. A Knight is Equipped to Fight a Monster Group if that Knight’s Wielded Items satisfy the requirements set out by that Monster Group’s Vulnerability.

If the Knights Win the Skirmish, the selected Monster Group’s Reward is divided evenly amongst all Knights who Wield at least one Weapon, with the Knights who are Equipped to Fight that Monster Group counted as two.

The Monster Groups are (listed as name - Vulnerability - Reward):
* Goblins - any Weapon - 40 Gold
* Skeletons - Blunt Weapon - 50 Gold
* Harpies - Ranged Weapon - 60 Gold
* Orcs - Heavy Weapon - 70 Gold
* Giant Spiders - two Weapons - 70 Gold

==Vanquishing Evil==

If every Beast is Slain and a single Knight has more Gold than every other Knight, then that Knight retires to found his or her own fiefdom and has achieved victory. (Once a Knight has retired to found his or her own fiefdom, no other Knight may do so.)

<div style="padding:8px;background:#ddd;"> 

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Knights.

;Daily Action
:If a game action is a Daily Action, each Knight able to perform it may take that action once each day, but not more than once every ten hours.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Knight’s Effective Vote Comment with respect to a given Votable Matter means that Knight’s Comment to that Votable Matter, if any, that contains that Knight’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Knight may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Knights is half the number of Knights in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Knights it is referring to, it is referring to a Quorum of all Knights.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Knight able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Knight per week.

;Wiki
:The BlogNomic Wiki at http://blognomic.com/wiki/index.php?title=Main_Page

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Knight may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Knight has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Knight may update any Knight's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Knight may correct the GNDT to comply with the Gamestate.

If a Knight feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Knights are encouraged to raise a Call for Judgement instead.
Knights shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Knight with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Knights to transfer a numeric value only allows them to transfer that value from themselves to another Knight (of their choice unless otherwise stated).
* A Knight who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
* If a game variable has no defined starting value for new Knights, or for existing Knights upon the variable’s creation, then that starting value is zero (for numerical variables) or blank (for a text string or list).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* Unless explicitly stated otherwise, a wiki page shall be blanked when it becomes gamestate.
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Player A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a Knight if it is explicitly stated that it refers to a Knight's name.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# 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 “Knights may Kick each other” and “Knights may not kick each other on Tuesdays” exist, and it is Tuesday, Knights may not Kick each other.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Knights may Punch a Spaceman on Friday” and “Knights may not Punch Spacemen on Friday”, then Knights may not Punch Spacemen on Friday.)

</div>

The Second Dynasty of RaichuKFM

2014-03-04T07:45:36Z

Purplebeard:

'''December 27, 2013 - March 4, 2014'''

== Ascension Address ==
A man comes to, lying on his stomach on a cold metal floor. He looks around and sees himself surrounded by unconscious strangers. Wait, no, this is a corridor of a ship, and those are some of his fellow crewmembers. They are starting to stir, as well. He gets up, and moseys over to the end of the hall, which is a gaping hole instead of the door it should have been. A verdant expanse stretches out to the horizon. It dawns on him that he must be crashed on a foreign planet, albeit luckily an inhabitable one. As he is joined by his comrades, he wracks his brain to remember what happened. This effort is interrupted by a fellow, speaking up to remind everyone that they should work on establishing shelter. A quick query reveals that noone has any recollection of what happened. The following silence is broken by the captain, who begins to organize efforts to establish supplies and shelter.

Rename Oligarch to Survivor and Despot to Captain.

==Players==
The following players were active at the end of the Dynasty:

Dorieke, Josh*, Kevan*, Larrytheturtle*, Purplebeard*, RaichuKFM*, Rodney*

==Final Ruleset==
[[Ruleset 116]]

==Posts of Interest==

==Ascension==

{{Dynastic Histories}}

Ruleset 116

2014-03-04T07:42:07Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Survivors shall obey it. Section One consists of the “core rules” of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the appendix, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Survivors may correct obvious spelling and typographical mistakes in the Ruleset and their own Pending Proposals at any time, including replacing Spivak and gender-specific pronouns with the singular “they”.

== Survivors ==
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a '''Survivor'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Survivor.

A Survivor may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Survivor may not rejoin the game within two weeks after having left. A Survivor may only change their name as a result of a proposal approving the change.

Some Survivors are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Survivors who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

===Idle Survivors===

Some Survivors are '''Idle''', and shall be marked as such in the sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Survivors”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Survivors are not counted as Survivors.

If a Proposal contains a provision that targets a specifically named Idle Survivor, then that Idle Survivor is considered to be Unidle solely for the purposes of enacting that specific provision

When a Survivor is unidled, if they went Idle in the same dynasty, their personal gamestate retains the last legally endowed values it had, if they are still valid. Otherwise (including if a value is invalid, does not exist, or the Survivor Idled in a different dynasty), the Survivor is given the default value for new Survivor, if such a value exists.

An Admin may render a Survivor Idle if that Survivor has asked to become Idle in an entry or comment from the past four days, or if that Survivor has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should make a post announcing it when they do so. An Admin may Unidle a Survivor if that Survivor has asked to become Unidle in an entry or comment from the past four days, and Idle Admins may Unidle themselves at any time, unless the Survivor who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Survivor, known as the Captain. If there is no Captain, the Dynasty is a Metadynasty.

== Votable Matters ==
A '''Votable Matter''' is a post which Survivors may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

Each Survivor may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Survivor’s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Survivor never has a Vote, even if they were a Survivor previously and had cast a valid Vote.

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

== Proposals ==
Any Survivor may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Survivor already has 2 Proposals pending, or has already made 3 Proposals that day).

=== Special Proposal Voting ===

When a Survivor casts an explicit vote AGAINST their own Proposal, this renders the Proposal '''Self-Killed''', even if the author later changes their Vote. The Captain may use VETO as a voting icon to cast a Vote on a proposal; when the Captain casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Captain later changes their Vote.

If a Survivor other than the Captain casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Captain. When the Captain has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Captain's Vote for the purposes of other rules unless otherwise specified.

=== Resolution of Proposals ===

The oldest pending [[#Proposals|Proposal]] may be '''enacted''' by any Admin (by updating the Ruleset and/or Gamestate to include the specified effects of that Proposal, and then setting that Proposal's status to Enacted) if either of the following is true:

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been Vetoed or Self-Killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, more valid Votes cast on it are FOR than are AGAINST, and it has not been Vetoed or Self-Killed.

The oldest pending Proposal may be '''failed''' by any Admin, if any of the following are true:

* It has been Vetoed or Self-Killed.
* The number of Survivors who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgement ==
If two or more Survivors actively disagree as to the interpretation of the Ruleset, or if a Survivor feels that an aspect of the game needs urgent attention, then any Survivor may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.

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.

Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==
If a Survivor (other than the Captain) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the '''Declaration of Victory''' category, detailing this.

Upon doing so, the game immediately goes into '''Hiatus''', if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Survivors”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Survivor may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A Pending DoV may be enacted if any of the following is true:

* It has been open for voting for at least 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the Captain has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of AGAINST Votes lesser than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, has a number of Votes that exceed or equal Quorum, and more than half of its valid Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for at least 12 hours, and the number of Survivors who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and cannot be Enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Survivor who made the DoV as its Captain. That Survivor may pass this role to another Survivor at this point by making a post to that effect, if they wish. The Hiatus continues until the new Captain makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Captain's chosen theme for the new Dynasty, and may optionally specify that the terms Survivor and Captain 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it has a number of AGAINST Votes that exceed Quorum, the Survivor who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Survivor's behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one Survivor within BlogNomic.
* A Survivor should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A Survivor should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A Survivor should not edit their own blog comments once posted, nor those of any other Survivor.
* A Survivor should not edit the "Entry Date" field of a blog post.
* A Survivor should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Survivor should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =
== Memory ==
All Survivors, except the Captain, have an amount of Recollection, which is an integer between 0 and 100, inclusive. Recollection is tracked in the GNDT and defaults to 30.

=== Brain Overdrive ===
If a Survivor takes a daily or weekly action that requires a die roll, they may choose to use Brain Overdrive before taking that action. If a Survivor uses Brain Overdrive, they may perform any die roll required by an action thrice and choose any one of the three rolls to use for the action. Furthermore, using Brain Overdrive decreases the Recollection of the Survivor by two.

===Studying===
As a weekly action, a Survivor may Study by rolling DICE3. If the result is a 1, they gain 5 Recollection. If the result is a 3, the Food is reduced by 2.

== Health ==
All Survivors have a Vitality, tracked in the GNDT. Valid Vitalities are Optimal, Healthy, Fatigued, Famished, Wounded, and Disabled. Vitality defaults to Fatigued.

A Survivor’s Vitality may be Increased or Decreased. When it is Increased, it becomes the entry to the left of the Survivor’s vitality in the above list (e.g. Wounded becomes Famished), or remains at Optimal if it is already Optimal. When it is Decreased, it becomes to the entry to the right of the Survivor’s Vitality (e.g. Wounded becomes Disabled), or remains at Disabled if it already Disabled.

A Survivor cannot achieve victory while his Vitality is “Disabled”.

As a weekly action, a Survivor may Attempt First Aid. When a Survivor Attempts First Aid, they pick another Survivor in the same Location as them and roll a DICE5. If the result is a 1, the chosen Survivor has their Vitality increased.

As a weekly action, a Survivor may Attempt Self-Medication. When a Survivor Attempts Self-Medication, they roll a DICE6. If the result is a 1, they have their Vitality increased.

A Survivor who is Disabled may not take any Daily or Weekly actions.

=== Hippocratic Oath ===

If a Survivor takes an action that causes another Survivor’s Health to change from Disabled to any status other than Infected, the former gains 5 Recollection.

== Communal Resources ==
There is a communal quantity of Food tracked in the Captain’s row of the GNDT in a column called Food, defaulting to six times the number of Survivors.

There is a communal quantity of electrical Power tracked in the Captain’s row of the GNDT in a column called Power, defaulting to 0.

There is a communal quantity of Supplies tracked in the Captain’s row of the GNDT in a column called Supplies, defaulting to 0.

== Modules ==
The ship has various modules. if a module has a Required Power attribute, it is considered Operational if and only if the communal Power is at least as high as the Required Power attribute.

=== List of modules ===

==== Infirmary ====
Required Power: 100

If this module is active, Survivors may Care For Sick as a weekly action. When a Survivor Cares For Sick, they pick another Survivor with a Vitality of “Famished” or lower and roll a DICE4. If the result is a 1, the chosen Survivor has their Vitality set to “Fatigued”. Regardless of the result of the dice roll, the communal Power is reduced by 5.

If this module is active, Survivors may Rest In Infirmary as a weekly action, under two conditions:
a) They have not yet taken a weekly action that week
b) Their Vitality is “Famished” or lower
When a Survivor Rests in Infirmary, they roll a DICE5. If the result is a 1, they have their Vitality set to “Fatigued”. Regardless of the result of the dice roll, the communal Power is reduced by 5, and they cannot take another weekly action that week.

==== Evil A.I. ====
Required Power: 200

If this module is active, Survivors may Recover Logs as a weekly action. When a Survivor Recovers Logs, they roll a DICE4. If the result is a 1, that Survivor gains 10 Recollection.

After performing a successful Recover Logs action and gaining Recollection, a survivor must roll an additional DICE4. If the result is 1, the Survivor is now considered Evil.
Evil Survivors do not perform the additional DICE4 evil roll.
Evil Survivors may perform the Recover Logs twice per week.
An Evil Survivor may not achieve victory if the Evil A.I. module is not operational.

==== Subspace Transceiver ====
Required Power: 300

== Specialists ==
Each Survivor has a single Specialization tracked in the GNDT in a column called Specialization, which is “None” by default. As a weekly action a Survivor may Respec. When a Survivor Respecs, their Specialization becomes “None”. Legal Specializations and their effects on dynastic actions are listed below:

* None: When a Survivor with Specialization of None Respecs, they may instead set their Specialization to any Legal Specialization which is not Commander Raichu and is not on the Crew Manifest.
* Hunter: A Safe Hunter in a Green Location adds 3 to the communal Food during the first step of Taking Stock.
* Doctor: When a Survivor with Specialization of Doctor Attempts First Aid, they roll a DICE4 instead of DICE5. When they Attempt Self-Medication, they roll a DICE5 instead of DICE6
* Technician: A Safe Technician in Location 0 adds 4 to the communal Power during the first step of Taking Stock.
* Scavenger: A Safe Scavenger in a Yellow Location adds 3 to the communal Supplies during the first step of Taking Stock.
* Commander Raichu: Commander Raichu has no special abilities.
* Lt Helle: If Lt Helle is Safe, the communal Food is increased by 3 during the first step of Taking Stock.
* Lt Monsen: If Lt Monsen is Safe and in a Green Location, the communal Food is increased by 5 during the first step of Taking Stock.
* Dr Prestrud: When Dr Prestrud Attempts First Aid, they roll a DICE3 instead of DICE5.
* Dr Larsen: When Dr Larsen Attempts First Aid, if the result is a 1 then the Survivor has their Vitality increased twice; if the result is 5, the Survivor has their Vitality decreased.
* Engineer Galti: If Engineer Galti is Safe, the communal Power is increased by 6 during the first step of Taking Stock.
* Engineer Bock: If Engineer Bock is Safe and in Location 0, the communal Power is increased by 8 during the first step of Taking Stock.
* Lt. Casey: If Lt. Casey is Safe, add DICE12 to the communal Supplies during the first step of Taking Stock.

=== Crew Manifest ===
The fire-damaged ship’s computer lists the Crew Manifest as:-

* Dr Prestrud
* Dr Larsen
* Engineer Galti
* Engineer Bock
* Lt Helle
* Lt Monsen
* Lt. Casey

If a Survivor’s Recollection is 40 or more, they may, as a Weekly Action, Recall their previous identity onboard the ship, by choosing any name on the Crew Manifest which is not currently taken as the Specialization of a Survivor with higher Recollection; upon doing so, this becomes their Specialization, and any other Survivor with that name as their Specialization has it set to “None”.

==Epiphanies==
The Captain has an ordered list of Epiphanies, consisting of short messages, coupled with a number called a Threshold. If a Survivor has had an amount of Recollection higher than the Threshold of an Epiphany, the Captain should send that Epiphany to the Survivor in a private message, if the Captain has not done so already. If a Survivor has received an Epiphany and no Survivor has Revealed that particular Epiphany yet, they may Reveal it by posting a Story Post highlighting this fact and adding the Epiphany to the wiki page “Epiphanies” in a bulleted list.

==Movement==
Every Survivor has a Location, which is a colored region on the “[[MaroonedMap]]”. Locations are tracked in the GNDT as integers between 0 and 16 (inclusive), corresponding to the Locations as shown on the Map, and defaulting to 0. Each Location has a Color, which can be Red, Green, Yellow, Blue, or Grey. The color of a Location is defined by its color on the MaroonedMap page. The MaroonedMap page cannot be altered except by Proposals or Call for Judgements.

Any Survivor, if they have not done so in the past 24 hours, and if their Vitality is not Wounded or Disabled, may Walk. They do so by changing their Location to one adjacent to the Location they are in, as shown on the Marooned Map. A Survivor with a Vitality of Wounded may Walk if they have not done so in the past 72 hours. Immediately after doing so, they must roll DICE3. If the result is a 3, their Vitality is Decreased. No Survivor may Walk to any Blue Location.

==Taking Stock==
A Survivor is Safe if they are not Disabled or Infected.

If at least 4 days have passed since Stock was last Taken, any Survivor may Take Stock by performing the following, in order:

1. For each Safe Survivor, the communal resources are increased by the amount corresponding to their Specialisation.<br>
2. Increase the Food by {G}DICE9, where {G} is the total number of Safe Survivors in a Green Location.<br>
3. Decrease the Food by 2 times the number of Safe Survivors in Location 0 and 3 times the number of Safe Survivors not in Location 0. If this would set it below 0, instead it is set to 0.<br>
4. If the Food is 0, Decrease every Safe Survivor’s Vitality.<br>
5. Increase the Power by 8 times the number of Safe Survivors in Location 0.<br>
6. Increase the Supplies by (3*Y)DICE3, where Y is the total number of Safe Survivors in a Yellow Location.<br>
7. Move The Alien by subtracting (3DICE3)-4 from the number of its current Location. If this would place The Alien at a Location smaller than 0 or greater than 16, it is placed at 0 or 16, respectively. <br>
8. Increase the recollection of any survivors with a Vitality of Healthy by 1 and those with a Vitality of Optimal by 2.

Survivors may not perform actions governed by Dynastic Rules while Stock is being Taken. If a Survivor begins Taking Stock but leaves the action incomplete, another Survivor may finish it.

==The Alien==
There is an entity, called The Alien by the Survivors, that has been seen stalking around the site of the crash. The Alien’s Location is tracked in its own GNDT row, with all other columns blank.

If a Survivor is ever in the same Location as The Alien, that Survivor's Vitality is set to Infected. If an Infected Survivor's Vitality would be Increased, instead nothing happens. If an Infected Survivor's Vitality is Decreased, it is set to Disabled. The Infected Vitality is otherwise considered to be at the same level as Fatigued.

If an Infected Survivor walks to a different Location on the MaroonedMap, he should roll a DICE6 for every non-Infected Survivor in the new Location. If the result is 1, that Survivor becomes Infected.

If a non-Infected Survivor walks to a different Location on the MaroonedMap and there is an Infected Survivor in the new Location, he should roll a DICE8. If the result is 1, he becomes Infected.

== Victory ==

If the Subspace Transceiver is Operational, the non-Disabled, non-Evil, non-Infected Survivor (or Survivors, in case of a tie) with the highest Recollection has achieved Victory.

If exactly one Survivor is not Disabled, and that Survivor is Evil, they have achieved Victory.

If every Survivor who is not Disabled is Infected, The Alien achieves Victory. In this case, all Dynastic Rules are repealed and a new Dynastic Rule is created with the name “Glorious Overlord” and the text “The Alien is an entity that is treated as a Survivor for all purposes. The Alien may never be idled.” Then, a new Dynasty begins with The Alien as Captain.

== Equipment ==

Survivors may possess Equipment. The Equipment a survivor possesses is tracked as a comma separated list in the GNDT, under Equipment.

A non-Disabled Survivor may transfer Equipment to another Survivor in the same location as themselves by removing the Equipment from their list and appending to the other Survivor’s list. A non-Disabled Survivor may transfer Equipment from a Disabled Survivor in the same location to themselves with the same method.

The possible types of Equipment are listed as subrules to this rule. Each Equipment has a Supply Cost.

=== Spear ===

Name: Spear
Supply Cost: 5
Effect: Any Safe Survivor in a Green Location with a Spear adds 1 to {G} when Stock is Taken. Multiple spears possessed by the same Survivor do not increase this effect.
A non-Disabled Survivor with a Spear may as a daily action attempt to stab another Survivor in the same location with a spear by rolling a DICE5. If the roll is a 1, the stab is successful and the stabbed survivor’s vitality is decreased. Multiple Spears do not allow multiple stabbing attempts.

=== Anti-Spore Mask ===

Name: Anti-Spore Mask
Supply Cost: 10
Effect: A Survivor with an Anti-Spore Mask may not become Infected.

=== Battery ===

Name: Battery
Supply Cost: 20
Effect: A non-Disabled Survivor at Location 0 with a battery may increase the communal Power by 10 by removing the Battery from their Equipment.
A non-Disabled Survivor may explode the battery by removing it from their Equipment. When they do so, all Survivors in the same Location have their vitality decreased.

== Requisitioning ==

Any Safe Survivor at Location 0 may suggest a distribution of supplies by making a Story Post with “Requisition” in the title. This is a Votable Matter, which only Safe Survivors at Location 0 may vote in.

A Requisition post must contain a list of any number of Survivors at Location 0, and for each, a list of new Equipment to be given to them.

After 48 hours, or reaching a Quorum of FOR or AGAINST votes, any Admin may resolve it. If there are more FOR than AGAINST votes the Requisition post passes, each Survivor listed receives the Equipment listed, and the communal Supplies are reduced by the Supply Cost of each Equipment distributed. If the total cost would be more than the supplies, or there are equal or fewer FOR votes than AGAINST votes, the Requisition post is failed instead, and nothing happens. If a listed Survivor has idled or is no longer at Location 0, the Equipment is not given to them, and the supply cost of that equipment is not subtracted from the communal Supplies.

=== Theft ===

Any Evil Survivor, as a Weekly Action, may Steal from the Supplies, by adding an Equipment to their Equipment list and reducing the communal Supplies by the Supply Cost of the Equipment. If the new Equipment’s Supply Cost would be greater than the communal supplies, it may not be stolen.

<div style="padding:8px;background:#ddd;"> 

= Appendix =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Survivors.

;Daily Action
:If a game action is a Daily Action, each Survivor able to perform it may take that action once each day, but not more than once every ten hours.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A Survivor’s Effective Vote Comment with respect to a given Votable Matter means that Survivor’s Comment to that Votable Matter, if any, that contains that Survivor’s Vote on that Votable Matter.

;Flavour Text
:When posting a blog entry, a Survivor may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;May not
:"is not permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Private Message
:A message sent via Blognomic’s Private Messages system at blognomic.com.

;Quorum
:Quorum of a subset of Survivors is half the number of Survivors in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Survivors it is referring to, it is referring to a Quorum of all Survivors.

;Resolve/Resolution
:If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words

;Rule
:Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.

;Shall
:"is required to"

;Should
:"is recommended that"

;Sibling Rule
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.

;Story Post
:A Story Post is an entry in the “Story Post” category.

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Subrule
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule “Votable Matters”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each Survivor able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Weekly Communal Action
:If a game action is a Weekly Communal Action, it can be performed by any Survivor, but only if it has not been performed (by any Survivor) already in the same week.

;Wiki
:The BlogNomic Wiki at http://blognomic.com/wiki/index.php?title=Main_Page

== Gamestate Tracking ==

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Survivor may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.

If no Survivor has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Survivor may update any Survivor's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Survivor may correct the GNDT to comply with the Gamestate.

If a Survivor feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Survivors are encouraged to raise a Call for Judgement instead.
Survivors shall be assigned a password for the GNDT when they join the Nomic.

=== Random Generators ===
The GNDT can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active Survivor with server-level access to the BlogNomic site who is able to perform the changes, and must also update this rule to reflect the new potential outcomes.

==Clarifications==

===Numbers and Variables===
* If a set of valid values is not specified in their definition, game variables defined to hold numeric values can hold only non-negative integers. Any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset.
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, to “spend” or “lose” an amount X of a numeric value “V” means to subtract X from V; to “gain” X of a numeric value “V” means to add X to V; and to “transfer” X of a numeric value “V” from A to B means to subtract X from A’s V and add X to B’s V. Unless otherwise specified, only positive amounts can be spent, lost, gained, or transferred, and a rule that allows Survivors to transfer a numeric value only allows them to transfer that value from themselves to another Survivor (of their choice unless otherwise stated).
* A Survivor who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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 a game variable has no defined starting value for new Survivors, or for existing Survivors upon the variable’s creation, then that starting value is zero (for numerical variables) or blank (for a text string or list).
* Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* Unless explicitly stated otherwise, a wiki page shall be blanked when it becomes gamestate.
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* If a rule would ever have no name, it is instead named “Unnamed Rule”.
* The names of rules are not themselves rule text and have no effect other than being rule names.
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Player A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.

===Time===
* For the purpose of all rules, time in Blognomic is in UTC.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a Survivor if it is explicitly stated that it refers to a Survivor's name.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any Rule;
# A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
# If both contradicting parts are a Core Rule, or if both of them are a Dynastic Rule, the part with more limited scope applies. (e.g. if the rules “Survivors may Kick each other” and “Survivors may not kick each other on Tuesdays” exist, and it is Tuesday, Survivors may not Kick each other.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Survivors may Punch a Spaceman on Friday” and “Survivors may not Punch Spacemen on Friday”, then Survivors may not Punch Spacemen on Friday.)

</div>

Ruleset 90

2011-04-22T15:33:12Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the Ruleset for BlogNomic; all '''Sheep''' shall obey it. Section One consists of the "core rules" of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the glossary, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Admins may correct obvious spelling and typographical mistakes in the Ruleset at any time, including replacing Spivak and gender-specific pronouns with the singular "they".

== Sheep ==

Anybody may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing their arrival. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a '''Sheep'''.

A '''Sheep''' may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A '''Sheep''' may only change their name as a result of a proposal approving the change.

Some '''Sheep''' are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. '''Sheep''' who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

Some '''Sheep''' are Idle, and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules 1.1, 1.2, 1.8 and 1.10, Idle '''Sheep''' are not counted as '''Sheep'''. Admins may render a '''Sheep''' Idle if that '''Sheep''' has asked to become Idle or if that '''Sheep''' has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time by announcing that they have done so in a blog post. Admins may de-Idle a '''Sheep''' at their request, and Idle Admins may de-idle themselves at any time, unless the idle '''Sheep''' in question asked to become (or rendered themselves) Idle within the previous 4 days, and within the current dynasty. The '''Sheep'''’s personal gamestate retains the values it had immediately prior to their going Idle. If one or more values would be undefined, it is set to the value new '''Sheep''' receive, if such a value exists.

== Proposals ==

Any '''Sheep''' may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Sheep already has 2 Proposals pending, or has already made 3 Proposals that day).

Proposals can either be Pending, Enacted, or Failed. When a Proposal is first put forward, it is considered Pending. A Proposal may not also be a Call for Judgment.

== Voting ==
Any '''Sheep''' may cast their Vote on a Votable Matter by making a comment to the official post that comprises that Votable Matter using a voting icon of FOR, AGAINST, DEFERENTIAL (only if the Votable Matter is a Proposal), or VETO (only if the Votable Matter is a Proposal and the '''Sheep''' is the '''Chairsheep''').

If the '''Sheep''' who authored a Votable Matter has not cast a Vote on it, their Vote is counted as FOR. If a '''Sheep''' uses more than one Voting Icon in comments on a Votable Matter, their Vote is the last voting icon they use. If a '''Sheep''' leaves the game or goes Idle, their Vote is no longer valid. If a '''Sheep''' Votes against their own Proposal, this renders the Proposal self-killed and that Vote may not be changed.

A Vote of DEFERENTIAL is a Vote of no opinion, or of faith in the decision of the '''Chairsheep'''. The Vote will count as the same as the '''Chairsheep'''’s Vote. If the '''Chairsheep''' casts a Vote of DEFERENTIAL on a Proposal, it serves the purpose of cancelling any previous Vote on that Proposal that was cast by the '''Chairsheep''' and counts as an explicit Vote of abstention. If there is no '''Chairsheep''', or the Vote is made by the proposal’s author on their own proposal and the '''Chairsheep''' does not Vote on it, a Vote of DEFERENTIAL counts as an explicit Vote of abstention, and has no effect except possibly to void earlier voting icons by that voter on that proposal.

If no '''Chairsheep''' has Voted on a Proposal, a Vote of DEFERENTIAL on that proposal does not count as a Vote for the purposes of rule 1.5.

== Resolution of Proposals ==

The oldest pending [[#Proposals|Proposal]] may be enacted by any Admin (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) if either of the following is true:-

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed or self-killed.
* It has been open for voting for at least 48 hours, it has continuously been a proposal for that time, it has more than 1 valid Vote, more than half of its Votes are FOR, and it has not been vetoed or self-killed.

The oldest pending Proposal may be failed by any Admin, if any of the following are true:-

* It has enough AGAINST Votes that it could not be Enacted without one of those Votes being changed.
* It has been open for voting for at least 48 hours and half or fewer of its Votes are FOR.
* It has been open for voting for at least 48 hours and has fewer than 2 valid Votes.
* The '''Sheep''' who proposed it has Voted AGAINST it.
* The '''Chairsheep''' has Voted to VETO it.

Whenever an Admin marks a proposal, CfJ, or DoV as enacted or failed, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

Proposals the '''Chairsheep''' has Voted to VETO are considered vetoed, and such a Vote cannot be changed. Proposals the author has Voted against are considered self-killed unless the '''Chairsheep''' has Voted VETO on them, or they have fulfilled one of the other requirements to fail a proposal before the author’s self-kill Vote is placed. Immediately after enacting a proposal that causes a rule with no name to be added to the ruleset, unless the proposal specifically states that the rule should have no name, the enacting admin can change the rule’s title to give it a name, so long as doing so does not change the meaning of any part of the ruleset, nor change any properties of the rule (such as specific words in the title) that the ruleset specifically cares about.

If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin.

== Calls for Judgment ==

If two or more '''Sheep''' actively disagree as to the interpretation of the Ruleset, or if a '''Sheep''' feels that an aspect of the game needs urgent attention, then any '''Sheep''' may raise a Call for Judgment (abbreviated CfJ) by posting an entry in the “Call for Judgment” category. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All '''Sheep''' may cast Votes on that CfJ to indicate agreement or disagreement with the position taken in that CfJ. Unfailed CfJs continue until they reach a [[#Enactment|Quorum]] of FOR Votes, a Quorum of AGAINST Votes, or if there is no hiatus going on, until four days have passed since they were posted, and if there is a hiatus going on until two days have passed since they were posted. After this time, if more than half the cast Votes are FOR Votes, the CfJ may be enacted by any Admin by updating or correcting the Gamestate and Ruleset as specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

Any CfJ that has no effect on the ruleset or gamestate may be automatically failed by any admin.

== Gamestate Tracking ==

[[#Proposals|Proposals]], [[#Calls for Judgment|Calls for Judgment]], and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any '''Sheep''' may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts.

If no '''Sheep''' has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any '''Sheep''' may update any '''Sheep''''s data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any '''Sheep''' may correct the GNDT to comply with the Gamestate.

If a '''Sheep''' feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, '''Sheep''' are encouraged to raise a Call for Judgment instead.
'''Sheep''' shall be assigned a password for the GNDT when they join the Nomic.

== Dynasties ==
BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single '''Sheep''', known as the '''Chairsheep'''.

The '''Chairsheep''' may Vote to VETO any Proposal.

== Victory and Ascension ==
If a '''Sheep''' (other than the '''Chairsheep''') believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the Declaration of Victory category, detailing this.

Upon doing so, the game immediately goes into Hiatus, if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “'''Sheep'''”, “Voting”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

Every '''Sheep''' may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A DoV may be enacted if any of the following is true:

* It has been open for voting for 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the '''Chairsheep''' has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of against Votes fewer than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, at least Quorum '''Sheep''' have Voted on it, and more than half of its Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for 12 hours and has enough AGAINST Votes that it could not be Enacted without one of those Votes being changed.
* It has been open for voting for at least 48 hours and cannot be legally enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Sheep who made the DoV as its Chairsheep. That Sheep may pass this role to another Sheep at this point by making a post to that effect, if they wish. The Hiatus continues until the new Chairsheep makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Chairsheep’s chosen theme for the new Dynasty, and may optionally specify that the terms Sheep and Chairsheep 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it has a number of AGAINST Votes that exceed Quorum, the '''Sheep''' who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

A Declaration of Victory may not also be any other type of Official Post unless the rules concerning that type of Official Post explicitly state otherwise.

== Fair Play ==

The following are BlogNomic’s rules of fair play. If any of these rules are found to have been broken, or if a Sheep’s behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one '''Sheep''' within BlogNomic.
* A '''Sheep''' should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A '''Sheep''' should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A '''Sheep''' should not edit their own blog comments once posted, nor those of any other '''Sheep'''.
* A '''Sheep''' should not edit the "Entry Date" field of a blog post.
* A '''Sheep''' should not make a DoV primarily to delay the game by putting it into Hiatus.
* A '''Sheep''' should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Voting,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =
==Officials==
Each Sheep can hold up to one Official Position. Official Positions are listed in subrules of this rule. Official Positions can be held by at most one Sheep at a time, and might not be held by any; which Official Position (if any) is held by each Sheep is tracked in the GNDT. The holder of an Official Position is known as an Official.

As a weekly action, a Sheep can take an Official Position that is not currently filled by another Sheep, unless another rule bans this, or that Sheep held that Position within the previous 2 weeks.

Each Official Position has Duties, a list of requirements relating to that position. It is not illegal for an Official to fail to perform his duties; however, if an Official Position’s Duties are not fulfilled (either by the appropriate Officer, or by anyone else), any Sheep can cause that Official Position to become vacant, and the Sheep holding it to hold no Official Position, as long as they explain the way in which the Duties weren’t fulfilled in the comment to the GNDT update. Official Positions can also have Powers, rules that only have an effect while someone holds that Official Position, and which often depend on the holder.

===Default Sanitiser===
Duties: Must ensure no office stays vacant for more than 48 hours.<br>
Powers: Nobody can take an official position that was created within the previous 48 hours, unless the Default Sanitiser first gives them permission in a blog post or blog comment.

===Sheep Counter===
Duties: Must ensure Quorum remains at least 8.

===Mr. Alarm Clock===
Duties: Must ensure that a blog post or comment reminds Sheep (other than Mr. Alarm Clock) who come within 48 hours from idling due to activity or missing an Official duties deadline that such a deadline is coming up, before the deadline actually passes.

===Baanker===
Duties: Must award Wages every week.<br>
Powers: As a weekly action, the Baanker can award Wages. Upon doing so, he or she shall give 2 Baabucks to each Sheep who has an Official Position, and 1 Baabuck to each other Sheep.

===Fraud Ewenit===
Duties: Must ensure that no Sheep gets preferential treatment from another Official as a result of a Baabucks payment.<br>
Powers: If ever a Sheep directly benefits as a direct result of an Officer using their Power, and has transferred Baabucks to them within the preceding 48 hours, then the Fraud Ewenit may reverse the use of the Power, fine both Sheep a quantity of Baabucks equal to the amount transferred, and/or change the Official Position of the offending Officer to -, at their discretion.

===Admin Herder===
Duties: Must ensure that the oldest pending proposal (if it exists) has been open for voting for no more than 60 hours.<br>
Powers: The Admin Herder may Stomp a proposal by including an Imperial Seal (VETO) in a comment on that proposal. A proposal that has been Stomped and either Vetoed or self-killed may be failed by any Admin.

===Animal Welfare Administrator===
Duties: Must perform the action described in the Animal Welfare Administrator’s Powers every Monday.<br>
Powers: The Animal Welfare Administrator can, as a daily action that can only be taken on Monday, subtract 2 from the highest Baabuck value in the GNDT, and change all Baabuck values of 0 to 1.

===White Team Leader===
Duties: Must be White.<br>
Powers: As a weekly action, the White Team Leader may turn the color of another Sheep with Undetermined color to White.

===Black Team Leader===
Duties: Must be Black.<br>
Powers: As a weekly action, the Black Team Leader may turn the color of another Sheep with Undetermined color to Black.

===Head of PR===
Duties: Must ensure that each week, the header image on the main blog is changed into a better representation of the current gamestate.

===Shearer===
Duties: Must never shear a Sheep who hasn’t asked to be Sheared in a GNDT or blog comment within the previous 12 hours.<br>
Powers: At any time, the Shearer may change the Fleece value of any Full Sheep (other than themselves) to Shorn. Upon doing so, the Shearer sells the wool at market and gains 1 Baabuck. (This process is known as “Shearing”.)

===Evangelist===
Duties: At least one new Sheep (who has not idled during this Dynasty) becomes an active Sheep during each week.<br>
Powers: Gains one Baabuck for each new Sheep (who has not idled during this Dynasty) who becomes an active Sheep (excluding any Sheep who is active at the time that this rule is added to the ruleset)

===Clodhopper===
Duties: Must not allow more than two Sheep to have zero Land.<br>
Powers: As a daily action, the Clodhopper may explore a new field, adding one Land to that of any Cramped Sheep. (A Sheep is Cramped if no other Sheep has less Land than it.)

==Baabucks==
Baabucks are currency used by Sheep. Each Sheep owns an integral number of Baabucks, which can be zero but cannot be negative. New Sheep, and Sheep unidling for the first time in the dynasty, have their Baabuck holdings set to the median of all other Sheep’s Baabuck holdings.

==Color (or colour if you swing that way)==
Each Sheep has a color, which is tracked in the GNDT. The possible colors of a Sheep are Black (which may be abbreviated in the GNDT as “B”), White (which may be abbreviated in the GNDT as “W”), and Undetermined (which may be abbreviated in the GNDT as “-”). All sheep start as having Undetermined color.

If a Sheep’s Fleece has been Full for more than 24 hours but their Color is Undetermined, they may change their Color to Black or White. If a Sheep has a full Fleece and an Undetermined Color, and has been that way for more than 48 hours, any Sheep may change that Sheep’s Color to either Black or White.

==Fleeced==
Each Sheep has a value “Fleece”, which is tracked in the GNDT. The state of Fleece is either “Full” or “Shorn”. All Sheep begin with Shorn Fleece.

As a weekly action any Sheep may grow their fleece so that it becomes full.

==Conspirators? Where?!==
Some Sheep are Conspirators. When a Conspirator idles, that (idle) Sheep ceases to be a Conspirator upon their de-idling. If at any time there are less than 3 Conspirators, the Chairsheep may secretly designate Sheep as Conspirators until there are exactly 3 Conspirators. The Chairsheep shall privately notify each new Conspirator of their new status, but shall not notify any Conspirator as to the identity of any other Conspirator.

The Conspirator with the most Baabucks is the Don. In case of a tie, there is no Don.

==Where there is bureaucracy, there is corruption==
As a weekly action, a sheep may transfer any positive quantity of Baabucks to any other sheep, provided that this leaves them with a non-negative quantity of Baabucks.

==Ousting==
As a weekly action, a Sheep can Oust an Official Position currently held by some Sheep by spending 2 Baabucks. Upon doing so, the position in question ceases to be held, and the Sheep who held it just before the Ousting gains 2 Baabucks; additionally, daily and weekly actions described in that Office’s Powers cannot be performed for 48 hours.

==Land==
Each Sheep owns an amount of Land, represented as a nonnegative integer. By default, Sheep own 3 units of Land. As a weekly action, a Sheep can spend any number of Baabucks to make that many simultaneous Land Transfers; performing a Land Transfer transfers 1 unit of Land from a Sheep to another Sheep, with the Sheep making the transfer choosing the target and destination of the transfer. (It is legal to choose different sources and/or targets for different transfers in a group of transfers made this way, or to choose the same source and target every time.)

A Sheep who owns no Land may not perform daily or weekly actions defined by dynastic rules other than this one.

===Takeover===
If any Sheep owns more Land than all other Sheep combined, that Sheep achieves victory.

<div style="padding:8px;background:#ddd;">

= Glossary =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal whose changes are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more '''Sheep'''.

;Daily Action
:If a game action is a Daily Action, each '''Sheep''' able to perform it may take that action once each day, but not more than once every six hours.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 GMT, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal whose only changes are the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A '''Sheep''''s Effective Vote Comment with respect to a given Proposal means that '''Sheep'''’s Comment to that Proposal (if any) that contains that '''Sheep'''’s Vote on the Proposal that is given effect in accordance with Rule 1.4 when the Proposal is Resolved, not including explicit Votes of abstention..

;Flavour Text
:When posting a blog entry, a '''Sheep''' may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Quorum
:Quorum of a subset of '''Sheep''' is half the number of '''Sheep''' in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of '''Sheep''' it is referring to, it is referring to a Quorum of all '''Sheep'''.

;Resolve/Resolution
:If used in a context of Proposals, Call for Judgements or Declarations of Victory, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Proposal, a Call for Judgement or a Declaration of Victory. The world “Resolution” means then the act of doing so. If used in another context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words.

;Shall
:"is required to"

;Should
:"is recommended that"

;Story Post
:A Story Post is an Official Post that is not a member of any specific category of Official Posts mentioned or defined in a Core Rule (excluding Official Post).

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Votable Matter
:The word “Votable Matter”, means a Proposal, a CFJ or a DoV.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule 1.4 “Voting”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each '''Sheep''' able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Wiki
:The BlogNomic Wiki at http://blognomic.com/wiki/index.php?title=Main_Page

==Clarifications==

===Numbers and Variables===
* Unless otherwise specified, game variables defined to hold numeric values can hold only non-negative integers, and any action that would set those values below zero is an illegal action unless explicitly otherwise stated in the ruleset. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, when “X” is a number, to spend X of a numeric value “V” means to subtract X from V (i.e. replace V with V-X); to gain X of a numeric value “V” means to add X to V; and to transfer X of a numeric value “V” from A to B means to subtract X from A's V and add the amount A's V was reduced by to B's V. Unless otherwise specified, a rule that allows '''Sheep''' to transfer a numeric value only allows them to transfer that value from themselves to another '''Sheep''' (of their choice unless otherwise stated).
* A '''Sheep''' who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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 a game variable has no defined starting value for new Sheep, or for existing Sheep upon the variable’s creation, then that starting value is zero (for numerical variables) or blank (for a text string or list).

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Enactment or Failure of a Proposal are the responsibility of the Admin who Enacts or Fails it.

===Time===
* For the purpose of all rules, time in Blognomic is in GMT.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a '''Sheep''' if it is explicitly stated that it refers to a '''Sheep''''s name.

</div>

Research projects

2011-03-28T07:55:51Z

Purplebeard: /* Social Order */

==Open==

:'''Lifting large rocks'''
:Prerequisites: thinking hard, tools
:Cost: 31/35
:Field: Progress
:Effect: The Cavemen learn that if you use the right tools, you can pick up and move very large rocks.

:'''Basic Geometry'''
:Prerequisites: basic math and thinking hard
:Cost: 45
:Field: knowledge
:Effect: cavemen learn about shapes, like triangles and squares. this will help them build things later. cavemen also start to think about big numbers and big math.

:'''Axe Crafting'''
:Prerequisite: “Tools” and “Making Pointy Sticks”
:Cost: 28
:Effect: Cavemen learn that fixing rock to stick make easier to hold rock, make rock move faster when hit things.
:A Caveman who has Knowledge of Axe Crafting may, as a daily action, remove a Stick and either a Sharp Rock or a Shiny Rock from their Tools, to craft an Axe. If they removed a Sharp Rock, they may add one Sharp Axe to their Tools as a result; if they removed a Shiny Rock, they may add one Shiny Axe to their Tools.
:Field: Art

==Complete==

:'''Bashing Rocks'''
:Prerequisite: None
:Cost: 0/20
:Field: Progress
:Effects: The Cavemen have learned that if you bash a rock against another rock, it makes a noise and sometimes a bit of light.

:'''Making Pointy Sticks'''
:Prerequisites: None
:Cost: 0/15
:Field: Progress
:Effect: Cavemen realize that if you break sticks right, you can make a pointed object that can be used to poke things.
:A Caveman who has Knowledge of Making Pointy Sticks may, as a daily action, turn any basic Sticks they are carrying into Pointy Sticks.

:'''cave painting'''
:prerequisites: none
:cost: 0/20
:field: art
:effect: the cavemen can draw things that have happened on the cave wall. If a Caveman knows Cave Painting and is carrying either a Burnt Stick or a Red Rock (known as the “Painting Tool”), then he or she may, as a weekly action, reduce the cost of any Open Research Project by his or her own Intelligence, provided that they have Knowledge of every Prequisite of the Project. Upon doing so, the Painting Tool is used up and is removed from their Tools.

:'''tools'''
:prerequisites: bash rocks
:cost: 0/20
:field: progress
:effect: when rocks bash against rocks bits come off. some bits cut. if rock tied to stick can bash against other rocks easier.
:when this learn think complete, each cave guy get smarter by one point. this has effect once only.
:A Caveman who has Knowledge of Tools may, as a daily action, turn any basic Rocks they are carrying into Sharp Rocks.

:'''thinking hard'''
:prerequisites: none
:cost: 30
:Field: Knowledge
:effect: the cavemen begin to wonder about the sun, moon and stars and also triangles and circles.

:'''sky fire'''
:prerequisites: bash rocks
:cost: 20
:field: knowledge
:effect: light from rock bash like light from sky fire. sky fire hit tree, tree gets hot and burny. perhaps burny tree can be used. perhaps can make burny tree with bash rocks.
:A Caveman who has Knowledge of both Bashing Rocks and Sky Fire, and who is carrying two Rocks (of any type) may, as a daily action, remove one Rock from their Tools to add Fire to their Tools. If there is at least a Caveman carrying the tool Fire, a Caveman who has Knowledge of Sky Fire, and who is carrying a Stick (of any type other than “Burnt”) may, as a daily action, remove that Stick from their Tools to add a Burny Stick to their Tools.

:'''grunting'''
:prerequisites: none
:cost: 0/10
:field: art
:effect: The cavemen are able to attract and direct one another’s attention with guttural noises.

:'''advanced painting'''
:prerequisites: cave painting and tools
:cost: -15/30
:field: art
:effect: Cavemen can use brushes to make very nice paintings instead of just finger scribbles. They can also use tools to make a better canvas than just cave walls.

:'''Basic math'''
:Prerequisites: thinking hard
:Cost: 0/30
:Field: knowledge
:Effect: cavemen now know numbers. all cavemen get one smartness. cavemen know now how much is correct cost of learn think. cavemen still do not know of big words like me di an and av er age.

:'''Rock Finding'''
:Prerequisite: Bashing Rocks
:Cost: 0/20
:Effect: Some rocks in valley not same as other rocks. Some rocks soft and red, some hard and bright, some wet and squishy.
:If a Caveman knows Rock Finding, then whenever they take an action which would add a basic Rock to their Tools, they may add a Red Rock, a Shiny Rock or a Squishy Rock instead.
:Field: Knowledge

:'''Hunt animals'''
:Prerequisite: Making pointy sticks
:Cost: 0/15
:Effect: If you hit an animal with a rock or stick, you will get a lot of raw meat. It is not so good to eat but better than starving. Again, it does not work with mammoth, for some reason. Any caveman with Knowledge of Hunt and carrying a Weapon may choose a Weapon they are carrying and Go Hunting. They shall do this by rolling a DICE5 (mentioning their chosen Weapon in the die roll comment) and adding their chosen Weapon’s Power. On a 6 or more, they may add one Raw Meat to their tools. On 5, they shall lose their chosen Weapon to gain a Raw Meat. On 4, they shall lose their Weapon. On 3 or less, nothing happens. If after hunting a Caveman would get his third tool, they must either lose their chosen Weapon before getting the Meat, or give the Meat to a Caveman with less than 2 tools. This transaction does not count towards the daily limit described in rule 2.4 “Tool Use”. A caveman may not Go Hunting more than 3 times a day.
:Field: Progress

The Fourth Dynasty of Clucky

2011-02-21T12:13:35Z

Purplebeard: /* Proposals */

'''January 9th, 2011 - February 18th, 2011'''

== Ascension Address==
===Sid, eat your heart out (or get your little friends to do it for you)===
Hello puny ants. Far too long you have fought with eachother for supremacy. Its timed you learned a lesson. Those fighting ways will only get you so far. Winter fasts approaches and I can promise it’ll be a tough one. If your colony has any hope of survival your gonna have to work togeather. Even if you do, I highly doubt you’ll find success because I am greater and more powerful than you all. Fear me.

Change “Mini Figure(s)” to “Ant(s)”, “Brick Master” to “Sandbox Master” and repel all rules but “Citizen Brick”.

==Players==
The following players were active at the end of this Dynasty:

Blacky Bucky* Chivalrybean* Darknight* Darth Cliche* Ely Geoff Kevan* Madalyn Purplebeard* Rodlen* Roujo Subrincinator udqbpn William Winner

==Final Ruleset==
[[Ruleset 87]]

==Posts of Interest==
===Proposals===
* [http://blognomic.com/archive/long_live_the_queen/ Long live the Queen] - Introduced the Queen, an NPC who represented the colony's food supply and started laying eggs later on.
* [http://blognomic.com/archive/fifty_times_your_own_weight/ Fifty Times Your Own Weight] - Carrying.
* [http://blognomic.com/archive/ant_colony_optimization/ Ant Colony Optimization] - Finding stuff to carry.
* [http://blognomic.com/archive/traditional_gender_roles/ Traditional Gender Roles] - Defined the castes.
* [http://blognomic.com/archive/preparing_for_war/ Preparing for war] - Defined health and death.
* [http://blognomic.com/archive/abundants/ Abundants] - Introduced a weekly consumption of food as well as the possibility of colony-wide starvation, which we came close to at the end of the dynasty.
* [http://blognomic.com/archive/antagonism/ Antagonism] - Ants who were carrying twigs could hit other Ants for 5 damage.
* [http://blognomic.com/archive/comradry_ii/ Comradry II] - Introduced Comradry Points (CP), a measure of how helpful an ant has been for the colony.
* [http://blognomic.com/archive/it_is_not_always_summer/ It is not always summer!] - Trying to add a weather parameter based on real time weather, no way to keep a log of it was found.
* [http://blognomic.com/archive/six_legs_good_eight_legs_bad/ Six Legs Good, Eight Legs Bad] - Introduced the Spider, another frequent cause of anticide.
* [http://blognomic.com/archive/ant_nauseam/ Ant Nauseam] - Implements Antributes, and kicked the frequency of ant puns into overdrive for the rest of the dynasty.
* [http://blognomic.com/archive/ascendantsy/ Ascendantsy] - Defined a Victory Condition: obediant ants had to survive and increase their CP, delinquants benefited from low CP and a lot of obediant corpses and all ants could also win by becoming a queen and mating.
* [http://blognomic.com/archive/break_antpart_1_fly_n_mate/ Break antpart 1: Fly ‘n Mate] - Defined flying and mating. However, by the time this passed, all ants with flying capabilities had died under mysterious circumstances, and there wasn't enough food around to promote new ants.

==Ascension==
After a few delinquant ants had weeded out most of their competition through twig attacks, giving other ants twigs to make them delinquant and provoking the spider to eat them, Rodlen was going to win as the only obediant ant left until Purplebeard, the delinquant with the lowest CP value, gave them a twig minutes before the deadline, thereby winning the dynasty.

==Miscellaneous==

==Commentary==
I still need to see a good game that requires only one winner AND is based on cooperation... --[[User:Elia|Elia]] 16:16, 18 Feb 2011 (GMT)

The puns got worse and worse as the dynasty progressed. I hold myself partly responsible for this. -[[User:Purplebeard|Purplebeard]] 10:29, 21 Feb 2011 (GMT)
{{dynastic Histories}}

Template:Dynastic Histories

2011-02-21T12:07:50Z

Purplebeard:

Ruleset 87

2011-02-18T09:43:51Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the Ruleset for BlogNomic; all '''Ants''' shall obey it. Section One consists of the "core rules" of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the glossary, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Admins may correct obvious spelling and typographical mistakes in the Ruleset at any time, including replacing Spivak and gender-specific pronouns with the singular "they".

== Ants ==

Anybody may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing their arrival. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become an '''Ant'''.

An '''Ant''' may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. An '''Ant''' may only change their name as a result of a proposal approving the change.

Some '''Ants''' are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. '''Ants''' who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

Some '''Ants''' are Idle, and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules 1.1, 1.2, 1.8 and 1.10, Idle '''Ants''' are not counted as '''Ants'''. Admins may render an '''Ant''' Idle if that '''Ant''' has asked to become Idle or if that '''Ant''' has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time by announcing that they have done so in a blog post. Admins may de-Idle an '''Ant''' at their request, and Idle Admins may de-idle themselves at any time, unless the idle '''Ant''' in question asked to become (or rendered themselves) Idle within the previous 4 days, and within the current dynasty. The '''Ant'''’s personal gamestate retains the values it had immediately prior to their going Idle. If one or more values would be undefined, it is set to the value new '''Ants''' receive, if such a value exists.

== Proposals ==

Any '''Ant''' may submit a Proposal to change the Ruleset or Gamestate, by [http://blognomic.com/update/index.php?C=publish posting an entry] in the "Proposal" category that describes those changes, except that:

* An '''Ant''' cannot submit a non-Core Proposal if that '''Ant''' already has two or more non-Core Proposals pending.
* An '''Ant''' cannot submit a Proposal if that '''Ant''' already has three or more Proposals pending.
* An '''Ant''' cannot submit a Proposal if that '''Ant''' has already submitted three or more Proposals that day.

Proposals can either be Pending, Enacted, or Failed. When a Proposal is first put forward, it is considered Pending. A Proposal may not also be a Call for Judgment.

== Voting ==
Any '''Ant''' may cast their Vote on a Votable Matter by making a comment to the official post that comprises that Votable Matter using a voting icon of FOR, AGAINST, DEFERENTIAL (only if the Votable Matter is a Proposal), or VETO (only if the Votable Matter is a Proposal and the '''Ant''' is the '''Sandbox Master''').

If the '''Ant''' who authored a Votable Matter has not cast a Vote on it, their Vote is counted as FOR. If an '''Ant''' uses more than one Voting Icon in comments on a Votable Matter, their Vote is the last voting icon they use. If an '''Ant''' leaves the game or goes Idle, their Vote is no longer valid. If an '''Ant''' Votes against their own Proposal, this renders the Proposal self-killed and that Vote may not be changed.

A Vote of DEFERENTIAL is a Vote of no opinion, or of faith in the decision of the '''Sandbox Master'''. The Vote will count as the same as the '''Sandbox Master'''’s Vote. If the '''Sandbox Master''' casts a Vote of DEFERENTIAL on a Proposal, it serves the purpose of cancelling any previous Vote on that Proposal that was cast by the '''Sandbox Master''' and counts as an explicit Vote of abstention. If there is no '''Sandbox Master''', or the Vote is made by the proposal’s author on their own proposal and the '''Sandbox Master''' does not Vote on it, a Vote of DEFERENTIAL counts as an explicit Vote of abstention, and has no effect except possibly to void earlier voting icons by that voter on that proposal.

If no '''Sandbox Master''' has Voted on a Proposal, a Vote of DEFERENTIAL on that proposal does not count as a Vote for the purposes of rule 1.5.

== Resolution of Proposals ==

The oldest pending [[#Proposals|Proposal]] may be enacted by any Admin (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) if either of the following is true:-

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed or self-killed.
* It has been open for voting for at least 48 hours, it has continuously been a proposal for that time, it has more than 1 valid Vote, more than half of its Votes are FOR, and it has not been vetoed or self-killed.

The oldest pending Proposal may be failed by any Admin, if any of the following are true:-

* It has enough AGAINST Votes that it could not be Enacted without one of those Votes being changed.
* It has been open for voting for at least 48 hours and half or fewer of its Votes are FOR.
* It has been open for voting for at least 48 hours and has fewer than 2 valid Votes.
* The '''Ant''' who proposed it has Voted AGAINST it.
* The '''Sandbox Master''' has Voted to VETO it.

Whenever an Admin marks a proposal, CfJ, or DoV as enacted or failed, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

Proposals the '''Sandbox Master''' has Voted to VETO are considered vetoed, and such a Vote cannot be changed. Proposals the author has Voted against are considered self-killed unless the '''Sandbox Master''' has Voted VETO on them, or they have fulfilled one of the other requirements to fail a proposal before the author’s self-kill Vote is placed. Immediately after enacting a proposal that causes a rule with no name to be added to the ruleset, unless the proposal specifically states that the rule should have no name, the enacting admin can change the rule’s title to give it a name, so long as doing so does not change the meaning of any part of the ruleset, nor change any properties of the rule (such as specific words in the title) that the ruleset specifically cares about.

== Calls for Judgment ==

If two or more '''Ants''' actively disagree as to the interpretation of the Ruleset, or if an '''Ant''' feels that an aspect of the game needs urgent attention, then any '''Ant''' may raise a Call for Judgment (abbreviated CfJ) by posting an entry in the “Call for Judgment” category. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All '''Ants''' may cast Votes on that CfJ to indicate agreement or disagreement with the position taken in that CfJ. Unfailed CfJs continue until they reach a [[#Enactment|Quorum]] of FOR Votes, a Quorum of AGAINST Votes, or if there is no hiatus going on, until four days have passed since they were posted, and if there is a hiatus going on until two days have passed since they were posted. After this time, if more than half the cast Votes are FOR Votes, the CfJ may be enacted by any Admin by updating or correcting the Gamestate and Ruleset as specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

Any CfJ that has no effect on the ruleset or gamestate may be automatically failed by any admin.

== Gamestate Tracking ==

[[#Proposals|Proposals]], [[#Calls for Judgment|Calls for Judgment]], and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any '''Ant''' may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts.

If no '''Ant''' has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any '''Ant''' may update any '''Ant''''s data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any '''Ant''' may correct the GNDT to comply with the Gamestate.

If an '''Ant''' feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, '''Ants''' are encouraged to raise a Call for Judgment instead.
'''Ants''' shall be assigned a password for the GNDT when they join the Nomic.

== Dynasties ==
BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single '''Ant''', known as the '''Sandbox Master'''.

The '''Sandbox Master''' may Vote to VETO any Proposal.

== Victory and Ascension ==
If an '''Ant''' (other than the '''Sandbox Master''') believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the Declaration of Victory category, detailing this.

Upon doing so, the game immediately goes into Hiatus, if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “'''Ants'''”, “Voting”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

Every '''Ant''' may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A DoV may be enacted if any of the following is true:

* It has been open for voting for 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the '''Sandbox Master''' has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of against Votes fewer than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, at least Quorum '''Ants''' have Voted on it, and more than half of its Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for 12 hours and has enough AGAINST Votes that it could not be Enacted without one of those Votes being changed.
* It has been open for voting for at least 48 hours and cannot be legally enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Ant who made the DoV as its Sandbox Master. That Ant may pass this role to another Ant at this point by making a post to that effect, if they wish. The Hiatus continues until the new Sandbox Master makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Sandbox Master’s chosen theme for the new Dynasty, and may optionally specify that the terms Ant and Sandbox Master 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it has a number of AGAINST Votes that exceed Quorum, the '''Ant''' who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

A Declaration of Victory may not also be any other type of Official Post unless the rules concerning that type of Official Post explicitly state otherwise.

== Fair Play ==

The following are BlogNomic’s rules of fair play. If any of these rules are found to have been broken, or if an Ant’s behaviour or actions are otherwise deemed unacceptable (socially or otherwise), a proposal or CfJ may be made to reprimand or punish the perpetrator or, in cases of extreme or repeated violations, remove them from the game and bar them from rejoining.

* A single person should not control more than one '''Ant''' within BlogNomic.
* An '''Ant''' should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* An '''Ant''' should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* An '''Ant''' should not edit their own blog comments once posted, nor those of any other '''Ant'''.
* An '''Ant''' should not edit the "Entry Date" field of a blog post.
* An '''Ant''' should not make a DoV primarily to delay the game by putting it into Hiatus.
* An '''Ant''' should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

==Seasonal Downtime==
Blognomic goes into hiatus every year on December 24th, and remains in hiatus until December 27th. During this time no game actions may be taken except those described in the rules entitled “Voting,” “Gamestate Tracking” and “Call for Judgement”.

</div>

= Dynastic Rules =

==NPCs==
Creatures are gamestate objects which have rows in the GNDT but do not count towards quorum and cannot vote on proposals. The current creatures in the game are listed as subrules of this rule. An NPC can be a Friend, an Enemy, or Neutral. Thus must be noted in the subrule describing an NPC. The text of NPC subrules shall contain what happens when that NPC is provoked (even if it is nothing,) or it may state that that NPC cannot be provoked.

===Provoking NPCs===

As a weekly action, and ant who is in the same location as an NPC may provoke that NPC.

===The Queen===
The queen counts as an ant for all dynastic rules unless the dynastic rule states otherwise, although she cannot take an action unless the ruleset indicates another ant may take the action on her behalf. The Queen is part of the Mature Queen caste but does not have the caste’s normal food limit. Instead, the Queen may have up to 50 food. This represents the colony’s food supply. The Queen is a Friend. The Queen cannot be provoked.

===The Spider===
The Spider is always Above Ground. When provoked, the Spider assaults a random Ant who is above ground (which may be the provoker) and reduces that Ant’s health by 10. If this causes an Ant to become dead, the Spider gains 1 food. The Spider is an Enemy.

==Carrying==
Each Creature and Ant may carry may carry a single object at a time from the following list - this carried object is tracked in the GNDT column 'Carrying'. Carryable objects are:-

<ul><li><b>Leaf.</b> A small section of leaf cut from a larger plant.
<li><b>Sugar.</b> A speck of sugar-rich matter found in the environment.
<li><b>Crumb.</b> A small item of less nutritious matter.
<li><b>Twig.</b> A small stub of a leaf stalk.
<li><b>Mould.</b> A section of fibrous mould grown within the colony.
<li><b>Egg.</b> A single ant's egg.</ul>

As a daily action, an Ant who is above ground may Follow a Trail by spending food equal to that Trail’s Distance. An Ant who Follows a Plant trail may reduce its Size by one to start carrying a Leaf or a Twig. An Ant who Follows a Filling Trail may reduce its Size by one to start carrying a Crumb. An Ant who Follows a Tasty Trail may reduce its Size by 1 to start carrying Sugar, and/or reduce its Size by 1 to increase their Food to 5.

As a weekly action, and only when the Queen has 15 food or more, an Ant who is Underground and is able to carry Eggs may reduce the Queen’s food by 10 to start carrying an Egg.

===Dropping and Using===
To 'drop' an object is to cease carrying it. To 'give' an object to another Ant or Creature is to cease carrying it, and make that Ant or Creature start carrying it. An Ant may drop the object they are carrying at any time. Any Ant may give the object they are carrying to another Ant, provided that the latter is not currently carrying anything and is able to carry the object.

An Ant who is Underground may drop a Leaf to start carrying Mould. Any Ant may drop Mould or a Crumb to distribute up to 5 food among all Ants in their location, including themself, or drop Sugar to distribute up to 8 food. An Ant may drop an Egg to change the Caste of any Worker in their location (including themself) to Soldier, Drone or Virgin Queen.

As a weekly action, an Ant who is carrying a Twig may decrease their CP by 5 to smack another Ant and reduce their (the other Ant’s) health by 5.

As a weekly action, an Ant who is carrying a Twig may increase their CP by 5 to smack an Enemy NPC and reduce their (the NPC’s) health by 5. If the NPC’s health is reduced zero (0) or less, the ant that smacked the NPC shall increase their CP by 5. If the NPC’s health is 1 or greater after being smacked, it shall be provoked as stated in the subrule for that NPC.

==Upstairs, Downstairs==
Each Ant or Creature is either Underground, Above Ground or Flying. This is tracked in the GNDT under the column entitled “Location”. New Ants start Underground, and newly created Creatures start Above Ground unless otherwise specified.

If not specifically forbidden by another rule, as a daily action an Ant may change their Location to Above Ground or Underground, but not more than three times in any seven-day period. A Creature may not have its location changed unless such a change is specifically mandated by another rule.

If an Ant has been Flying for 7 days without interruption any Ant may change their health to 0. That Ant is not considered killing the flying Ant nor making it die directly.

==Food==
Each ant and creature has an amount of food which is tracked in the GNDT and which may not exceed the limit for their Caste, or 5 if the Ant of Creature has no Caste. At any time, an ant may spend a positive amount of food and add the same amount to another Ant in the same Location, unless this action would make the latter exceed their maximum. However, an Ant may transfer exactly 6 food from themself to a Worker other than themself who possessed exactly 6 food before this action to change the latter's Caste to Honeypot. This action may only be performed if both Ants are Underground.

Whenever an Ant idles or leaves the game, all food they held is transferred to the Queen (up to her maximum), and they do not regain it if they de-idle. Whenever an Ant joins the game or de-idles, 4 food or all the Queen's food, whichever is smaller, is transferred to them from the Queen.

As a weekly action, an Ant who is Underground may transfer up to 3 food from the Queen or a Honeypot Ant to themself.

As a daily action, any Ant which has zero food may decrease the amount of food of one Ant in the same location by one, thereby increasing its own amount of food to one. The CP value of the receiving ant is decreased by one and the CP value of the giving ant is increased by one, at the same time.

===Starvation===
As a weekly action, and only if it hasn’t been done before this week, any Ant may decrease each Ant’s food by two.

When all Ants, including the Queen, have exactly zero food, the colony starves. If this happens, all proposals are failed and all dynastic rules are repealed, and a new dynasty begins with no Sandbox Master.

==Trails==
The [[Trails]] wiki page contains the trails the ant colony has found that lead to useful resources. Each trail entry must detail a Name, Type, Size and a Distance from the colony. When a Trail’s Size is reduced to 0, remove its entry from the page.

As a weekly action, an Ant who is Above Ground and who has at least 1 Food by spending 1 food may search the surroundings by rolling DICEX, where X is 5 plus the amount of existing Trails. If the result is 3 or less, they succeed, and may create a new Trail. If the result is 4 or 5, they get lost and lose 1 additional Food. If the result is greater than 5, they find a resource that has already been discovered, and nothing happens.

To create a Trail, roll DICE6. On a 1, 2 or 3, the type of the new Trail is Plant. On a 4 or 5, the type is Filling. On a 6, the type is Tasty. Then, roll DICE6 to determine the Size and DICEB to determine the Distance, where B is 2 plus the amount of other Trails of the same Type. Finally, choose a Name for the new Trail and list it on the Trails page.

If possible an ant which discovers a new trail may immediately start to carry an object according to the type of that trail as described in rule “Carrying”.

==Castes==
All Ants have a Caste, which is tracked in the GNDT and determines their role in the Colony. New Ants start as Workers. The different Castes are:

* '''Worker.''' By far the most numerous inhabitants of the colony, these small females carry out most daily tasks of the colony, including foraging, brood care and nest upkeep. Workers may have up to 6 food. Workers start with a health of 15.
* '''Soldier.''' These larger females with giant heads are primarily concerned with the defense of the colony, but they will generally act as workers if no enemies are nearby. Soldiers are limited to 4 food maximum, and their large mandibles make them unfit for carrying anything but Leafs, Twigs and Crumbs. Soldiers start with a health of 30.
* '''Honeypot.''' These ants have been gorged with food by workers, and essentially serve as living food storage. Honeypot ants may not carry anything and may not go Above Ground. They may have up to 50 food. Honeypots start with a health of 8. Honeypot Ants may not change their own food value through any means but the following: as a weekly action, a Honeypot Ant may transfer up to 5 food from themself to another Ant who is Underground. If a Honeypot Ant ever has 6 food or less, they become a Worker.
* '''Drone.''' The only males in the colony, these small winged ants are cared for by the others and prepared for the nuptial flight, where they will attempt to mate with virgin queens. Drones may have up to 5 food, and can only carry Sugar, Crumbs and Mould. Drones start with a health of 10. If they own 5 food and Weather is not snowy, Drones may change their location from "Above Ground" to "Flying" by spending 5 food.
* '''Virgin Queen.''' These winged fertile females have not yet mated, and are awaiting the nuptial flight so that they can mate and start a new colony. Virgin Queens may have up to 7 food and may not carry anything. Virgin Queens start with a health of 8. If they own at least 3 food and Weather is not snowy, Virgin Queens may change their location from "Above Ground" to "Flying" by spending 3 food. When Virgin Queens are in Flying location with one or more Drones, they may Mate with one of them. They change their Caste to Mature Queen and their location to Above Ground. They shall change the partner Drone's Caste to Worker, their Location to Underground, increase their CP by 15 and change their Antribute to Obediant, if not already.
* '''Mature Queen.''' The mother of and most important ant in the colony, this queen has been fertilized and no longer has wings. As her sole purpose is to reproduce, a Mature Queen may not carry anything. Mature Queens may have up to 50 food. Mature Queens start with a health of 40.

==Health==
Each ant and creature has a stat called health which is tracked in the GNDT in a column also called health.

If an ant’s health is ever zero, the ant is said to be dead and their food value is immediately set to 0. An ant which is dead may not take any actions outlined in dynastic rules of the ruleset with the exception of the following sentence. If an ant has been dead for 24 hours, they may reset all of their stats tracked in the GNDT to that of a new ant and are no longer dead.

An Ant’s health can never exceed its starting health as defined in the Rule “Castes”. When the Cast of an Ant is changed, set its health to the starting health of the new caste. Same applies also for Creatures.

==Товарищ==
Each ant has an amount of Comradery points (CP) which may hold any integer value and is tracked in the GNDT. All ants start with zero CP. For any positive amount food which an ant gives to another ant or a Creature, the CP of the giving ant may be increased by 1 for each unit of food. For any positive amount food which an ant receives from another ant or a Creature, the CP of the receiving ant must be decreased by 1 for each unit of food.

==Double Antendre==
Each Ant has an Antribute, which is tracked in the GNDT. New Ants start as Reincarnant. The different Antributes are:

* '''Obediant.'''
* '''Delinquant.''' Whenever an Obediant Ant starts carrying a Twig, they become Delinquant.
* '''Inantimate.''' Whenever an Ant becomes dead, they also become Inantimate.
* '''Reincarnant.''' Whenever an Ant ceases to be dead, they become Reincarnant.
* '''Expectant.''' Mature Queens are always Expectant.

If an Ant de-idles, their Antribute is set to Reincarnant instead of retaining its earlier value.

==Weather==
The [[Weather]] wiki page contains the history of all the weather conditions, with their submission date/time.
The current Weather is the last submitted in the Weather page.
If the Weather has never been changed on the current week, any Ant may change it by rolling DICE3.

- on 1 the Weather becomes Sunny;

- on 2 Rainy;

- on 3 Snowy.

They shall then add to the top of the Weather page the new weather condition and sign it with current date/time (use <nowiki>--~~~~</nowiki>).

==Victory==

The Queen and the Sandbox Master are not Ants for the purposes of this rule.

One Ant may be the Ascendant. If, at noon on the 17th of February, there is an Ascendant, that Ant has achieved victory. If more than one Ant meets the requirements below at that time or there is no Ascendant, instead all instances of "the 17th of February" in this rule are changed to that date plus three days, so that the 1st of January would become the 4th of January (assume it is not a leap year when determining this date).

* If exactly one Ant is Expectant, that Ant is the Ascendant.
* Otherwise, if there are Obediant Ants, the Obediant Ant with the highest CP is the Ascendant.
* Otherwise, if there are no Obediant Ants and there are Delinquant Ants, the Delinquant with the lowest CP is the Ascendant.
* Otherwise, if there are neither Obediant ants nor Delinquant Ants, there is no Ascendant.

<div style="padding:8px;background:#ddd;">

= Glossary =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal whose changes are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more '''Ants'''.

;Daily Action
:If a game action is a Daily Action, each '''Ant''' able to perform it may take that action once each day, but not more than once every six hours.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 GMT, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal whose only changes are the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:An '''Ant''''s Effective Vote Comment with respect to a given Proposal means that '''Ant'''’s Comment to that Proposal (if any) that contains that '''Ant'''’s Vote on the Proposal that is given effect in accordance with Rule 1.4 when the Proposal is Resolved, not including explicit Votes of abstention..

;Flavour Text
:When posting a blog entry, an '''Ant''' may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Quorum
:Quorum of a subset of '''Ants''' is half the number of '''Ants''' in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of '''Ants''' it is referring to, it is referring to a Quorum of all '''Ants'''.

;Resolve/Resolution
:If used in a context of Proposals, Call for Judgements or Declarations of Victory, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Proposal, a Call for Judgement or a Declaration of Victory. The world “Resolution” means then the act of doing so. If used in another context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words.

;Shall
:"is required to"

;Should
:"is recommended that"

;Story Post
:A Story Post is an Official Post that is not a member of any specific category of Official Posts mentioned or defined in a Core Rule (excluding Official Post).

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Votable Matter
:The word “Votable Matter”, means a Proposal, a CFJ or a DoV.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule 1.4 “Voting”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each '''Ant''' able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Wiki
:The BlogNomic Wiki at http://blognomic.com/wiki/index.php?title=Main_Page

==Clarifications==

===Numbers and Variables===
* Unless otherwise specified, game variables defined to hold numeric values can hold only non-negative integers, and any action that would set those values below zero instead sets them to zero. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, when “X” is a number, to spend X of a numeric value “V” means to subtract X from V (i.e. replace V with V-X); to gain X of a numeric value “V” means to add X to V; and to transfer X of a numeric value “V” from A to B means to subtract X from A's V and add the amount A's V was reduced by to B's V. Unless otherwise specified, a rule that allows '''Ants''' to transfer a numeric value only allows them to transfer that value from themselves to another '''Ant''' (of their choice unless otherwise stated).
* An '''Ant''' who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
* If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* 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.

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Enactment or Failure of a Proposal are the responsibility of the Admin who Enacts or Fails it.

===Time===
* For the purpose of all rules, time in Blognomic is in GMT.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of an '''Ant''' if it is explicitly stated that it refers to an '''Ant''''s name.

</div>

The Fifth Dynasty of Josh

2011-01-10T12:27:49Z

Purplebeard: /* Posts of Interest */

<div style="float:right">http://brontides.com/files/bnheaderjosh5.png</div>

'''December 18th, 2010 - January 9th, 2011'''

== Ascension Address==
http://upload.wikimedia.org/wikipedia/commons/thumb/1/15/Green_Lego_Baseplate.jpg/800px-Green_Lego_Baseplate.jpg

Repeal all dynastic rules. Throughout the ruleset, change Divinity to Mini Figure and Imperatrix to Brickmaster.

==Players==
The following players were active at the beginning of this Dynasty:

Alecto, Ambisinister, Blacky, Clarinet, Clucky, coppro, Darknight, Darth Cliche, Hyronious, iqforu, JoeFish, Josh, Purplebeard, SethOcean, Stormshade, Subrincinator, William

==Final Ruleset==
[[Ruleset 86]]

==Posts of Interest==
===Proposals===
* [http://blognomic.com/archive/another_brick_in_the_wall/ Another brick in the wall] - Introduced bricks.
* [http://blognomic.com/archive/hard_hats/ Hard Hats] - Mini Figures could buy bricks and combine them to build constructions.
* [http://blognomic.com/archive/grab_bag/ Grab Bag!] - Some bricks could be bought in random colours for 80% of the price. However, any constructions built with them could still be sold at full price.
* [http://blognomic.com/archive/citizen_brick/ Citizen Brick] - Created Requests, contests to build the best structure bound by certain criteria. All Requests were created and judged by the Brick Master, and a couple of requests with some of the most impressive submissions are listed below.
* [http://blognomic.com/archive/building_up/ Building Up] - The first victory condition. After a certain amount of requests, the Brick Master could call a Lego-Off, a contest between the two richest Mini Figures to decide the winner.
* [http://blognomic.com/archive/the_good_ol_activity_injector/ The good ol’ activity injector] - Write good proposals, get free cash. Never fails to increase activity in some of the more opportunistic players.
* [http://blognomic.com/archive/behold_my_life-size_assault_tank/ Behold My Life-Size Assault Tank] The second victory condition required a construction of base value 1500 to be built. This was triggered by Clucky, who won the dynasty.

===Requests===
* [http://blognomic.com/archive/closed_request_oh_tannenbaum/ Oh Tannenbaum]
* [http://blognomic.com/archive/open_request_something_new/ Something New]
* [http://blognomic.com/archive/closed_request_monumental/ Monumental]
* [http://blognomic.com/archive/open_request_traffic_lights/ Traffic lights]

==Ascension==
Clucky used the Big modifier, a grab-bag of assorted bricks and a well-timed sell to turn 480 Funds into a dungpile with a value of more than 3000 Funds, winning the game.

==Miscellaneous==
This dynasty saw a proposal pass that codified holiday breaks, initially over Christmas. The proposal made it clear that BlogNomic does not recognise or endorse any religious, seasonal, or national holidays, but can put measures in place to adapt to predictable downturns in activity.

==Commentary==
WOOT LEGO {{User:Darth Cliche/sig}} 22:51, 18 Dec 2010 (GMT)

{{dynastic Histories}}

The First Dynasty of Alecto

2010-12-19T12:50:06Z

Purplebeard:

<div style="float:right">http://blognomic.com/images/alecto1header.png</div>

'''November 29th, 2010 - December 18th, 2010'''

== Ascension Address==

==Players==
The following players were active at the end of this Dynasty:

Alecto, Ambisinister, Blacky, Clarinet, Clucky, coppro, Darknight, Darth Cliche, Hyronious, iqforu, JoeFish, Josh, Purplebeard, SethOcean, Stormshade, Subrincinator, William

==Final Ruleset==
[[Ruleset 85]]

==Posts of Interest==

==Ascension==
A dubious scam by Josh led to an even more dubious victory.

Josh's [http://blognomic.com/archive/ragnarok/ first DoV] was based on two very weak scams. The first scam utilised a very loose interpretation of the rules for enacting CfJs to rush through a pending CFJ that would allow him to create a new mortal. The second was based on the assumption that the mortal's name (which, as the creating mortal, he could chose) could have an effect on other parts of the gamestate.

Purplebeard disputed the second scam but accepted the first, and went so far as to instantly pass [http://blognomic.com/archive/shameless_hijack/ his own CFJ], granting himself victory and failing Josh's pending DoV. However, in his hurry he improperly adminned it, allowing Josh to revert it, force through an identical CfJ, and finally [http://blognomic.com/archive/this_is_getting_silly/ successfully claim victory].

==Miscellaneous==

==Commentary==
I don't for even one second believe that that victory would have flown if the dynasty hadn't been deathly quiet anyway. [[User:Josh|Josh]]

Ed de Goey was a childhood hero of mine (and still is), and I've been known to insert his name into any conversation that is even tangentially related to football or the topic of awesome people. It feels good to have introduced him to blognomic as the focal point of an ancient prophecy. [[User:Purplebeard|Purplebeard]]

{{dynastic Histories}}

Ruleset 84

2010-11-29T09:32:35Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the Ruleset for BlogNomic; all '''Student'''s shall obey it. Section One consists of the "core rules" of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the glossary, which exists solely to clarify the remainder of the ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

Admins may correct obvious spelling and typographical mistakes in the Ruleset at any time, including replacing Spivak and gender-specific pronouns with the singular "they".

== Students ==

Anybody may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing their arrival. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a '''Student'''.

A '''Student''' may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A '''Student''' may only change their name as a result of a proposal approving the change.

Some '''Student'''s are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. '''Student'''s who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.

Some '''Student'''s are Idle, and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules 1.1, 1.2, 1.8 and 1.10, Idle '''Student'''s are not counted as '''Student'''s. Admins may render a '''Student''' Idle if that '''Student''' has asked to become Idle or if that '''Student''' has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time by announcing that they have done so in a blog post. Admins may de-Idle a '''Student''' at their request, and Idle Admins may de-idle themselves at any time, unless the idle '''Student''' in question asked to become (or rendered themselves) Idle within the previous 4 days, and within the current dynasty. The '''Student'''’s personal gamestate retains the values it had immediately prior to their going Idle. If one or more values would be undefined, it is set to the value new '''Student'''s receive, if such a value exists.

== Proposals ==

Any '''Student''' may submit a Proposal to change the Ruleset or Gamestate, by [http://blognomic.com/update/index.php?C=publish posting an entry] in the "Proposal" category that describes those changes, except that:

* A '''Student''' cannot submit a non-Core Proposal if that '''Student''' already has two or more non-Core Proposals pending.
* A '''Student''' cannot submit a Proposal if that '''Student''' already has three or more Proposals pending.
* A '''Student''' cannot submit a Proposal if that '''Student''' has already submitted three or more Proposals that day.

Proposals can either be Pending, Enacted, or Failed. When a Proposal is first put forward, it is considered Pending. A Proposal may not also be a Call for Judgment.

== Voting ==
Any '''Student''' may cast their Vote on a Votable Matter by making a comment to the official post that comprises that Votable Matter using a voting icon of FOR, AGAINST, DEFERENTIAL (only if the Votable Matter is a Proposal), or VETO (only if the Votable Matter is a Proposal and the '''Student''' is the '''Headmaster''').

If the '''Student''' who authored a Votable Matter has not cast a Vote on it, their Vote is counted as FOR. If a '''Student''' uses more than one Voting Icon in comments on a Votable Matter, their Vote is the last voting icon they use. If a '''Student''' leaves the game or goes Idle, their Vote is no longer valid. If a '''Student''' Votes against their own Proposal, this renders the Proposal self-killed and that Vote may not be changed.

A Vote of DEFERENTIAL is a Vote of no opinion, or of faith in the decision of the '''Headmaster'''. The Vote will count as the same as the '''Headmaster'''’s Vote. If the '''Headmaster''' casts a Vote of DEFERENTIAL on a Proposal, it serves the purpose of cancelling any previous Vote on that Proposal that was cast by the '''Headmaster''' and counts as an explicit Vote of abstention. If there is no '''Headmaster''', or the Vote is made by the proposal’s author on their own proposal and the '''Headmaster''' does not Vote on it, a Vote of DEFERENTIAL counts as an explicit Vote of abstention, and has no effect except possibly to void earlier voting icons by that voter on that proposal.

If no '''Headmaster''' has Voted on a Proposal, a Vote of DEFERENTIAL on that proposal does not count as a Vote for the purposes of rule 1.5.

== Resolution of Proposals ==

The oldest pending [[#Proposals|Proposal]] may be enacted by any Admin (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) if either of the following is true:-

* It has a number of FOR Votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed or self-killed.
* It has been open for voting for at least 48 hours, it has continuously been a proposal for that time, it has more than 1 valid Vote, more than half of its Votes are FOR, and it has not been vetoed or self-killed.

The oldest pending Proposal may be failed by any Admin, if any of the following are true:-

* It has enough AGAINST Votes that it could not be Enacted without one of those Votes being changed.
* It has been open for voting for at least 48 hours and half or fewer of its Votes are FOR.
* It has been open for voting for at least 48 hours and has fewer than 2 valid Votes.
* The '''Student''' who proposed it has Voted AGAINST it.
* The '''Headmaster''' has Voted to VETO it.

Whenever an Admin marks a proposal, CfJ, or DoV as enacted or failed, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

Proposals the '''Headmaster''' has Voted to VETO are considered vetoed, and such a Vote cannot be changed. Proposals the author has Voted against are considered self-killed unless the '''Headmaster''' has Voted VETO on them, or they have fulfilled one of the other requirements to fail a proposal before the author’s self-kill Vote is placed. Immediately after enacting a proposal that causes a rule with no name to be added to the ruleset, unless the proposal specifically states that the rule should have no name, the enacting admin can change the rule’s title to give it a name, so long as doing so does not change the meaning of any part of the ruleset, nor change any properties of the rule (such as specific words in the title) that the ruleset specifically cares about.

== Calls for Judgment ==

If two or more '''Student'''s actively disagree as to the interpretation of the Ruleset, or if a '''Student''' feels that an aspect of the game needs urgent attention, then any '''Student''' may raise a Call for Judgment (abbreviated CfJ) by posting an entry in the “Call for Judgment” category. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All '''Student'''s may cast Votes on that CfJ to indicate agreement or disagreement with the position taken in that CfJ. Unfailed CfJs continue until they reach a [[#Enactment|Quorum]] of FOR Votes, a Quorum of AGAINST Votes, or if there is no hiatus going on, until four days have passed, and if there is a hiatus going on until two days have passed. After this time, if more than half the cast Votes are FOR Votes, the CfJ may be enacted by any Admin by updating or correcting the Gamestate and Ruleset as specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

Any CfJ that has no effect on the ruleset or gamestate may be automatically failed by any admin.

== Gamestate Tracking ==

[[#Proposals|Proposals]], [[#Calls for Judgment|Calls for Judgment]], and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any '''Student''' may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts.

If no '''Student''' has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any '''Student''' may update any '''Student'''s data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any '''Student''' may correct the GNDT to comply with the Gamestate.

If a '''Student''' feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, '''Student'''s are encouraged to raise a Call for Judgment instead.
'''Student'''s shall be assigned a password for the GNDT when they join the Nomic.

== Dynasties ==
BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single '''Student''', known as the '''Headmaster'''.

The '''Headmaster''' may Vote to VETO any Proposal.

== Victory and Ascension ==
If a '''Student''' (other than the '''Headmaster''') believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the Declaration of Victory category, detailing this.

Upon doing so, the game immediately goes into Hiatus, if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “'''Student'''s”, “Voting”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

Every '''Student''' may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A DoV may be enacted if any of the following is true:

* It has been open for voting for 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the '''Headmaster''' has Voted FOR it or it has no AGAINST Votes.
* It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of against Votes fewer than half of Quorum, rounded down.
* It has been open for voting for at least 48 hours, at least Quorum '''Student'''s have Voted on it, and more than half of its Votes are FOR.

A DoV may be failed if any of the following are true:

* It has been open for voting for 12 hours and has enough AGAINST Votes that it could not be Enacted without one of those Votes being changed.
* It has been open for voting for at least 48 hours and cannot be legally enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the '''Student''' who made the DoV as its '''Headmaster'''. (That '''Student''' may pass this role to another '''Student''' at this point, if they wish.) The Hiatus continues until the new '''Headmaster''' posts an Ascension Address to the BlogNomic weblog - this should specify the '''Headmaster’s''' chosen theme for the new Dynasty, and may optionally specify that the terms '''Student''' and '''Headmaster''' 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.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it has a number of AGAINST Votes that exceed Quorum, the '''Student''' who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

A Declaration of Victory may not also be any other type of Official Post unless the rules concerning that type of Official Post explicitly state otherwise.

== Fair Play ==

The following are BlogNomic’s rules of fair play. If any of the rules are found to have been broken, a proposal or CfJ may be made to remove the perpetrator from the game, and bar them from rejoining.

* A single person should not control more than one '''Student''' within BlogNomic.
* A '''Student''' should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* A '''Student''' should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
* A '''Student''' should not edit their own blog comments once posted, nor those of any other '''Student'''.
* A '''Student''' should not edit the "Entry Date" field of a blog post.
* A '''Student''' should not make a DoV primarily to delay the game by putting it into Hiatus.
* A '''Student''' should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).
</div>

= Dynastic Rules =
==Student Handbook==
Each Student other than the Headmaster is assigned to a Dormitory, which is tracked in the GNDT, and is one of the following:

#Gothmog Hall
#Ichneumon Hall
#Penanggalan Hall
#Bandersnatch Hall

When an Admin adds a Student without a Dormitory to the GNDT, that Admin shall assign them to the Dormitory with the fewest Students. (If several Dormitories are tied for this, the tie is resolved randomly using a GNDT die roll.)

If a Student is assigned to a Dormitory which has more Students in it than any other Dormitory, and a Dormitory exists which has fewer Students than any other Dormitory, then the Student may change their assignation to the latter Dormitory.

All Students have a Condition, which can be Alive, Ghost, or Zombie. This is tracked in the GNDT. New Students start Alive.

Each Student may have a number of Enchantments affecting them, listed in a GNDT field “Enchantments” and separated by commas. If an Enchantment includes a number, that number is its Force. Students begin with no Enchantments.

===Incorporeality===
A Student whose Condition is Ghost may not achieve or declare victory. Where contradictory, this rule supersedes all other rules.

==Free Time==

An Alive or Zombie Student is Free if they have not posted a valid Class Action on any currently Open Lesson, and are not on Detention.

A Ghost Student is Free if they are not on Detention.

==Nomich==

Nomich is a sport played by Students. It may only be played on a Saturday. Students who belong to the same Dormitory are always on the same team.

Nomich is played with an ordinary deck of 52 cards. At all times when not playing a game of Nomich, each Dormitory should be holding seven cards. The cards held by each Dormitory should be kept a secret to all other Dormitories and should be tracked by the Headmaster. If, at any time, a Dormitory is holding less than seven cards and is not playing a Nomich, the Headmaster should assign them enough cards that they have a hand of seven, and should then send a private message to all prefects of that Dormitory telling them the composition of their new hand. These Prefects must truthfully relay the hand’s composition to the other members of their Dormitory at the earliest opportunity. The Headmaster must ensure that the same card is not being held by more than one Dormitory at any given time.

Any member of a Dormitory may challenge another Dormitory to a match of Nomich by making a post to that effect. A Dormitory is obliged to accept the first such challenge levelled against it on a Saturday. Each Dormitory may play no more than one match of Nomich per day, and a Dormitory may not make a challenge if it is playing a match of Nomich or has already played a match of Nomich that day; nor can a challenge be levelled against a Dormitory that is playing or has played a match of Nomich that day. A Student in Detention can not issue or respond to a Nomich Challenge.

Once a Dormitory has challenged another Dormitory to a match of Nomich, each Dormitory has 24 hours to post a play in the comments to the challenge post. A play is a sequence of cards, of any size or composition, from the Dormitory’s hand that the Dormitory intends to score against. The Dormitory whose play scores highest wins the match. Any member of a Dormitory whose Condition is Alive may post a play on behalf of their Dormitory, and the first play posted by a Dormitory in a challenge thread is the one that is scored for that match. If a Dormitory does not post a play on a Challenge, they are assumed to have declined (i.e. not accepted) the challenge if it is be legal to do so, or played a sequence containing no cards otherwise. When a Challenge is declined in this manner it ceases to be a Challenge. Once a legal play has been made by both Dormitories, all cards in those plays are removed from the hands of the Dormitories involved. If both Dormitories in a match have the same score, the Headmaster shall choose one of them as the winner of the match.

The score value of any play is adjudged according to the Nomich Ruleset. The Nomich Ruleset is secret and should be known in its entirety only to the Headmaster. The first rule in the Nomich ruleset is as follows:

<blockquote>The play with the largest cumulative face value scores 5 points. In Nomich, an Ace is considered have a face value of 1, a Jack to have a face value of 11, a Queen to have a face value of 12, and a King to have a face value of 13.</blockquote>

At the end of each Sunday, or as soon as possible thereafter, the Headmaster should indicate in each challenge thread which Dormitory won and what each play scored.

A Dormitory who wins a game of Nomich may perform one of the following actions:

* Add a new rule to the Nomich ruleset by PMing it to the Headmaster
* Change the Condition of one Student of the opposing Dormitory to Ghost or Zombie
* Choose a Teacher and a Student and, if that Teacher has a Grudge against that Student, remove that Grudge
* Pick any Subject, and increment the grade in that Subject by one for all Students in the winning Domitory

The Headmaster shall interpret the first private message specifying one of these actions from a Prefect of the winning Dormitory to be that Dormitory’s choice.

The Headmaster shall appraise any proposed addition to the Nomich Ruleset and may choose to accept or reject it. Any rule thus rejected is lost and the Dormitory who proposed it may not undertake another winning action.

==Grades==

Each Student has a Grade in each of the main Subjects: Beginner’s Alchemy (ALC), Wild Beasts (BST), Recreational Necromancy (RNY), Divination (DIV), Explosive Latin (LAT), and Unbridled Evil (UNE). These are tracked in the GNDT. A Grade may be (in descending order) A+, A, B, C, D, E, F or Ungraded (”-”) and each Student’s Grade for each Subject starts as Ungraded. If a Grade would be incremented above A+, it remains A+; if it would be decremented below F, it remains F.

Each Grade corresponds to a Spell Power, which may be negative. A Student with a Grade of A+ in a Subject has a Spell Power of 5 in that Subject. Similarly, A gives 3 Spell Power, B gives 2, C gives 1, D gives -1, E gives -3 and F gives -5. Ungraded Grades give a Spell Power of -10.

==Lessons==

As a daily action, the Headmaster may call a Lesson by posting a blog entry with the subject “[SUBJECT] Lesson: [LEVEL] [SPECIALISATION] with [TEACHER]”, where [SUBJECT] is a Subject, [LEVEL] is an optional adjective of either “Basic”, “Intermediary” or “Advanced” (if omitted, the Lesson is counted as Intermediate), [SPECIALISATION] is any word or phrase and [TEACHER] is the Teacher who will give the Lesson. An Advanced Lesson may only be given by a Teacher who has that Subject as their Field.

If a Student is Free, they may take one of the following Class Actions in that Lesson:

* If a Student Studies in a Basic Lesson, they may either set their Grade in that Lesson’s Subject to ‘C’, or increment their current Grade in that Lesson’s Subject to a maximum of 'B'.
* If a Student Studies in an Intermediate Lesson, they may either set their Grade in that Lesson’s Subject to ‘C’, or increment their current Grade in that Lesson’s Subject to a maximum of 'A'.
* If a Student Studies in an Advanced Lesson, they may either set their Grade in that Lesson’s Subject to ‘E’, or (if their Grade is D or higher) raise their current Grade in that Lesson’s Subject by two levels.
* If a Student Brown Noses, they stand a chance of becoming Teacher’s Pet at the end of the lesson.
* If a Student Disrupts an Intermediate or Advanced Lesson for which they have a Grade of E or higher, they may set their Grade in that Lesson’s Subject to ‘F’ and trigger that Lesson’s Disaster, as listed in the “Disasters” rule.
* If a Student Distracts in an Intermediate or Advanced Lesson, they may decrement (to a minimum of “E”) the Grade in that Subject of up to 3 Students who have Studied most recently in the lesson. (This action counts as a Disruption.)

Lessons can either be Open or Ended, and begin as Open. If a Lesson has been Open for more than 24 hours, the Headmaster may end it by leaving a comment on the blog entry to that effect. If a Lesson has been Open for 48 hours, it ends.

When a Lesson ends:
* The Headmaster shall give the Teacher of the Lesson a Grudge against any Students who Disrupted the Lesson.
* If any students posted comments that were not Class Actions, the Headmaster may, at their discretion, give the Teacher of the Lesson a Grudge against any or all of those Students as if they had Disrupted the Lesson.
* If any Students Brown Nosed during the Lesson, the Headmaster shall select the Student among them with the lowest number of Grudges held against them collectively by the faculty (resolving ties randomly) to become that Teacher’s Pet.

The prefects of the Dormitories can request a Lesson to be given by the teacher assigned to their dormitory. After such a request is posted in a story post, the headmaster must advise this teacher to give a lesson in his subject. In any case a teacher can give only one lesson at a time.

===Chores===

If a Student is on Detention, they may choose to carry out Chores by posting a comment to this effect in an Open Lesson by the Teacher assigned to their Dormitory. If they do so, when that Lesson ends, if the Student is not the subject of a Grudge by every Teacher, that Student is no longer on Detention.

===Disasters===

* If a Disaster occurs in a '''Beginner’s Alchemy''' Lesson, noxious fumes fill the classroom. No further Class Actions may be taken in this Lesson.
* If a Disaster occurs in a '''Wild Beasts Lesson''', the subject matter runs amok. Any Alive Student who has taken a Class Action other than “Studying” in the Lesson becomes a Zombie.
* If a Disaster occurs in a '''Recreational Necromancy''' Lesson, a greenish-white glow fills the room. Any Zombie or Ghost who has taken a Class Action in the Lesson becomes Alive.
* If a Disaster occurs in a '''Divination''' Lesson, the Students get a harrowing glimpse of their future. Each Student who has taken a Class Action in the Lesson has their Grade reduced by one level in every Subject.
* If a Disaster occurs in an '''Explosive Latin''' Lesson, a magical fight breaks out. The Alive Student with the lowest Grade in Explosive Latin who has taken a Class Action in the Lesson (if only one such Student exists) becomes a Zombie.
* If a Disaster occurs in an '''Unbridled Evil''' Lesson, the pupils cheer. Any Alive Student who has taken a Class Action in the Lesson becomes a Zombie.

If a Disaster is triggered by a Disruption by a Student, that Student is immune to the effects of the Disaster.

===Class Actions===

A Student may take a Class Action in an Open Lesson by posting a comment to that Lesson’s entry, describing their behaviour. A Class Action must begin with one of the following phrases:

* ‘Studying’.
* ‘Brown Nosing’.
* ‘Distracting’.
* ‘Disrupting’.

The first comment posted by a Student on an Open Lesson’s entry that matches this criteria shall count as that Student’s Class Action for the Lesson.

==Teachers==

Professor Abalone’s School of Witchcraft and Miscellany has a number of Teachers, listed in the BlogNomic wiki page “[[Teachers]]”. Each Teacher has a Name, a Field (any Subject), a Condition (Alive, Ghost, or Zombie), a Pet (None, or STUDENT’S NAME) and a Grudge against any number of Students. The Headmaster may hire new Teachers at any time by adding them to the wiki page; new Teachers have a Name, Field and Condition of the Headmaster’s choosing, a Pet status of None, and no Grudges.

If a Student is the subject of a Grudge by every Teacher, then that student is put on Detention.

===Teacher’s Pet===

As a weekly action, a Student may Wheedle a Teacher, so long as they are that Teacher’s Pet. Upon doing so, they may give that Teacher a Grudge against any Student, and/or remove a single Grudge that that Teacher has.

===Resident Scholar===

2.6.2 Resident Scholar. Each dormitory is overseen by one of the full time faculty. No Teacher may be assigned to more than one Dormitory. If a dormitory currently has no Teacher assigned to it, then the Headmaster shall randomly assign a Teacher to that dormitory. If a Teacher is assigned to a dormitory, then that information will be noted in the Teacher’s profile on the wiki.

Students within a dormitory may attempt to request a change in the Teacher assigned to their dormitory. As a weekly action, a student may publish a post entitled “Request for Change of Faculty Supervisor” and within which they will nominate a new Teacher, designate a Dormitory (Which must be the Dormitory the posting student resides in) and offer a reason as to why they would like a change to occur.

Resolution of the Request for Change of Faculty Supervisor is handled in the following fashion:
* Students who reside within the Dormitory may vote ‘for’ or ‘against’ the change by commenting on the post.
* If the designated Faculty Member is currently overseeing another Dormitory, residents of that Dormitory may vote ‘for’ or ‘against’ the change by commenting on the post.
* The Headmaster may vote ‘for’ or ‘against’ the change by commenting on the post and his vote shall be counted twice.
* For each Grudge the Teacher holds against a Student in the requesting Student’s dormitory, add a vote of ‘against’ towards the Request for Change of Faculty Supervisor. These votes will be tallied by the posting Student and posted as a comment. Failure to do so within 48 hours of the original post will result in the Request failing.
* If the designated Teacher is currently overseeing another Dormitory, for each Grudge he or she holds against a student in the Dormitory he or she is currently overseeing, add a vote of “for” towards the Request for Change of Faculty Supervisor.These votes will be tallied by the posting Student and posted as a comment. Failure to do so within 48 hours of the original post will result in the Request failing.
* After a 48 hour period, if the number of “for” votes exceeds the number of “against” votes, then the designated Teacher will be unassigned from their current Dormitory and assigned to the designated Dormitory. At this time the Headmaster shall assign a new Teacher to any Dormitory that currently has no assigned Teacher. If the number of “against” votes exceeds or ties the number of “for” votes, then no change will occur.

===Lord Marvolo===

Professor Abalone’s School of Witchcraft and Miscellany goes through cycles of Light Ascendancy, when the Headmaster and Alive Students have the upper hand, and Dark Ascendancy, where Lord Marvolo and the Zombie Students are more powerful. The school is normally considered to be in a time of Light Ascendancy. While the number of Loathed Deans held by all Students is at least twice the number of Loved Deans held by all Students, and the total number of all Deans is greater than 25, the school is considered to be in a time of Dark Ascendancy.

As a weekly action, and only if no other Student has done so within the preceding five days, a Zombie Student may Channel Lord Marvolo by callling a Lesson under the same rules as regular Lessons. However, the Teacher of the Lesson must be Lord Marvolo, and the Subject must be Unbridled Evil. Students who are Alive may not Study in such Lessons, and Students who are Zombies may not Disrupt them.

==Library==

The School Library has a vast collection of books, but zombies have been known to hide among its shelves. As a weekly action, a Student who is Alive may Study in the Library by incrementing their Grade in any one main Subject. As a weekly action, a student who is a Zombie may convert to Zombie status any other student who Studied in the Library in the previous 24 hours and is still Alive.

==Spells==

All Students have access to a number of Spells, listed in subrules to this rule. All spells have a Difficulty Level in one or more subjects, which may be negative, and an Effect.

A student (the caster) may attempt to cast a spell as a weekly action. To do so, they must make a post with the title “Casting {Spell}, where {Spell} is the name of the spell they intend to cast. If the Effect of that spell requires a target, one must be specified in the body of the post. Students who share a dormitory with the caster may join in the casting by adding a FOR icon in a comment to the post. The caster may complete the spell once within 48 hours of making the post and, if for each subject in which the Spell has a Difficulty level the sum of Spell Power of all participating Students (including the caster) in that subject meets or exceeds the Difficulty Level, execute the Effect of the spell. Add 1 to the calculated Spell Power of any subject that matches the Field: (Subject) of the Teacher assigned to the casting Student’s Dormitory.

Unsupervised spellcasting is a stressful and often dangerous experience. After completing a Spell, the Caster must decrement his or her Grade in any Subjects for which that Spell had a Difficulty Level.

===Revive===
:'''Difficulty level:''' RNY 15; ALC 0
:'''Effect:''' Set the condition of the targeted Student to Alive.

===Transmute Card===
:'''Difficulty level:''' DIV 1, ALC 1
:'''Effect:''' If the target Nomich card is held by a Dormitory, the Headmaster shall replace it with a random other legal card. If the target Nomich card is also in a play, the Headmaster post the result in a comment to the challenge containing that play, and the play is amended to use the new card in place of the targetted one.
===Cartomancy===
:'''Difficulty level:''' DIV 0
:'''Effect:''' The caster gains a “Cartomancy X” Enchantment, where X is the total Spell Power in Divination of all participating Students (including the caster). When a Student makes a Nomich play, they may remove a Cartomancy Enchantment from their Enchantments to add a single card of any suit to that play, with a face value up to the Enchantment’s Force. This card must be denoted by [square brackets] and may not have a face value greater than K (13).
===Autodecapitatum===
:'''Difficulty level:''' RNY 0
:'''Effect:''' Set the caster’s Condition to Zombie or Ghost. If the total Spell Power in Recreational Necromancy applied to this spell is at least 5, the caster may also choose any Student and set that Student’s Grade in one Subject to F. If the caster’s Condition was Zombie or Ghost when they began casting this spell, their Grade in Recreational Necromancy is set to F.

===Guardian Toothfish===
:'''Difficulty level:''' BST 0
:'''Effect:''' The caster gains a “Toothfish” Enchantment. If a Student with a Toothfish Enchantment would have their Grade in a Subject decremented as a result of a Disruption Class Action, that Grade is not decremented and they instead lose one Toothfish Enchantment. If a Student with a Toothfish Enchantment would be the target of a Bullying or Incitement action, then nothing happens and they instead lose one Toothfish Enchantment.
===Marvolo's Challenge===
:'''Difficulty Level:''' UNE:10 RNY 8, LAT 6, ALC 4, DIV 2
:'''Effect:''' If the school is in a time of Light Ascendancy, the caster may choose to do either or both of the following:
:* Change one Alive Student to Zombie
:* Change one Alive Student to Ghost
:If the school is in a time of Dark Ascendancy, the caster must roll a DICE10 for each Alive Student as if they were targeted by the Bullies, and apply the resulting effect as per “During Dark Ascendancy”. This action counts as an Incitement action, but it ignores the seven-day limit, and does not count for the weekly action of Inciting the Bullies.
:If this Spell would be cast as a result of its own Effect, instead cast it as if the school were in a time of Light Ascendancy.
===Potion of Fast Learning and Temporary Haunting===
:'''Difficulty Level:''' ALC (-3)
:'''Effect:''' If the Targeted Student is not the Caster and doesn’t join, this spell does nothing.
:If the Targeted Student was in a class that has not ended when the spell is cast, that class counts as having ended for that student. The student cannot be the target of Disruptions for that class and is not affected by the Disasters triggered in that class.
:If the caster has an ALC of D, E, F or Ungraded when the spell resolves (but before decrementing ALC as part of the cost for casting the spell), the caster must roll a DICE2 in the GNDT before the effect is applied. On a 1, the Targeted Student’s Condition becomes Ghost. Other effects work as normal.
===Headmaster's Protection===
:'''Difficulty level:''' ALC 10, BST 8, RNY 6, LAT 4, DIV 2
:'''Effect:''' If the school is in a time of Dark Ascendancy, the caster may choose to do either or both of the following:
:* Change one Zombie Student to Alive
:* Change one Zombie Student to Ghost
:If the school is in a time of Light Ascendancy, all Alive Students gain a “Toothfish” Enchantment, and the caster gains an additional “Toothfish” Enchantment.

==Explosive Language==
Explosive Latin is the language of spellcasting. Whenever a Student casts a Spell, they must roll DICE10 in the GNDT, and add the Spell Power that Student has in LAT to the result, plus the number of Chocolate Basilisks the Student has eaten in the past hour. If the result is a 1, 2 or 3 then an accident occurs.

If an accident occurs, the spell fails but the Student does not have to decrement their Grade. Instead they may increment their grade in LAT and, if they are Alive, set their Condition to either Zombie or Ghost (their choice).

==Titles==

A Student may have a Title, which may be:-

* Prefect
* Student Corpus President
* School Mascot
* Salutorian
* Lieutenant of the Pep Squad
* University Mrrrgrannahh

===Prefects===

At any time, the Headmaster may remove the Prefect title from any or all Students belonging to a given Dormitory, then assign the Prefect title to up to two Students in that Dormitory who are not in Detention, do not have a Title, and who have or are tied for the highest or second-highest combined total Spell Power in all subjects.

===School Mascot===

The School Mascot wears the traditional Mascot’s Hat, a jingling jester’s cap impregnated with a powerful anti-magic aura. As a result, the Mascot can neither cast Spells, nor be the target of Spells (that is, a Spell cannot select the School Mascot as a “targeted Student”).

If a Student (the “Chump”) has no Title, and for each Subject there is no Student with a lower Grade in that Subject than the Chump, then the Chump is a potential Mascot. If only one Student (other than the Headmaster) is a potential Mascot, any Student may remove the School Mascot Title from any Student who has it, and then set the potential Mascot’s Title to “School Mascot”.

==Snitching==

As a weekly action, a Student may Snitch by PMing the Headmaster with the name of a lesson that has not ended and the name of a student who they suspect will attempt to disrupt that lesson. If the named student subsequently does disrupt that lesson, then the Snitching student becomes the Teacher’s Pet of the teacher of the affected lesson, and the disruptive student gets Detention.

If two or more Students correctly Snitch on the same Student for the same Lesson, then the one who Snitched first gets to be Teacher’s Pet, but the one who Snitched last becomes the subject of a Grudge from the Lesson’s Teacher when the Lesson is Ended.

==Detention==

If a Student has been in Detention for more than seven days, they may, as a weekly action, remove one Grudge held against them by any one Teacher.

If a Student is in Detention for three weeks without interruption then they become a Ghost.

==Sweets==

Each Student may have a number of Sweets, listed in the GNDT as “Tuck”. A Student may, as a weekly action, visit the Tuck Shop, and award themselves any number of Sweets from the following priced list, to a maximum value of 10p.

* Sugar Lungorthin - 5p
* Jenglot Baby - 4p
* Jelly Dean - 3p
* Chocolate Basilisk - 2p
* Vorpal Chew - 1p

A Student may eat a Sweet they own, at any time, by removing it from their Tuck.

If a Student has a Jelly Dean, they may roll DICE4 to unwrap it. If the result is N or less, the Jelly Dean becomes a Loved Dean. Otherwise, it becomes a Loathed Dean. N is 1 if the Student is a Zombie, 2 if they are a Ghost and 3 if they are Alive.

==Ascendancy==

Professor Abalone’s School of Witchcraft and Miscellany goes through cycles of Light Ascendancy, when the Headmaster and Alive Students have the upper hand, and Dark Ascendancy, where Lord Marvolo and the Zombie Students are more powerful. The school is normally considered to be in a time of Light Ascendancy. While the number of Loathed Deans held by all Students is greater than the number of Loved Deans held by all Students, and the total number of all Deans is greater than 25, the school is considered to be in a time of Dark Ascendancy.

==The Bullies==

Blodger, Scraggs and Venter are, collectively, the school Bullies. The effect that they have on the game depends on the current Ascendancy.

===During Light Ascendancy===

During Light Ascendancy, the bullies’ fear of punishment and the Headmaster limits their capacity for mischief. Once, within 24 hours of a Student (“the Nerd”) carrying out Chores or becoming a Teacher’s Pet, any other Student may make a Bullying roll by posting “Bullying: DICE2” in the GNDT. If the result is a 1, then the Bullies attack the Nerd, stealing all of their sweets - their Tuck is set to -.

===During Dark Ascendancy===

During Dark Ascendancy, the vicious natures of the Bullies become more apparent. As a weekly action, and only if no Student has done so within the preceding seven days, whichever Student has most recently Channelled Lord Marvolo may incite the bullies.

To do so, they must make an Incitement roll to the GNDT by posting “Incitement: DICEx DICE10”, where x is the number of Students whose condition is Alive. The result of the DICEx roll determines which Student is Bullied by the Incitement and corresponds to the order in which Student names are listed in the GNDT. The result of the DICE10 determines the outcome of the incitement.

*On a roll of 1, the Bullied Student is wedgied to death and becomes a Zombie.
*On a roll of 2, the Bullied Student is conventionally bullied and their Tuck is set to -.
*On a roll of 3 or 4, the Bullied Student is corrupted by the Bullies; their UNE is incremented.
*If the result anything from 5 to 9, the Student successfully hides from the bullies. There is no effect.
*On a roll of 10, the Bullies’ manage enough articulation to actually cast a spell. Let Z be the result of DICEY, where Y is the number of subrules to Rule 2.8; the Spell described in Rule 2.8.Z is cast. The caster of the spell and (if required) the targeted Student are both the Bullied Student. The inciter may make any other decisions required by the spell.

==Lavatory Studies==

A Student may, as a weekly action, lock themself in a lavatory stall and experiment with advanced magic. This is done by posting a comment in the GNDT in the form “Lavatory for [SUBJECT]: DICE6”, where [SUBJECT] is any of the legal academic Subjects. Depending on the result of that die roll, the effects are as follows:

* On a 1-4, the Student may increment their Grade in that Subject by one; or, if their Grade in that Subject is currently Ungraded, set it to C.
* On a 5, nothing happens.
* On a 6, the Student has made a hideous mistake. If they are Alive or Zombie, they must set their Condition to Ghost; if they are a Ghost, they must set their grade in the attempted Subject to F.

==Graduation==

If there is ever exactly one Student whose condition is Alive, that Student achieves victory. If there is ever exactly one Student whose condition is Zombie, that Student achieves victory.

If there is ever exactly one Student who has a grade of A+ in five Subjects, that Student achieves victory.

<div style="padding:8px;background:#ddd;">

= Glossary =

==Keywords==
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

;Can
:"is able to"

;Comment
:A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Core Proposal
:A Proposal whose changes are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more '''Students'''.

;Daily Action
:If a game action is a Daily Action, each '''Student''' able to perform it may take that action once each day, but not more than once every six hours.

;Day
:References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 GMT, ending when the next day begins. It can never be 2 different days at the same instant.

;Dice
:References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

;Dynastic Proposal
:A Proposal whose only changes are the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.

;Effective Vote Comment (EVC)
:A '''Student''''s Effective Vote Comment with respect to a given Proposal means that '''Student'''’s Comment to that Proposal (if any) that contains that '''Student'''’s Vote on the Proposal that is given effect in accordance with Rule 1.4 when the Proposal is Resolved, not including explicit Votes of abstention..

;Flavour Text
:When posting a blog entry, a '''Student''' may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

;Gamestate
:Any information which the Ruleset regulates the alteration of.

;IRC Channel
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

;May
:"is permitted to"

;Post
:A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]

;Quorum
:Quorum of a subset of '''Student'''s is half the number of '''Student'''s in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of '''Student'''s it is referring to, it is referring to a Quorum of all '''Student'''s.

;Resolve/Resolution
:If used in a context of Proposals, Call for Judgements or Declarations of Victory, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Proposal, a Call for Judgement or a Declaration of Victory. The world “Resolution” means then the act of doing so. If used in another context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words.

;Shall
:"is required to"

;Should
:"is recommended that"

;Story Post
:A Story Post is an Official Post that is not a member of any specific category of Official Posts mentioned or defined in a Core Rule (excluding Official Post).

;Subject
:The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.

;Votable Matter
:The word “Votable Matter”, means a Proposal, a CFJ or a DoV.

;Vote
:The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule 1.4 “Voting”. The word “Vote”, used as a verb, means the act of casting such a Vote.

;Voting Icons
:For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.

;Week
:References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.

;Weekly Action
:If a game action is a Weekly Action, each '''Student''' able to perform it may take that action once each week, but not more than once every twenty-four hours.

;Wiki
:The BlogNomic Wiki at http://blognomic.com/wiki/index.php?title=Main_Page

==Clarifications==

===Numbers and Variables===
* Unless otherwise specified, game variables defined to hold numeric values can hold only non-negative integers, and any action that would set those values below zero instead sets them to zero. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* All numbers, unless stated otherwise by a rule, are in base ten.
* Unless otherwise specified, when “X” is a number, to spend X of a numeric value “V” means to subtract X from V (i.e. replace V with V-X); to gain X of a numeric value “V” means to add X to V; and to transfer X of a numeric value “V” from A to B means to subtract X from A's V and add the amount A's V was reduced by to B's V. Unless otherwise specified, a rule that allows '''Student'''s to transfer a numeric value only allows them to transfer that value from themselves to another '''Student''' (of their choice unless otherwise stated).
* A '''Student''' who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one of those values to an illegal value.
* If a rule implies that the result of a division should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the division is instead the result rounded towards 0.
* 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.

===Rules and Proposals===
* If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
* Where a [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
* Rules which trigger upon the Enactment or Failure of a Proposal are the responsibility of the Admin who Enacts or Fails it.

===Time===
* For the purpose of all rules, time in Blognomic is in GMT.
* All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

===Spelling===
* Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

===Names===
* Within the ruleset, a word only refers to the name of a '''Student''' if it is explicitly stated that it refers to a '''Student''''s name.

</div>

Loot

2010-07-24T09:29:58Z

Purplebeard: /* 1 */

__NOTOC__
==1==
{| border="1"
|-
! Amount
! Enchantment
! Item
|-
| 2
|
| spellbook of Force Bolt
|-
| 3
| +0
| quarterstaff
|-
| 2
|
| wand of cold
|-
| 7
|
| Food Ration
|-
| 2
| +0
| Short Sword
|-
| 17
| +0
| Dagger
|-
| 2
|
| Lock Pick
|-
| 1
|
| Unidentified potion
|-
| 2
| +0
| Cloak of Magic Resistance
|-
| 1
| +1
| Ring Mail
|-
| 1
| +0
| Leather Armour
|-
| 1
| +0
| Ring Mail
|-
| 1
| +1
| Mace
|-
| 2
|
| Potion of Holy Water
|-
| 2
|
| Potion of Healing
|-
| 3
|
| Amulet Beacon
|-
| 1
| +0
| Longsword
|-
| 1
| +1
| Leather Armour
|-
| 30
| +2
| Dart
|-
| 1
| +0
| Hawaiian Shirt
|-
| 3
|
| Bag of Gold
|}

==2==

==3==
{| border="1"
|-
! Amount
! Enchantment
! Item
|-
| 1
| -
| Unidentified Potion
|-
| 1
| +0
| mace
|-
| 1 || +0 || ring mail
|-
| 1 || || food ration
|-
| 1 || || Amulet Beacon
|}

==4==
{| border="1"
|-
! Amount
! Enchantment
! Item
|-
| 1
| +0
| Cloak of Magic Resistance
|-
| 2
| +0
| Two-Handed Sword
|-
| 1 || +3 || small shield
|-
| 1 || +2 || two-handed sword
|-
| 1 || +1 || dagger
|-
| 1 || +2 || Dwarven Chain Mail
|-
| 1 || +2 || leather gloves
|-
| 1 || +2 || Hawaiian Shirt
|-
| 1 || +3 || robe
|-
| 1 || || food ration
|-
| 1 || || unidentified potion
|-
| 1 || +0 || shortbow
|}

==5==

==6==
==7==
==8==
==9==
==10==

Settlement

2010-04-21T08:10:37Z

Purplebeard: Grazing

<pre>

ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz

0 ....................T...............................
1 ................................t...................
2 .....T.....................................T........
3 ................t...................................
4 ....................................................
5 ....t...............................................
6 ...................................bt...............
7 ~~~~...............................CCC.......T......
8 ~~~~~~~~~~~~~~~~~~~~~...............................
9 ~~~~~~~~~~~~~~~~~~~~~~~~~III~~~~~~~~~~~~~~~~~~~~~~..
10 ~~~~~~~~~~~~~~~~~~~~~~~~~III~~~~~~~~~~~~~~~~~~~~~~~~
11 ...~~~~~~~~~~~~~~~~~~~~~~III~~~~~~~~~~~~~~~~~~~~~~~~
12 .......................~....~....~~~~~~~~~~~~~~~~~~~
13 ........................_...~....................~~~
14 ...............................................t....
15 ..T.....t...........................................
16 .......................tb...........................
17 ......................................T.............
18 ....................................................
19 .................................................t..
20 .......t........................t...................
21 ....T...............................................
22 ....................................................
23 ......................T......................T......
24 ....................................................
25 ..T................................................#
26 .........t.......................................###
27 ..............................##..............######
28 .............................####..........#########
29 ..t...T................###...+..####...#############
30 ...........###############..#.#.+..#################
31 ....##################.k.+..#.#.#.a#################
32 .#####################...##+#.#.####################
33 ######################...#.b..#.####################
34 ###########################...#.####################
35 ###########################...#.####################
36 ###########################...#.####################
37 ###########################...#.####################
38 ###########################...#.####################
39 ###########################..##.####################
40 ###########################..##.####################
41 ###############################.####################
42 ###############################.####################
43 ###############################.####################
44 ###############################.####################
45 ###############################....#################
46 ###############################.ba..################
47 ###############################....#################
48 ####################################################
49 ####################################################
50 ####################################################

Legend:

Empty:
. Dirt
+ Door
; Seedling
_ Channel
% Smoke
a Table
b Bed
c Small Crop
C Mature Crop
H Chimney
I Bridge
k Stove
t Bush or small Tree
y Catapult

Occupied:
~ Water
# Rock
O Wall
T Large Tree

</pre>

County Activity

2010-03-29T09:55:28Z

Purplebeard: Corrections.

Trade routes:
*Iron: '''Staffordshire''' <span style="color:#FF0000">'''|'''</span> Warwickshire, Gloucestershire, Wiltshire, Hampshire
*Wood: '''Hertfordshire''', Bedfordshire, '''Huntingdonshire'''
*Quicksilver: '''Westmorland''', Lancashire, Cheshire, '''Shropshire'''
*Caffeine: '''Westmorland''', Lancashire, Cheshire, '''Shropshire''' <span style="color:#FF0000">'''|'''</span> Herefordshire, Gloucestershire, Somerset, Devon
*Cogs: '''Dorset''' <span style="color:#FF0000">'''|'''</span> Hampshire, Sussex
*Gems: '''Lancashire''', Yorkshire, '''Lincolnshire''' <span style="color:#FF0000">'''|'''</span> Cambridgeshire
*Coal: '''Derbyshire''', Leicestershire, Lincolnshire, '''Norfolk'''
----
[[Image:England traditional counties.png|300px|thumb]]

#'''Bedfordshire''': Wood x1.5
#<span style="color:#FF0000">'''Berkshire'''</span>: No changes.
#<span style="color:#FF0000">'''Buckinghamshire'''</span>: No changes.
#<span style="color:#FF0000">'''Cambridgeshire'''</span>: No changes.
#'''Cheshire''': Caffeine x1.5, Quicksilver x1.5
#'''Cornwall''': No changes.
#'''Cumberland''': No changes.
#'''Derbyshire''': Coal x0
#<span style="color:#FF0000">'''Devon'''</span>: no changes.
#<span style="color:#FF0000">'''Dorset'''</span>: no changes
#'''County Durham''': No changes.
#<span style="color:#FF0000">'''Essex'''</span>: No changes.
#<span style="color:#FF0000">'''Gloucestershire'''</span>: No changes.
#'''Hampshire''': No changes.
#<span style="color:#FF0000">'''Herefordshire''':</span> No changes.
#'''Hertfordshire''': Wood x0
#'''Huntingdonshire''': Wood x2
#<span style="color:#FF0000">'''Kent'''</span>: No changes.
#'''Lancashire''': Caffeine x1.5, Gems x0, Quicksilver x1.5
#'''Leicestershire''': Coal x1.5
#'''Lincolnshire''': Coal x1.5, Gems x2
#<span style="color:#FF0000">'''Middlesex'''</span>: No changes.
#'''Norfolk''': Coal x2.
#<span style="color:#FF0000">'''Northamptonshire'''</span>: No changes.
#'''Northumberland''': No changes.
#'''Nottinghamshire''': No changes.
#<span style="color:#FF0000">'''Oxfordshire'''</span> (liberated by Keba): No changes.
#'''Rutland''': No changes.
#'''Shropshire''': Caffeine x2, Quicksilver x2
#<span style="color:#FF0000">'''Somerset'''</span> (liberated by Keba): No changes.
#'''Staffordshire''': Iron x0.
#<span style="color:#FF0000">'''Suffolk'''</span>: No changes.
#<span style="color:#FF0000">'''Surrey'''</span>: No changes.
#<span style="color:#FF0000">'''Sussex'''</span>: No changes.
#<span style="color:#FF0000">'''Warwickshire'''</span>: No changes.
#'''Westmorland''': Caffeine x0, Quicksilver x0
#<span style="color:#FF0000">'''Wiltshire'''</span>: No changes.
#'''Worcestershire''': No changes.
#'''Yorkshire''': Gems x1.5

Admin FAQ

2008-11-11T12:25:11Z

Purplebeard: Argh, I forgot to change the title. This is not a FAQ at all!

Ruleset 53

2008-04-08T17:19:03Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==
This is the Ruleset for BlogNomic; all '''Captains''' must obey it. Section One consists of the "core rules" of BlogNomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the glossary, which exists solely to clarify the remainder of the ruleset. Rules may be referred to by their type and entire number or type and name. (e.g. This Rule may be referred to as Rule 1.1 or the Rule entitled "Ruleset and Gamestate"). If a Proposal refers to a Rule by number and that Rule has been renumbered since the Proposal posting, that Proposal does nothing if enacted.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

'''Admins''' may correct obvious spelling and typographical mistakes in the Ruleset at any time.

== Captains ==

Anybody may apply to join BlogNomic (if he is not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing her arrival. An '''Admin''' will add her to the roster in the sidebar, at which moment he becomes a '''Captain'''.

A '''Captain''' may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A '''Captain''' may only change her name as a result of a proposal approving the change.

Some '''Captains''' are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. '''Captains''' who wish to become '''Admins''' shall sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves '''Admins'''. Existing '''Admins''' may be removed from their posts by Proposal, CfJ, or voluntary resignation.

Some '''Captains''' are '''Idle''', and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules 1.1, 1.2 and 1.8, Idle '''Captains''' are not counted as '''Captains'''. '''Admins''' may render a '''Captain Idle''' if that '''Captain''' has asked to become '''Idle''' or if that '''Captain''' has not posted a entry or comment for more than 7 days. '''Admins''' may de-Idle a '''Captain''' at her request - the '''Captain's''' personal gamestate retains the values it had immediately prior to her going Idle. If one or more values would be undefined, it is set to the value new '''Captains''' receive, if such a value exists.

A single person may not control more than one '''Captain''' within BlogNomic. If anybody is suspected of controlling more than one '''Captain''', then a Proposal may be made to remove any number of such '''Captains''' from the game, and to bar the perpetrator from rejoining.

== Proposals ==

Any '''Captain''' may submit a Proposal to change the Ruleset or Gamestate, by [http://blognomic.com/update/index.php?C=publish posting an entry] in the "Proposal" category that describes those changes (unless the Captain already has 2 Proposals pending, or has already made 3 Proposals that day).

Proposals can either be Pending, Enacted, or Failed. When a Proposal is first put forward, it is considered Pending.

== Voting ==

Any '''Captain''' may cast her Vote on a Pending Proposal by making a comment on that entry using a voting icon of FOR, AGAINST or DEFERENTIAL.

If the '''Captain''' who made a Proposal has not cast a Vote on it, her Vote is counted as FOR. If a '''Captain''' casts more than one Vote on a Proposal, only the most recent of those Votes is counted. If a '''Captain''' leaves the game or goes Idle, her Vote no longer counts. If a '''Captain''' votes against her own proposal, that vote may not be changed. This is referred to as a Self-Kill.

A vote of DEFERENTIAL is a vote of no opinion, or of faith in the decision of the [[#Dynasties|Dread Pirate]]. The vote will count as the same as '''the Dread Pirate's''' vote. The '''Dread Pirate''' cannot cast a vote of DEFERENTIAL. If there is no '''Dread Pirate''', a vote of DEFERENTIAL counts as an explicit vote of abstention.

== Enactment ==

The oldest pending [[#Proposals|Proposal]] may be enacted by any '''Admin''' (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) if either of the following is true:-

* It has a number of FOR votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed or self-killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid vote, more than half of its votes are FOR, and it has not been vetoed or self-killed.

The oldest pending Proposal may be failed by any '''Admin''', if any of the following are true:-

* It has enough AGAINST votes that it could not be Enacted without one of those votes being changed.
* It has been open for voting for at least 48 hours and half or fewer of its votes are FOR.
* It has been open for voting for at least 48 hours and has fewer than 2 valid votes.
* The '''Captain''' who proposed it has voted AGAINST it.
* The '''Dread Pirate''' has voted to VETO it.

Whenever an '''Admin''' marks a proposal as enacted or failed, he must also mark her name, and report the final tally of votes (or the fact that the proposal was self-killed or vetoed).

== Calls for Judgment ==

If two or more [[#Captain|Captain]] actively disagree as to the interpretation of the [[#Ruleset and Gamestate|Ruleset]], or if a '''Captain''' feels that an aspect of the game needs urgent attention, then any '''Captain''' may raise a '''Call for Judgment''' by posting an entry in the "Call for Judgment" category. If the '''Captain''' wishes, he may post anonymously by choosing "Call for Judgment" from the Author drop-down menu on the OPTIONS tab. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All '''Captains''' may add votes of agreement or disagreement in comments to this entry, using appropriate voting icons (a '''Captain's''' later votes overriding their earlier ones). Unfailed CfJs continue until they reach a [[#Enactment|quorum]] of FOR votes, a quorum of AGAINST votes, or if there is no hiatus going on, until four days have passed, and if there is a hiatus going on until two days have passed. After this time, if more than half of the cast votes are in favour, the Gamestate and Ruleset shall be amended as was specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

== Gamestate Tracking ==

[[#Proposals|Proposals]], [[#Calls for Judgment|Calls for Judgment]], and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any [[#Captains|'''Captain''']] may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered '''official posts'''.

If no '''Captain''' has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. The '''Admin''' processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's '''Status''' must changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than five minutes and has no comments, the author may change the categories as they wish.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any '''Captain''' may update any '''Captain's''' data via the '''GNDT''', whenever the Ruleset permits it.

All updates to the GNDT are logged - if a '''Captain''' feels that an alteration goes against the Rules (as they were at the time of the alteration), he may simply undo the effects of that alteration. If such an undoing is disputed, a [[#Calls for Judgment|Call for Judgment]] shall be raised.

'''Captains''' shall be assigned a password for the GNDT when they join the Nomic.

== Dynasties ==

BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single '''Captain''', known as the '''Dread Pirate''', and is named according to the number of Dynasties he has headed (eg. "The First Dynasty of Myke").

The '''Dread Pirate''' may vote to VETO any Proposal.

==Victory and Ascension==
If a '''Captain''' (other than the '''Dread Pirate''') believes that he has achieved victory in the current Dynasty, he may make a post to the Blognomic weblog in the <b>Declaration of Victory</b> category, detailing this.

Upon doing so, the game immediately goes into Hiatus, if it hasn't already. During this time, the only game actions that may be taken are those covered by Rules "Captains", "Calls for Judgment", "Gamestate Tracking" and "Victory and Ascension".

Every '''Captain''' may respond to an active DoV saying whether or not he believes the poster has achieved victory in the current Dynasty (using the FOR and AGAINST icons).

The Declaration of Victory may be resolved after 24 hours, or after 12 hours if the '''Dread Pirate''' has voted on it. Upon resolution, if a Quorum of '''Captains''' have voted on the DoV and more than half of those votes were in favour, then the DoV passes - otherwise the DoV fails, and if no other DoVs are still pending, the Hiatus ends.

When a DoV passes, all other active DoVs are failed, and a new Dynasty begins with the '''Captain''' who made the DoV as its '''Dread Pirate'''. (That '''Captain''' may pass this role to another '''Captain''' at this point, if he wishes.) The Hiatus continues until the new '''Dread Pirate''' posts an Ascension Address to the BlogNomic weblog - this shall specify the '''Dread Pirate's''' chosen theme for the new Dynasty, and may optionally include a proclamation that any number of Dynastic Rules will be repealed, and that any keywords will be replaced with new theme-appropriate terms.

</div>

= Dynastic Rules =

==Pirate or Ninja==
All Captains have a Role, which is either Pirate or Ninja, to be chosen by em and to be tracked in the GNDT, may not change eir Role once it is chosen. A captain may not take any other action outlined in section two of the ruleset until e has chosen a role.

==Ships==
All Captains have a Ship, which has a name, that may not be the same as any other Ship’s name, and is to be tracked in the GNDT.

If for any reason, a Captain loses er Ship, the value for that attribute shall be set to “-”. That Captain's Location attribute shall be set to Home Land, er Flavor shall set to “Sour” and er Army shall be set to 0. Then, as long as er Ship value remains as “-”, as a weekly action, that Captain may pay 100 gold to purchase a new Ship and record its new name in er Ship attribute. The new Ship’s name may not be the same as any other Ship that Captain had before.

A Captain whose Ship has been sunken may not set er Location to any value other than Home Port, until e buys a new Ship.

A ship has no effect or meaning unless specifically referred to as a ship.

==Gold==
All Captains have a certain amount of Gold, measured in coins, initially set to 100 coins, and is to be tracked in the GNDT.

==Army==
Each Captain has an army of the same type of eir Pet to assist them, the size of which is tracked in a GNDT called “Army Size”.
All captains start with an army size of zero.

At any time, a captain may increase the size of their army by one, by paying 2n + 1 gold where n is the current size of their army.
At any time, a captain may reduce the size of their army by one, by paying 2n - 1 gold as a severance, where n is the current size of their army, provided it does not go below zero.

As a weekly action, a Captain may pay n squared gold where n is eir Army Size at 0:00 of the previous Sunday. Every Sunday at 0:00 AM, each Captain who has failed to complete this action during the previous week and who could have paid at least 1 gold gets er army size reduced by DICEX where X is er current Army Size at that time. If this happens, that Captain’s Flavor is set to “Bitter”.

A Captain may only change the size of eir army, by the mechanics of this rule, if e is currently located at Home Land.

==Sailing==

All Captains have a ‘Rank’ whose value matches one element of the sequence ‘1st’, ‘2nd’, ‘3rd’, ‘4th’, ‘5th’, ‘6th’ and ‘7th’ and it shall be tracked in the GNDT. A Captain must set eir Rank to ‘1st’ if it is not set to a valid value at any time.

Whenever a Proposal is enacted, the Captain who Proposed it and any Captain who Voted FOR on that Proposal may change eir Rank to the next or previous value in the sequence as e prefers, but only within the next 24 hours after the proposal becomes enacted. (The sequence does not loop over itself, so for example, a ‘7th’ rank can only move to ‘6th’ rank, not back to ‘1st’). This action is called “Bragging”.

There exists a section of sub-rules within this rule, called '''“Bragging Rights”'''. Each Rule within that section will apply only to Captains who’s rank is one specified in that rule, and will apply to no one else. No sub-rule may be created in this section that affects more than three ranks at once. Each rule will be noted down in this fashion, replacing words within parenthesis with the appropriate value:

'''(Rule Name) [(Ranks)]:''' (Rule Text)

All such rules will be noted below, within this rule.

Only while being at Sea
can a Captain have er Rank
increase by Bragging

===Bragging Rights===

Plunderin’ [3rd through 6th]: Pirates may, as a weekly action, add three times DICE10 to their Gold.

Lethal Skillz [3rd through 6th]: Ninjas may, as a weekly action, reduce a single Pirates Army Size of their choice by DICE4.

Impressment [1st through 3rd]: Captains who have a flavor of ‘Bitter’ may, as a weekly action while at Home Land, add 1 to their Army Size, if their current Army Size is greater than 1 but less than 5, and if they have at least one Grog or Sake, which is in turn reduced by 1.

Prosperity [7th]: You may reduce your Rank by X places, X can't be greater than 6. Add 10 + (XDICE10) to your Gold.

==Yo-ho-ho==

In the spirit of piracy, all Pirates are encouraged to:

#Use the words ‘Yarr’, ‘Matey’ and their kin as often as possible
#Promote the looting and plundering of non-Pirates
#Demand the keelhauling or walking of the plank of any person for any infraction
#Note that mutiny is a fact of life aboard pirate vessels.
#Drink lots and lots of rum

==Horses==

Milking cows is a weekly action. When a captain Milks the Cows, then that captain will receive DICEX gold, where X is the number of captains. All other captains of the same flavor as that captain will also receive 1 gold. All captains not of the same flavor will reduce their gold by 1.

==Flavor==

All Captains have exactly one Flavor (which is tracked in the GNDT and which may be referred to as a “Flavour” by Captains of the British persuasion). The eligible Flavors are Sweet, Salty, Sour and Bitter. All Captains who are Pirates have an initial Flavor of “Salty”, for obvious reasons. All Captains who are Ninjas have an inital Flavor of “Sweet” because Ninjas are totally sweet (http://www.realultimatepower.net/ninja/ninja2.htm).

==Pet==

Every Captain shall have a Pet, which shall be one of {Penguin, Monkey, Parrot, Cow, Panda}, and only a pirate may have a parrot, and only ninja may have panda. This pet shall be set once only, must be set before any change in eir ”Army Size”, and shall be tracked in the GNDT under ”Pet”.

==The Man from Nantucket==

If a Ninja posts a proposal in the form of one or more haikus (and only haikus, including italicized text), and the proposal passes, the Ninja may increase his Gold by 1DICE20.

If a Pirate posts a proposal in the form of one or more limericks(and only limericks, including italicized text), and the proposal passes, the Pirate may increase his Gold by 1DICE20.

==Spam, egg, spam, spam, bacon and spam==

The wiki pages “About Hammer crushers” http://blognomic.com/wiki/index.php?title=About_Hammer_crushers&rcid=8922 (which may be referred to as the “Hammer Crushers Page") and “About non-metallic mineral resources in China” http://blognomic.com/wiki/index.php?title=About_non-metallic_mineral_resources_in_China&rcid=8953 (which may be referred to as the “Non-Metallic Mineral Resources Page") are gamestate documents and may only be revised as permitted by the Ruleset.

==Home Land==

There exists two islands that all Captains may call home. Shuriken Island is home to Ninja Captains while Cutlass Island is home to Pirate Captains. A Captain may port at his home island or head out to sea or sail to a Treasure Island as a daily action. A Captain may never change their location to anywhere but Sea if their current location is not Sea. The location of every Captain shall be tracked on the GNDT in a section called “Location”. The possible locations are Home Land, Sea, or any treasure island listed in the rule Treasure Islands. While at their Home Land, a Captain can never be pillaged or pillage someone.

New captains start at Home Land.

==Scurvy==

If a Captain’s Fruit reaches 0, he has contracted Scurvy. Eir Sickness value in the GNDT shall be changed to ‘Scurvy’. A Captain with Scurvy may not Brag or take part in an Insult Swordfight. A Captain with Scurvy shall not Feed.

A Captain with at least 5 barrels of Fruit may reduce eir Fruit by 5 at any time to change eir Flavor to Sour. If eir Sickness was Scurvy when e did this, it becomes ‘None’.

==Ninjitsu==

In the spirit of honor, all Ninjas are encouraged to:

* Avoid the words ‘Yarr’, ‘Matey’ and their kin as often as possible
* Discourage the looting and plundering of others
* Discourage the keelhauling or walking of the plank of any person
* Note that sepukku is an honorable path among Ninja’s
* Drink lots and lots of sake

==Insult Swordfighting==

Any captain may challenge another captain to a swordfight, provided both captains aren’t currently in a swordfight already, by making a post to that effect. A captain at sea may only challenge a captain who is also at sea, and a captain in Home Land may only challenge a captain at Home Land at the same island. While participating in an insult swordfight, the participating captains may not change their location.

If the challenged captain accepts within 48 hours by making a comment to that effect to the aforementioned post, the swordfight officially starts. Both captains may then insult one another in their comments to the post, and respond to the other’s insults. If a challenged captain changes their location before accepting a challenge, they have ignored the challenge and their flavor shall be set to “Sour”.

After a suitable amount of time has passed, the dread pirate may end the swordfight and declare a winner. The captain he decrees has displayed more wit is declared the winner of the swordfight, and immediately takes 2DICE10 of the other captain’s gold (or all their gold if they had less). The flavor of the loser (the other captain) is then set to ‘bitter’.

All captains who share the same flavor
hold each other in very good favor
And won’t sword-fight each other
Rather, only another
Captain with a different flavor.

If the Dread Pirate is swordfighting, any admin, other than the Dread Pirate, may declare the winner.

If an admin is fighting the Dread Pirate, that admin may not declare the winner of that battle.

The winner of an insult swordfight shall collect the reward regardless of the location of all captains involved.

The winner of an Insult Swordfight may lower the loser’s Rank by one, as long as er Rank remains a legal value.

===High Seas Rules===
If an insult swordfight is taking place at sea, the following must be adhered to:

* All insults must consist of exactly one sentence and must end with a word rhyming with ‘hated’, ‘died’, ‘vow’, ‘clay’, ‘knee’ or ‘you’.
*All responses must consist of exactly one sentence and must rhyme with the previous insult.
* Each insult (except the first one) must be preceded by a response to the previous insult (captains may not respond to their own insults).

===Tournament===
Every captain has a ‘tournament’ value, tracked by the GNDT, initially set to ‘Not Competing’.

Any entrant may challenge any other entrant to a swordfight, regardless of location and flavour, provided both entrants aren’t in a swordfight already. The title of the post challenging another entrant must include the word ‘tournament’ for it to fall under this rule. This swordfight shall be fought as if both captains were at sea (High Seas Rules apply). If a captain is the loser of such a fight, or if a captain does not accept such a challenge within 48 hours, his ‘tournament’ value shall be set to ‘Eliminated’.

Until March 27th, any captain may become an entrant by changing their ‘tournament’ value from ‘Not Competing’ to ‘Entrant’.

==The Man of the Hour==

There exists an entity called "The Man of the Hour", separate from all Captains and not controlled by any Captain, who has his own row in the GNDT. His ship's name is "The Poisonous Flower" and his flavor is "Sour".

The Man of the Hour
in the G N D T he
shall be set at “sea”

and only be set
at “Home Land” at the same time when
cows are being milked

then in twenty-four
hours since coming in to Home Land
he goes back to sea.

==Lady Luck==

As a weekly action, the Dread Pirate may make a comment in the GNDT “DICE2 DICEX DICE100”, where X is the number of different pets. With the result of the comment, the Dread Pirate will add to all Captains that has role Pirate (if the result of the first DICE is 1) or Ninja (if the result of the first DICE is 2), and has a Pet that is the xth in the list of pets in the rule “Pet”, where x is the result of the second DICE, n Gold where n is the result of the third DICE.

==Treasure==

There exists a finite amount of game objects called “Treasure”, which can only be created by a successful Proposal. No Captain may come in possession of Treasure in any way other than those specified by the rules. There shall be a Gamestate document in the Wiki that will track each existing Treasure and it’s owner (if it has one). For a Treasure to exist, its Name and Gold Value must be defined by the Proposal that created it. No two Treasures may share the same Name. The Gold Value must be a positive integer. A Treasure may or may not also have a property listed as ‘Enchantment’, which consists of a string of text describing a magical effect bestowed upon the owner of the particular Treasure. Enchantments must be specified upon creation of the Treasure entity and cannot be changed otherwise except as in accordance with the game ruleset; a Treasure shall default to having no Enchantment if not specified.

An effect of Enchantment may be invoked by the Captain whom owns the respective Treasure once per day (unless otherwise stated in the Treasure’s Enchantment description) and may modify any of the invoking Captain’s stats or general game condition by a specified magnitute for: a specified amount of time; until some specified event occurs; or as a discrete instantaneous action. When a Captain acquires Treasure, e may keep it for as long as e wishes, or sell it whenever e is at Home Land. When a Captain sells Treasure e is no longer the owner of the Treasure, and that Captain adds it’s Gold Value to er own Gold. That Treasure then becomes owned by the Black Market. A Captain in posession of a Treasure may invoke its magical Enchantment when e so wishes if that Treasure has not been used previously within the specified use-limit period.

Each Treasure is made of exactly one of the numbered Materials listed on the Non-Metallic Metal Resources Page. The name of each Treasure shall include its Material (for example, “Jade Monkey"). In addition, the Treasure’s Material must be specified at the creation of the Treasure and may only be changed as in accordance with the game ruleset.

===Treasure Hunting===

To hunt for treasure, a Captain must have a Treasure Map and their location must be the Location listed on any treasure map they possess. While at a Treasure Island, if allowed by the rules, a Captain may hunt for treasure as a daily action. To do so, the Captain rolls a DICE5 in the GNDT. If the result is a 1 or a 2, they have found the treasure and it shall be noted as described in the rules as owned by them.

==Grog eats metal cups and sake for the sake of it.==

Once while docked in port
sake a ninja may buy
pirates can buy grog

Five shall be the most
That a ships hold can contain
never less than none

The G N D T
Shall track the sake and grog
That each captain holds

Both grog and sake
Shall cost two gold coins apiece,
Buying captain pays

==Treasure Maps==

A Treasure Map may only be created by a successful Proposal, and is tracked in the Gamestate document Wiki page for Treasures, along with the Treasure Map’s owner (if any).

A Treasure Map, in the Proposal that created it, and on the Wiki page, shall list the name of the single Treasure to which it refers, and the alleged Location of that Treasure. Neither the named Treasure nor its alleged Location needs to exist in the Gamestate at the time of the enactment of the Treasure Map’s Proposal. However, no more than one Treasure Map may refer to the same named Treasure.

If the same Treasure Map is claimed by two different Captains for any reason, the last person to claim the Treasure Map may challenge the first one to an Insult Swordfight. The winner of the Insult Swordfight becomes the owner of the Treasure Map. If no challenge to an Insult Swordfight is made, the first to claim the Treasure Map becomes the only owner.

===Visiting the Tavern===

Any Admin may, as a daily action, make a story post rolling DICEX and DICEY (in that order), where X is the number of active Captains located at Home Port and Y is the number of unowned Treasure Maps. E shall also include the name of the Captain whose position in alphabetical order (from the set of Active Captains located at Home Port) matches the number rolled by DICEX, as well as the name of the Treasure Map whose position in alphabetical order (from the set of unowned Treasure Maps) matches the number rolled by DICEY. The named Captain, has 48 hours to respond to that post with a comment claiming the Map and paying 1 GrogOrSake. If e does so within the time limit, the named Treasure Map becomes owned by that Captain. This process is known as “Visiting the Tavern”.

No other Admin may take this action until the Map is claimed or the 48 hour response period expires, whichever occurs first.

===Finders Keepers===

When a proposal that creates a Treasure Map is enacted and the Proposal includes the text “Finders Keepers” (even in flavor text), the Admin who is doing the enactment shall make a DICEX roll in a GNDT comment and include it in er Admin comment. X must be the number of Captains who voted on that Proposal, including the creator. Then assign ownership of the created Treasure Map, to the Captain whose position in the voting order matches the dice roll and include er name in the Admin Comment as well. If the assigned Captain is idle at the time of the enactment, the Treasure Map remains unowned.

==Fruit==

All Captains have a certain amount of Fruit, measured in barrels, initially set to 50 barrels, and is to be tracked in the GNDT. Once every Monday, each Captain must lower their Fruit by n+1, ‘n’ being their Army Size. This action is known as Feeding. If a Captains Fruit reaches 0 Barrels, he shall not Feed until he acquires Fruit again.

A Captain may at any time purchase Fruit from a branch of Fingal’s Fruiterers. Fruit is priced at 10 Gold for a barrel of Fruit. A Captain may only purchase Fruit while e is at Port.

==Battles==

As a daily action, a Captain who is at Sea may Attack another Captain who is at Sea, by making a blog post stating the action. The attack is resolved by making a comment in the GNDT of “DICEX DICEY”, where X is one more than the size of the Attacking Captain’s Army, and Y one more than the size of the Attacked Captain’s Army. If a Captain’s Sickness is set to Scurvy, eir Army size shall be counted as two-thirds of its actual size recorded in the GNDT, rounded down. Should the first DICE roll be strictly greater than the second, then the Attack is successful, and the Attacking Captain may plunder 2DICE10 gold from the other Captain, whose Flavour is set to Bitter. If the first roll is more at least double the second roll and the defending Captain owns a treasure, then the attacking captain may take one treasure at random. To choose a treasure, the attacking Captain shall roll DICET where T is the number of treasures the the defending captain holds and alphabetically count to T and take that treasure. (Example: If the defender has treasures A B and C and the roll is 3, e shall take treasure C) Otherwise the Attacked Captain has fended off the attack, and the Attacking Captain loses half of the first DICE roll, rounded up, from the size of eir Army, and eir Flavour is set to Bitter. No single Captain may Attack the same Captain more than once in a week.

==Treasure Islands==

If the a treasure map proposal mentions a location that does not exist on the list of islands below in this rule, is shall be listed when the treasure map proposal is passed. An island listed this way will have no special attributes or effects unless the proposal causes it. Listed below are possible Treasure Islands that a Captain or treasure may be located:

===The Isle of Untimely Demise===
* If a Captain (called The Tardy Captain) spends more than three days located at this island, daily any Captain may roll DICEX where X is half the size (rounded up) of the Tardy Captain’s army and a DICE3. The result of the DICEX roll will be removed from the Tardy Captain’s army value after a number of days equal to the DICE3 roll have passed, if possible.

===Icecube Isle===

===Forsaken Clay Mound Isle===

===Deep Burial Reef===

===Squeaky Sands Island===

===Icecube Isle===

===Forsaken Clay Mound Isle===

===Deep Burial Reef===

===Squeaky Sands Island===

===Isle of Infinite Fright===

===Forbidden Orchard Isle===

==Sickness==

The GNDT contains a column called ‘Sickness’. The eligible values are ‘Cabin Fever’, ‘Scurvy’. and ‘None’. If ever a captain has an undefined value for Sickness, eir Sickness value shall be changed to ‘None’.

==Cabin Fever==

If a captain’s Location is set to Sea for more than a week straight, that Captain has contracted Cabin Fever and eir Sickness value in the GNDT shall be changed accordingly. A captain with Cabin Fever may not change eir Location by the rule “Home Land”. As a daily action a captain with Cabin Fever may roll 1DICE50 to try to escape the doldrums. A result of 0 to 24 means the captain is still stuck in the doldrums. A result of 25 to 44 means the captain can make it back to eir homeland (eir location shall be changed to either Port or Home Land, as determined by the text of the rule “Home Land"). A result of 45 to 50 means that the captain has shown great skill in eir escape and may change eir location to any legal value.

If the Location of a captain with Cabin Fever is ever not “Sea” eir Sickness shall be set to “None”.

==Black Market==

There exists a non-playing game entity known as “Black Market”. The only ability of the Black Market is to own sold Treasures.

Any Captain whose Location is Home Land may purchase a Treasure owned by the Black Market by making a Story Post announcing the Purchase and paying an amount of Gold equal to the Treasure’s Gold Value plus an additional 20% of that amount, rounded up.

==Sea Monsters==

There exists a finite number of game objects known as ‘Sea Monsters’. Sea Monsters may be summoned by Captains to perform certain actions. For a Sea Monster to exist it shall be created through a successful proposal. There shall be a Gamestate document in the Wiki entitled ‘Sea Monsters’ that will track each existing Sea Monster, its Affiliation, Summoning Cost and Effect.

For a Sea Monster to exist, its Name, Affiliation, Summoning Cost and Effect shall be defined by the proposal that created it.

No two Sea Monsters may share the same Name. A Sea Monster’s Affiliation may be either Pirates or Ninjas. Only Pirates may summon Sea Monsters affiliated with Pirates. Only Ninjas may summon Sea Monsters affiliated with Ninjas.

A Sea Monster’s Summoning Cost details how much Gold and Fruit a Captain shall pay to Summon the Sea Monster. A Sea Monster’s Summoning Cost shall consist of positive integers only. A Sea Monster’s Summoning Cost may consist of only a Fruit value, of only a Gold value or of two values, Fruit and Gold.

A Sea Monster’s Effect details what effect the Sea Monster will have on the summoning Captain’s target. Effects shall be specified upon creation of the Sea Monster and cannot be changed otherwise except as in accordance with the Game Ruleset. If a Sea Monster’s Effect is not specified, it’s Effect shall be ‘None’, and it shall have no effect.

As a weekly action, a Captain may summon a Sea Monster Affiliated to eir Role by making a post to that effect. In this post, the Captain shall state the Captain e wishes to target and the Name of the Sea Monster e is summoning. The Effect of the Sea Monster may then be carried out. Only Captains with eir location set to ‘Sea’ may summon a Sea Monster. Only Captains with eir location set to ‘Sea’ may be targeted.

= Glossary =
<div style="padding:8px;background:#ddd;">
This is always at the end of the Ruleset. Its only effect can be to clarify ambiguity.

* It is noted that where a [[#Proposals|Proposal]] would '''amend''' the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their writer a banana when enacted would not earn a banana for its own writer, when enacted).
* Rules which '''trigger''' upon the Enactment or Failure of a Proposal are the responsibility of the '''Admin''' who Enacts or Fails it.

* Appropriate '''Icons''': For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a vote of DEFERENTIAL, and an Imperial Seal (currently http://blognomic.com/images/vote/seal.gif) shall represent the Imperial Veto.
*The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.
* '''"Posts"''' and '''"comments"''' refer only to those made to the BlogNomic weblog at [http://blognomic.com blognomic.com]
* A '''keyword''' defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "Bananas are Blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)
* Unless otherwise specified, game '''variables''' defined to hold numeric values can hold only non-negative integers, and any action that would set those values below '''zero''' instead sets them to zero. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* Unless otherwise specified: When "X" is a number, to '''spend''' X of a numeric value "V" means to subtract X from V (i.e. replace V with V-X); no action may be taken which requires spending X of a numeric value when the subtraction would result in a number which is illegal as a replacement for that value (e.g. if the value represents a variable which is restricted to non-negative integers, but the subtraction comes up negative).
* Superficial differences between the '''spelling''' of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.
* '''Gamestate''' is defined as any information which the Ruleset regulates the alteration of, such as '''Captains'''' names and the blog colour scheme.

== Typographic Conventions ==

* '''Italicized text''' is not considered part of the ruleset and may be used to clarify rules with examples, notes, and flavor text. ''For example, this italicized text provides an example of the use of italicized text.''

== Timespans ==

* References to '''"a day"''' (as an entity rather than a duration, eg. "Sunday") refer to that day in the timezone of the BlogNomic blog, which is considered to be GMT for all purposes.
* References to a '''"week"''' refer to the period of time between the start of a Monday and the end of the following Sunday.
* All '''references to time''' must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* If a game action is a '''Daily Action''', each Captain able to perform it may take that action once per day, but not more than once every six hours.
* If a game action is a '''Weekly Action''', each Captain able to perform it may take that action once per week, but not more than once every twenty-four hours.

== Keywords ==

* '''Quorum''' is equal to half the number of '''Captains''', rounded down, plus one.

== Dice ==

References to '''"YDICEX"''' refer to Y X-sided dice. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

== IEEE ==
* The IEEE auxiliary verbs used in Blognomic are:
** Is required to: '''"shall"''';
** Is recommended that: '''"should"''';
** Is permitted to: '''"may"''';
** Is able to: '''"can"'''.
</div>

Treasures Page

2008-04-07T11:34:43Z

Purplebeard: /* The Diamond Steering Wheel of Destiny */

This is where Pirates and Ninjas track the Treasures they possess
<br clear=all>
http://blognomic.com/images/member/photo_253.jpg

=Treasures=

===The Ice Spar Bucket of Nantucket===
The Ice Spar Bucket of Nantucket. It is worth 61 gold.

===The Calcite Milking Gloves===
The Calcite Milking Gloves. They are worth 100 gold.

===Mica Mirror===
When a Captain acquires the Mica Mirror by whatever means, he must change his Flavor within 24 hours to a different Flavor. If he fails to do so, any Admin may change that Captain’s Flavor to a random Flavor. Gold Value: 15

===The Big Whoop - Abestos Edition===

Value: 100 times its current owner's rank.

Make a story post that contains a DICE7 Roll. Then, apply the effect corresponding to the result from this list.

1) Set your Ship Value to ‘-’ (You have sunk your own ship)
2) Set your Flavor to Sour and your Sickness to ‘Asbestos Poisoning’
3) Change your Rank to any legal value.
4) Set your GrogOrSake to 10, this supersedes rule 2.19
5) Add DICE150 to your Fruit.
6) Add up to 20 to your army size, then add up to 400 to your Gold.
7) Re-roll DICE7, then pick another effect from this list. If this is the third time you have Re-Rolled today, you win the game.

Whenever this Treasure’s Enchantment is used, “The Big Whoop - Asbestos Edition” and every map that references it becomes unowned.

===RECTORITE Clay Idol===

Gold Value: 80

Twice a week you may increase you army size by 1 for a period of 24 hours. This Enchantment cannot be activated again until that period ends.

===Kaolin Shovel===

Value: 150

Once a week, at a time you’re hunting for treasure, you may obtain the treasure without Rolling any dice for digging, as long as you fulfill any other existing requirements for that treasure.

===Pumice Orange Basket===

Value: 180

You may, as a weekly action take 10 Fruit from another Captain of your choice, and add it to your Fruit.

===Other Clay Champion Belt===

Value: 75

This belt may not be sold.

As a daily action, you may make any other non-entrant captain an entrant by changing their tournament value to ‘entrant’. You then gain DICE10 gold.

If you lose a tournament swordfight, or fail to accept a challenge to one within 48 hours (unless you were unable to accept it), the entrant who defeated you (or challenged you) will gain ownership of this treasure.

'''Owner: Purplebeard'''

===BORON PROSPECTING Dummy===

Value: 130

Once a week, when a Captain targets you with the effect of a Sea Monster, you may respond within 24 hours to er Sea Monster attack post with a comment that reads “I’m sorry, sir. You miss.” and pay 1 Army. If you do, ignore all effects of that Sea Monster during this attack. If the effects where already applied, undo them.

===Mystical Diatomite Seed===

Once a Week you may roll DICE10 and add the resulting amount to your Fruit. If a Captain rolls exactly 10, er Flavor becomes Sweet. This enchantment can only be activated while it’s owner is located on Forbidden Orchard Isle.

===The Diamond Steering Wheel of Destiny===

As a daily action, you may achieve victory.

'''Owner: Purplebeard'''

=Maps=

===The Ice Spar Bucket of Nantucket===

This map shall guide ye to me treasure, the Ice Spar Bucket of Nantucket, on Icecube Isle.

Due to the frozen ground, the Ice Spar Bucket of Nantucket is harder to dig up then most treasures. For a pirate to claim this treasure, e must roll a 1 or 2 twice during the same attempt at hunting for treasure, once to break the icy ground and a second to dig the treasure up before the ground freezes again.

===RECTORITE Clay Idol===

The “RECTORITE Clay Idol” lies in no place other than the Forsaken Clay Mound Isle, where a Captain must go and dig for it. An army size of at least three is required to claim the treasure successfully, because it is so heavy and slippery.

===Kaolin Shovel===

The Kaoilin Shovel is located at “Deep Burial Reef”. Because of the huge dangers in navigating the reef, It can only be claimed by a Captain of Rank 3rd or Greater.

'''Owner: Purplebeard'''

===Pumice Orange Basket===

The Pumice Orange Basket is hidden on “Squeaky Sands Island”. There is Quicksand around the edge of this Island, and the Squeaking Sands may frighten less experienced Captains, therefore, only Captains of Rank 4th or higher, with a Fruit value of less than 50 may claim this Treasure.

===BORON PROSPECTING Dummy===

The Treasure referenced by this map can be found on the Isle of Infinite Fright. If you attempt to dig this treasure and fail (that is, your dig roll is not 1 or 2) your Army is reduced to 0, your location is set to ‘Home Port’ and your flavor is set to ‘Sour’.

'''Owner: arthexis'''

===Mystical Diatomite Seed===

To unearth the Mystical Diatomite Seed, a Captain must dig for it at Forbidden Orchard Isle on a Tuesday.

'''Owner: aaronwinborn'''

===The Diamond Steering Wheel of Destiny===

The Diamond Steering Wheel of Destiny is located at “Doom Island”. Only captains with at least 200 gold, an army of 20, 3 treasures and 50 fruit may hunt for this treasure. This treasure map may not be distributed through visiting the tavern.

Sea Monsters

2008-04-02T15:15:14Z

Purplebeard:

==Kargo Krushing Kraken==

Affiliation: Pirates

Summoning cost: 5 barrels of fruit, 10 gold

Effect: Reduce target’s Gold by 10. Reduce target’s Fruit by 10. Set target’s rank to 1st.

==Shuriken Island Sea-Moth==

Affiliation: Ninja

Summoning cost: 5 barrels of fruit, 10 gold

Effect: Reduce target’s Gold by 10. Reduce target’s Fruit by 10. Set target’s flavour to Sour.

Ruleset Draft, Take Two

2008-03-16T19:28:40Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Core Rules =

== Ruleset and Gamestate ==

''This is the '''Ruleset''' for '''BlogNomic'''; all Captains must obey the most recent version of this document.''

Section One consists of the '''"core rules"''' of blognomic, covering basic Captain and proposal mechanics; Section Two contains the '''"dynastic rules"''' of the current round, and Section Three contains the '''glossary''', which exists solely to clarify the remainder of the ruleset.

The '''Ruleset''' and '''Gamestate''' can only be altered in manners specified by the Ruleset.

If two parts of the '''Ruleset''' contradict each other, precedence shall be construed in the following order:

# The '''Glossary''' has precedence over any '''Dynastic Rule''' or '''Core Rule''';
# A '''Dynastic Rule''' has precedence over a '''Core Rule''', unless that '''Core Rule''' explicitly says it can't be overruled by a '''Dynastic Rule''';
# If both contradicting parts are a '''Core Rule''', or if both of them are a '''Dynastic Rule''', the part with more limited scope applies. ''(e.g. if the rules "Players can Fight each other" and "Players cannot Fight each other on Tuesdays" exist, and it is Tuesday, players cannot fight each other.)''
# If two parts with the same scope contradict each other, the negative rule applies. ''(e.g. with "Players can Fight each other on Tuesdays" and "Players cannot fight each other on Tuesdays", Players cannot fight each other on Tuesdays.)''

'''Admins''' may correct obvious spelling and typographical mistakes in the Ruleset at any time.

No '''Rule''' may contain a provision that bars itself from being altered and/or repealed. If at any moment a '''Rule''' exists or is altered in a manner that renders it to contain such a provision, the entirety of that '''Rule''' shall be considered void and with no effects on the '''Gamestate'''. ''A rule A is considered to fall under this paragraph's provisions if it protects another rule B from being altered and/or repealed and that rule B prevents rule A from being altered. Daisy-chains of protection also fall under this paragraph's provisions.'' The provisions on this paragraph supersede any text in a '''Dynastic Rule'''.

== Captains ==

Anybody may apply to join BlogNomic (if he is not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing her arrival. An '''Admin''' will add her to the roster in the sidebar, at which moment he becomes a '''Captain'''.

A '''Captain''' may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A '''Captain''' may only change her name as a result of a proposal approving the change.

Some '''Captains''' are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. '''Captains''' who wish to become '''Admins''' shall sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves '''Admins'''. Existing '''Admins''' may be removed from their posts by Proposal, CfJ, or voluntary resignation.

Some '''Captains''' are '''Idle''', and shall be marked as such in the sidebar. Idle '''Captains''' are not counted as '''Captains''', except when they are directly referred to as "Idle Captains". '''Admins''' may render a '''Captain Idle''' if that '''Captain''' has asked to become '''Idle''' or if that '''Captain''' has not posted a entry or comment for more than 7 days. '''Admins''' may unidle a '''Captain''' at her request - the '''Captain's''' personal gamestate retains the values it had immediately prior to her going Idle. If one or more values would be undefined, it is set to the value new '''Captains''' receive, if such a value exists.

If the last '''Admin''' would go Idle or resign, they must immediately make one other '''Captain''' an '''Admin'''.

A single person may not control more than one '''Captain''' within BlogNomic. If anybody is suspected of controlling more than one '''Captain''', then a '''Call for Judgment''' may be made to remove any number of such '''Captains''' from the game, and to bar the perpetrator from rejoining.

== Proposals ==

Any '''Captain''' may propose changes to the '''Ruleset''' or '''Gamestate''' by making a '''Proposal'''. To make a '''Proposal''', a '''Captain''' must {{Make a Post}}, in the "Proposal" category, that describes the changes he wishes to be made. A Proposal is a '''Voting Post'''.

Only the oldest Pending '''Proposal''' may be '''Enacted''' or '''Failed'''. This does not stop '''Voting Posts''' of other types from being '''Enacted''' or '''Failed'''.

When a '''Proposal''' is '''Enacted''', the effects it describes are made by the Enacting '''admin'''.

A '''Captain''' may not make a '''Proposal''' if he already has 2 '''Proposals''' pending. Furthermore, no '''Captain''' may post more than 3 '''Proposals''' in the same day.

== Voting ==

Some Offical posts, known as '''Voting Posts''', may be voted upon. These posts have 3 states: '''Pending''', '''Passed''' or '''Failed'''. When a '''Voting Post''' is first put forward, it is considered '''Pending'''.

Any Captain may cast his '''Vote''' on a Pending Voting Post by declaring it in the comments of the entry. Valid votes are '''FOR''', '''AGAINST''', and '''DEFERENTIAL''', which must be represented by appropriate icons. If there exists more than one Vote from a single Captain on a single Post, only the most recent of those Votes is counted. If a Captain leaves the game or goes idle, his Vote no longer counts.

A vote of DEFERENTIAL is a vote of faith in the decision of the [[#Dynasties|Dread Pirate]]. The vote will count as the same as the Dread Pirate's vote. If the Dread Pirate votes DEFERENTIAL, or there is no Dread Pirate, any DEFERENTIAL votes are not counted.

If the Captain who made a Voting Post has not cast an explicit Vote on it, his Vote is counted as FOR.

== Enactment ==

A Voting Post may be enacted by any '''Admin''' if either of the following is true:-

* It has a number of FOR votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed or self-killed.
* It has been open for voting for at least 48 hours, it has more than 1 valid vote, more than half of its votes are FOR, and it has not been vetoed or self-killed.

The oldest pending Voting Post may be failed by any '''Admin''', if any of the following are true:-

* It has enough AGAINST votes that it could not be Enacted without one of those votes being changed.
* It has been open for voting for at least 48 hours and half or fewer of its votes are FOR.
* It has been open for voting for at least 48 hours and has fewer than 2 valid votes.
* The '''Captain''' who posted it it has voted AGAINST it.
* The '''Dread Pirate''' has voted to VETO it.

Whenever an Admin marks a Voting Post as passed or failed e must report the following information on the Voting Post:
# the final tally of for to against votes, or whether the proposal was self-killed or vetoed
# the time of enactment or failure
# the identity of the enacting or failing admin

== Calls for Judgment ==

If two or more [[#Captain|Captain]] actively disagree as to the interpretation of the [[#Ruleset and Gamestate|Ruleset]], or if a '''Captain''' feels that an aspect of the game needs urgent attention, then any '''Captain''' may raise a '''Call for Judgment''' by posting an entry in the "Call for Judgment" category. If the '''Captain''' wishes, he may post anonymously by choosing "Call for Judgment" from the Author drop-down menu on the OPTIONS tab. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All '''Captains''' may add votes of agreement or disagreement in comments to this entry, using appropriate voting icons (a '''Captain's''' later votes overriding their earlier ones). Unfailed CfJs continue until they reach a [[#Enactment|quorum]] of FOR votes, a quorum of AGAINST votes, or if there is no hiatus going on, until four days have passed, and if there is a hiatus going on until two days have passed. After this time, if more than half of the cast votes are in favour, the Gamestate and Ruleset shall be amended as was specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

== Gamestate Tracking ==

[[#Proposals|Proposals]], [[#Calls for Judgment|Calls for Judgment]], and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any [[#Captains|'''Captain''']] may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered '''official posts'''.

If no '''Captain''' has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. The '''Admin''' processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's '''Status''' must changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than five minutes and has no comments, the author may change the categories as they wish.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any '''Captain''' may update any '''Captain's''' data via the '''GNDT''', whenever the Ruleset permits it.

All updates to the GNDT are logged - if a '''Captain''' feels that an alteration goes against the Rules (as they were at the time of the alteration), he may simply undo the effects of that alteration. If such an undoing is disputed, a [[#Calls for Judgment|Call for Judgment]] shall be raised.

'''Captains''' shall be assigned a password for the GNDT when they join the Nomic.

== Dynasties ==

BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single '''Captain''', known as the '''Dread Pirate''', and is named according to the number of Dynasties he has headed (eg. "The First Dynasty of Myke").

The '''Dread Pirate''' may vote to VETO any Proposal.

If at any time there is no Dread Pirate, any Captain may propose that BlogNomic enter into a '''Metadynasty''' via a Proposal or a Call for Judgment.

Metadynasties are named according to the number of Metadynasties that have occured ''(eg. "Third Metadynasty")'' unless the name is changed.

==Victory and Ascension==
If a [[#Captains|Captain]] believes e has achieved '''victory''' as specified in the current [[#Ruleset and Gamestate|Ruleset]] and no active DoV has been posted by em, e may {{Make a Post}} to the Blognomic frontpage in the '''Declaration of Victory''' category. As soon as it is posted, a Declaration of Victory (hereafter referred as a DoV) becomes Active and remains so until it passes or fails. No Captain may have more than one active DoV pending at any time.

Whenever a DoV becomes active and there is not a '''Hiatus''' in effect, a Hiatus begins. So long as a Hiatus is in effect, the only game actions that may be taken are those covered by Core Rules "Captains", "Calls for Judgment", "Gamestate Tracking" and "Victory and Ascension".

Every Captain may vote on an active DoV, saying whether e believes the poster has achieved victory or not (using the FOR and AGAINST vote icons). If a single Captain votes more than once on the same active DoV, only the most recent of those Votes is counted.

The Declaration of Victory may be resolved after 24 hours, or after 12 hours if the '''Dread Pirate''' has voted on it. Upon resolution, if a Quorum of '''Captains''' have voted on the DoV and more than half of those votes were in favour, then the DoV passes - otherwise the DoV fails, and if no other DoVs are still pending, the Hiatus ends. DoV's may not be resolved if a Call for Judgment is pending.

At the winner's discretion, e may choose another active Captain to be the current Dread Pirate for the next dynasty. This is known as '''Passing the Mantle'''. If the selected Captain agrees, then all rights and responsibilities of the Dread Pirate transfer to the selected Captain. If the winner makes no mention of Passing the Mantle, it is assumed that the winner has decided to become the next Dread Pirate.

The Hiatus then continues until the new Dread Pirate posts an '''Ascension Address''' to the BlogNomic weblog - this shall specify the new Dread Pirate's chosen theme for the new round, and may optionally include a proclamation that any number of Rules will be repealed, and/or that the words "Captain" and "Dread Pirate" will be replaced with new theme-appropriate terms. The new Dread Pirate may also proclaim at the Ascension Address the veto of any Pending Proposals.

Upon posting this Address, and having made the Ruleset changes, the Hiatus period ends and the new Dynasty commences. Unless decreed otherwise by the Dread Pirate in the Axcension Address, all Captains' GNDT (http://blognomic.com/gndt/generic.cgi?nomic=blog) stats are then reset to zero or blank, and all NPC entities are removed.

The current Dread Pirate may not declare victory in eir own dynasty.

</div>

= Dynastic Rules =

= Glossary =
<div style="padding:8px;background:#ddd;">
This is always at the end of the Ruleset. Its only effect can be to clarify ambiguity.

* It is noted that where a [[#Proposals|Proposal]] would '''amend''' the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their writer a banana when enacted would not earn a banana for its own writer, when enacted).
* Rules which '''trigger''' upon the Enacment or Failure of a Proposal are the responsibility of the '''Admin''' who Enacts or Fails it.

* Appropriate '''Icons''': For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a vote AGAINST, an I http://blognomic.com/images/vote/imperial.gif shall represent a vote of DEFERENTIAL, and an Imperial Seal (currently http://blognomic.com/images/vote/seal.gif) shall represent the Imperial Veto.
* The '''"subject"''' of a blog entry is the Title of the entry. Any entry that does not have exactly one subject is not valid.
* '''"Posts"''' and '''"comments"''' refer only to those made to the BlogNomic weblog at [http://blognomic.com blognomic.com]
* A '''keyword''' defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "Bananas are Blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)
* Unless otherwise specified, game '''variables''' defined to hold numeric values can hold only non-negative integers, and any action that would set those values below '''zero''' instead sets them to zero. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* Unless otherwise specified: When "X" is a number, to '''spend''' X of a numeric value "V" means to subtract X from V (i.e. replace V with V-X); no action may be taken which requires spending X of a numeric value when the subtraction would result in a number which is illegal as a replacement for that value (e.g. if the value represents a variable which is restricted to non-negative integers, but the subtraction comes up negative).
* Superficial differences between the '''spelling''' of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.
* '''Gamestate''' is defined as any information which the Ruleset regulates the alteration of, such as '''Captains'''' names and the blog colour scheme.

== Typographic Conventions ==

* '''Italicized text''' is not considered part of the ruleset and may be used to clarify rules with examples, notes, and flavor text. ''For example, this italicized text provides an example of the use of italicized text.''

== Timespans ==

* References to '''"a day"''' (as an entity rather than a duration, eg. "Sunday") refer to that day in the timezone of the BlogNomic blog, which is considered to be GMT for all purposes.
* References to a '''"week"''' refer to the period of time between the start of a Monday and the end of the following Sunday.
* All '''references to time''' must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* If a game action is a '''Daily Action''', each Captain able to perform it may take that action once per day, but not more than once every six hours.
* If a game action is a '''Weekly Action''', each Captain able to perform it may take that action once per week, but not more than once every twenty-four hours.

== Keywords ==

* Unless otherwise specified, '''Quorum''' is equal to half the number of '''Captains''', rounded down, plus one.

== Dice ==

References to '''"YDICEX"''' refer to Y X-sided dice. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.

== IEEE ==
* The IEEE auxiliary verbs used in Blognomic are:
** Is required to: '''"shall"''';
** Is recommended that: '''"should"''';
** Is permitted to: '''"may"''';
** Is able to: '''"can"'''.
</div>

About non-metallic mineral resources in China

2008-03-13T21:44:09Z

Purplebeard: Enacting "And you thought it was just a silly non-sequitur...". Yeah, I cheated a little.

China many non-metallic mineral species, abundant resources, and widely distributed. Proven reserves are 88 kinds of non-metallic mineral:

===diamond===
===graphite===
===natural sulfur===
===pyrite===
===crystal===
===corundum===
===kyanite===
===Xi Shi line===
===andalusite===
===wollastonite===
===sodium saltpeter===
===talc===
===asbestos===
===Blue asbestos===
===mica===
===feldspar===
===garnet stones===
===pyrophyllite===
===diopside===
===tremolite===
===vermiculite===
===zeolite===
===alunite===
===Glauber's salt===
===gypsum===
===barite===
===witherite===
===Trona===
===calcite===
===ice spar===
===magnesite===
===fluorite===
===precious stones===
===jade===
===agate===
===pigment minerals===
===limestone===
===marl===
===chalk===
===dolomite===
===quartzite===
===sandstone and natural quartz sand===
===quartz veins===
===quartz powder===
===natural Whetstone===
===potassium content sandstone and shale===
===diatomite===
===shale===
===kaolin===
===ceramics soil===
===refractory clay===
===palygorskite clay===
===sepiolite clay===
===illite clay===
===RECTORITE clay===
===bentonite===
===iron bauxite===
===other clay===
===peridotite===
===serpentinite===
===basalt===
===amphibolite===
===gabbro===
===diabase===
===andesite===
===diorite and granite===
===perlite===
===pumice===
===nepheline syenite===
===rough rocks===
===tuff===
===ash===
===scoria===
===marble===
===slate===
===gneiss===
===peat===
===salt===
===potassium===
===magnesium===
===iodine===
===bromine===
===arsenic===
===BORON PROSPECTING===
===phosphate rock===
===Magnesite===

Motion to Fix Spelling of Clarification

2007-02-28T21:01:49Z

Purplebeard: Unnecessary

Ruleset Reconstruction

2006-09-23T15:28:17Z

Purplebeard:

{{TOCRight}}

<div style="padding:8px;background:#ddd;">
= Laws =

== Ruleset and Gamestate ==
This is '''not''' the '''Ruleset''' for '''BlogNomic'''; Swashbucklers may ignore it. Section One consists of the "laws" of blognomic, covering basic Swashbuckler and proposal mechanics; Section Two contains the "rules" of the current round, and Section Three contains the glossary, which exists solely to clarify the remainder of the ruleset. Laws and rules may be referred to by eir type and entire number or type and name. (e.g. This Law may be referred to as Law 1.1 or the Law entitled "Ruleset and Gamestate"). No Rule may contain a provision that bars itself from being altered and/or repealed. If at any moment a Rule exists or is altered in a manner that renders it to contain such a provision, the entirety of that Rule shall be considered void and with no effects on the Gamestate. The provisions on this paragraph supersede any text in a Rule.

The Ruleset and '''Gamestate''' can only be changed when the Ruleset specifically permits eir being changed.

Spivak pronouns, as defined in the [[#Glossary|Glossary]], shall be used whenever a Swashbuckler is referred to.

Admin Staff may correct obvious spelling and typographical mistakes in the Ruleset at any time.

== Swashbucklers ==

Anybody may apply to join BlogNomic (if e is not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing eir arrival. An Admin will add em to the roster in the sidebar, at which moment e becomes a '''Swashbuckler'''.

A Swashbuckler may change eir name or eir sidebar link by editing eir blognomic.com profile. A Swashbucklerâ€™s name may only ever act as a signifier identifying a certain player. A name change may never create a meaning in the Ruleset that was not present before it. E may leave the game by posting an entry to the BlogNomic weblog requesting such action.

Some Swashbucklers are '''Admin Staff''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Swashbucklers who wish to become Admins shall sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from eir post by Proposal, CfJ or voluntary resignation.

Some Swashbucklers are '''Idle''', and shall be marked as such in the sidebar. For the purposes of the ruleset, excluding Laws 1.1 and 1.2, idle Swashbucklers are not counted as Swashbucklers. Admin may render a Swashbuckler idle if that Swashbuckler has failed to vote for more than a week, or if it has asked to become idle. Admins may un-idle a Swashbuckler at eir request - the Swashbuckler's personal gamestate retains the values it had immediately prior to eir idling.

A single person may not control more than one Swashbuckler within BlogNomic. If anybody is suspected of controlling more than one Swashbuckler, then a Proposal may be made to remove any number of such Swashbucklers from the game, and to bar the perpetrator from rejoining.

== Proposals ==

Any Swashbuckler may propose a change to the Ruleset or gamestate by [http://blognomic.com/update/index.php?C=publish posting an entry] in the '''"Proposal"''' category that describes the changes e wishes to be made.

Proposals can either be '''Pending''', '''Enacted''', or '''Failed'''. When a Proposal is first put forward, it is considered Pending.

No ostensible Proposal shall be legal if its posting leads to its poster having more than 2 Proposals pending. Furthermore, no Swashbuckler may post more than 3 Proposals in the same day. Rules may take precedence over this paragraph.

== Voting ==

Any Swashbuckler may cast eir '''Vote''' on a Pending [[#Proposals|Proposal]] by declaring it in the comments of the entry. Valid votes are '''FOR''', '''AGAINST''', and '''DEFERENTIAL''', which must be represented by appropriate icons. If there exists more than one Vote from a single Swashbuckler on a single Proposal, only the most recent of those Votes is counted. Rules may take precedence over the previous sentence. If a Swashbuckler leaves the game or goes idle, eir Vote no longer counts.

A vote of DEFERENTIAL is a vote of no opinion, or of faith in the decision of the [[#Dynasties|Captain]]. The vote will count as the same as the Captain's vote. The Captain cannot cast a vote of DEFERENTIAL. If there is no Captain, a vote of DEFERENTIAL counts as an explicit vote of abstention.

If the Swashbuckler who made a Proposal has not cast an explicit Vote on it, eir Vote is counted as FOR.

== Enactment ==

'''Quorum''' is equal to half the number of Swashbucklers, rounded down, plus one.

If the oldest pending [[#Proposals|Proposal's]] FOR votes exceed or equal Quorum and that Proposal has been open for voting for at least 12 hours, or if it is more than 48 hours old and more than half of its votes are FOR, then any Admin Staff may mark that Proposal as Enacted, then update the Ruleset and/or Gamestate to include the specified effects of that Proposal.

If the oldest pending Proposal has enough AGAINST votes that it could not be Enacted without one of those votes being changed, or if all Swashbucklers have voted on it and it still cannot be Enacted, or if the Swashbuckler who proposed it has voted AGAINST it, or if it is more than 48 hours old and half or fewer of its votes are FOR, then any Admin Staff may mark that Proposal as Failed. When the proposer votes against eir own proposal, that vote may not be changed.

Whenever an Admin marks a proposal as enacted or failed e must report the following information on the proposal:<br>
1) the final tally of for to against votes, or whether the proposal was self-killed or vetoed<br>
2) the time of enactment or failure<br>
3) the identity of the enacting or failing admin

Rules may take precedence over any part of this law.

== Calls for Judgment ==

If two or more [[#Swashbucklers|Swashbucklers]] actively disagree as to the interpretation of the [[#Ruleset and Gamestate|Ruleset]], or if a Swashbuckler feels that an aspect of the game needs urgent attention, then any Swashbuckler may raise a '''Call for Judgment''' by posting an entry in the "Call for Judgment" category . If the Swashbuckler wishes, e may post anonymously by choosing "Call for Judgment" from the Author drop-down menu on the OPTIONS tab. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All Swashbucklers may add votes of agreement or disagreement in comments to this entry, using appropriate voting icons (a Swashbuckler's later votes overriding eir earlier ones). CfJs continue until they reach a [[#Enactment|quorum]] of FOR votes, a quorum of AGAINST votes, or if there is no hiatus going on, until four days have passed, and if there is a hiatus going on until two days have passed. After this time, if more than half of the cast votes are in favour, the Gamestate and Ruleset shall be amended as was specified. Otherwise, the CfJ fails and may have no further effect.

== Gamestate Tracking ==

[[#Proposals|Proposals]], [[#Calls for Judgment|Calls for Judgment]], and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any [[#Swashbucklers|Swashbuckler]] may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered '''official posts'''.

If no other Swashbuckler has commented on it, an official post may be altered or removed; otherwise this can only be done as allowed by the Ruleset. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's '''Status''' must changed to reflect its status.

A non-official post may not through editing of the blog be changed into an official post.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Swashbuckler may update any Swashbuckler's data via the '''GNDT''', whenever the Ruleset permits it.

All updates to the GNDT are logged - if a Swashbuckler feels that an alteration goes against the Rules (as they were at the time of the alteration), e may simply undo the effects of that alteration. If such an undoing is disputed, a [[#Calls for Judgment|Call for Judgment]] shall be raised.

Swashbucklers shall be assigned a password for the GNDT when they join the Nomic.

== Dynasties ==

BlogNomic is divided into a number of Rounds, referred to as '''Dynasties'''.

Each Dynasty has a single '''Captain''' and is named according to the number of times which that [[#Swashbucklers|Swashbuckler]] has been the Captain (or Captain equivalent) (eg. "The First Dynasty of Myke").

The Captain has the following powers:

* E may '''veto''' any Proposal; that Proposal immediately fails. (This veto may be contested with a CfJ if it is thought excessively unreasonable.)
* E may change the BlogNomic header, the colour scheme and the VETO icon, whenever e likes.

If there is no Captain, any Swashbuckler may propose a new header, color scheme, and/or VETO icon. If such a proposal passes, the changes will be made by any Admin.

A page of [[Dynasty Records]] is kept on a separate weblog, recording events that took place during past Dynasties, noting eir themes, eir Captain or equivalent, interesting rules, large arguments, the winning move, etc. A Dynasty record must accurately reflect the Dynasty it refers to. Swashbucklers may submit Dynasty Records to the Captain.

==Victory and Ascension==

If a [[#Swashbucklers|Swashbuckler]] believes that e has achieved '''victory''' as specified in the current [[#Ruleset and Gamestate|Ruleset]], e may {{Make a Post}} to the Blognomic frontpage entitled '''"Declaration of Victory"''', and a '''Hiatus''' begins. So long as the Hiatus is in effect, the only game actions that may be taken are those covered by laws 1.2, 1.6, and 1.9.

Every Swashbuckler may respond to the Declaration of Victory saying whether e regards it as legal or illegal (using the FOR, AGAINST and DEFERENTIAL icons). The following stipulations must be true before a DoV may pass or fail.
* 12 hours have passed since the posting of the DoV.
* If less than 24 hours have passed since the posting of the DoV the current Captain has voted upon the DoV.
If both of these stipulations are true and at least half of all Swashbucklers have voted FOR the DoV passes and the poster of the Declaration is considered to have officially won the Dynasty - the Dynasty ends. If both of these stipulations are true and at least half of all Swashbucklers have voted AGAINST the DoV the the DoV fails. If no clear decision is reached after 24 hours, the [[#Dynasties|Captain]] may optionally Pass or Fail the DoV on his own accord.

Hiatus may not end if either of the following stipulations are false and ends once they are both true:
* There is no active DoV.
* There are no pending CFJs.

At the winner's discretion, e may choose another active Swashbuckler to be the Captain for the next dynasty. This is known as '''Passing the Mantle'''. If the selected Swashbuckler agrees, then all rights and responsibilities of the Captain transfer to the selected Swashbuckler. If the winner makes no mention of Passing the Mantle, it is assumed that the winner has decided to become the next Captain.

When a Dynasty has been won, all Swashbucklers' {{GNDT}} stats are reset to zero or blank. Any Swashbucklers who were idle throughout that Dynasty may be removed from the game, at the Captain's discretion.

The Hiatus then continues until the new Captain posts an '''Ascension Address''' to the BlogNomic weblog - this shall specify the Captain's chosen theme for the new round, and may optionally include a proclamation that any number of Rules will be repealed, and/or that the words "Swashbuckler" and "Captain" will be replaced with new theme-appropriate terms. If the new Captain chooses not to repeal a rule, e may also replace any keyword in those rules with a new theme-appropriate term. The remaining rules, after the new Captain's proclamation, shall be renumbered to keep a sequential progression. The new Captain may also proclaim at the Ascension Address the veto of any Pending Proposals.

Upon posting this Address, and having made the Ruleset changes, the Hiatus period ends and the new Dynasty commences.

The Captain may not declare victory in eir own dynasty.

</div>

= Rules =

<div style="padding:8px;background:#ddd;margin:8px 0px;">

= Glossary =

This is always at the end of the Ruleset. Its only effect can be to clarify ambiguity.

* It is noted that where a [[#Proposals|Proposal]] would '''amend''' the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their writer a banana when enacted would not earn a banana for its own writer, when enacted).
* Rules which '''trigger''' on Enactment or Failure of a Proposal are the responsibility of the acting Admin, who is responsible to check if Quorum is met at the moment of the Enactment.
* Appropriate '''Icons''': For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a vote AGAINST, an I http://blognomic.com/images/vote/imperial.gif shall represent a vote of DEFERENTIAL, and an Imperial Seal (currently http://blognomic.com/images/vote/seal.gif) shall represent the Imperial Veto.
* The '''"subject"''' of a blog entry is the first and only sentence in the Title of an entry. Any entry that does not have exactly one subject is not valid.
* '''"Posts"''' and '''"comments"''' refer only to those made to the BlogNomic weblog at [http://blognomic.com blognomic.com]
* A '''keyword''' defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "Bananas are Blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)
* Unless otherwise specified, game '''variables''' defined to hold numeric values can hold only non-negative integers, and any action that would set those values below '''zero''' instead sets them to zero. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
* Superficial differences between the '''spelling''' of geographic versions of English, e.g, British English, American English, Australian English shall be construed as irrelevant for the purposes of play.
* '''Gamestate''' is defined as any information which the Ruleset regulates the alteration of, such as Countries' names and the blog colour scheme.

== Typographic Conventions ==

* '''Italicized text''' is not considered part of the ruleset and may be used to clarify rules with examples, notes and flavor text. ''For example, this italicized text provides an example of the use of italicized text.''

== Timespans ==

* References to '''"a day"''' (as an entity rather than a duration, eg. "Sunday") refer to that day in the timezone of the BlogNomic blog, which is considered to be GMT for all purposes.
* References to a '''"week"''' refer to the period of time between the start of a Monday and the end of the following Sunday.
* All '''references to time''' must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
* An action which may be taken''' 'often' '''may be taken once per day, but not more than once every six hours.
* An action which may be taken''' 'occasionally' '''may be taken once per week, but not more than once per twenty-four hours.

== Dice ==

References to '''"YDICEX"''' refer to Y X-sided dice. To roll dice, post DICEX in the comments field of a post, replacing X with the number of sides on the die you wish to roll.

== Spivak ==

* The Spivak pronouns used in Blognomic are:
** Subject case: '''"e"''';
** Object case: '''"em"''';
** Possessive Adjective case: '''"eir"''';
** Possessive Pronoun case: '''"eirs"''';
** Reflexive case: '''"emself"'''.

== IEEE ==
* The IEEE auxiliary verbs used in Blognomic are:
** Is required to: '''â€œshallâ€''';
** Is recommended that: '''â€œshouldâ€''';
** Is permitted to: '''â€œmayâ€''';
** Is able to: '''â€œcanâ€'''.
</div>

Local Proposals

2006-07-05T17:58:14Z

Purplebeard:

==Example Proposal (this is not a legal proposal)==
===Proposal: Example (0001/01/01)===
Proposed by Angry Grasshopper

"Cheese may never be called awesome."
====Votes====

Excalabur: http://blognomic.com/images/vote/for.gif

Hix: http://blognomic.com/images/vote/seal.gif

Angry Grasshopper: http://blognomic.com/images/vote/for.gif

Bucky: http://blognomic.com/images/vote/imperial.gif

Chronos Phaenon: http://blognomic.com/images/vote/against.gif

====Outcome====
http://blognomic.com/images/vote/against.gif (Failed)

==Local Proposals==

Commodities Market

2005-10-21T09:39:44Z

Purplebeard: /* Purplebeard */ Paying for reproduction

{{TOCRight}}
*The [[World]]
*The [[Ruleset]]
*The [[Quick Reference]]
*The [[Talk:Commodities Market|Discussion Page]]

== [[User:Excalabur|Excalabur]] ==
* Grain: 345
* Metal: 515
* Petroleum: 182
* Nat.Beauty: 145

== [[User:GazeboDude|Gazebo Dude]] ==
* Grain: 314
* Metal: 664
* Petroleum: 108
* Nat.Beauty: 0

== [[User:Jamuraa|Jamuraa]] ==
* Grain: 374
* Metal: 696
* Petroleum: 167
* Nat.Beauty: 0

== [[User:Purplebeard|Purplebeard]] ==
* Grain: 386
* Metal: 502
* Petroleum: 117
* Nat.Beauty: 19

== [[User:Rodney|Rodney]] ==
* Grain: 344
* Metal: 410
* Petroleum: 251
* Nat.Beauty: 0

== [[User:Smith|Smith]] ==
* Grain: 153
* Metal: 367
* Petroleum: 35
* Nat.Beauty: 54

== [[User: Lunaetic|Lunaetic]] ==
* Grain: 205
* Metal: 323
* Petroleum: 74
* Nat.Beauty: 0

World

2005-10-21T09:39:30Z

Purplebeard: /* Purplebeard Homeland */ Initiating reproduction

{{TOCRight}}
*The [[Commodities Market]]
*The [[Ruleset]]
*The [[Quick Reference|Quick Reference Page]]
== Chronos Phaenon Homeland ==
* Controller: '''Excalabur'''
* Population: 133
* Maximum Beauty: 24
=== Production ===
* Grain: 13
* Metal: 9
* Petroleum: 4
* Natural Beauty: -2

=== Buildings ===
* Operating: Fortification

=== Adjacent to ===
* (2) Excalabur Homeland
* (3) Gazebo Dude Homeland
* (4) Jamuraa Homeland
* (5) Purplebeard Homeland
* (6) Rodney Homeland
* (7) Seventy-Fifth Trombone Homeland
* (8) ShadowClaw Homeland
* (9) Smith Homeland
* (10) Tekneek Homeland
* (11) Devil's Hole
* (13) Area 51
* (14) Somewhere over the Rainbow
* (15) Death's Valley
* (23) The Pervasive Sea
* (24) Cul-de-Sac
* (25) Sea of Serenity
* (26) Munchkinland
* (31) Lunaetic Homeland

=== In Transit ===
* Invasion Transport: Smith Homeland, 2, ? periods left (smith)

== Excalabur Homeland ==
* Controller: '''Excalabur'''
* Population: 122
* Maximum Beauty: 24
=== Production ===
* Grain: 6
* Metal: 5
* Petroleum: 11
* Natural Beauty: 2

=== Buildings ===
*Operating: Farm
*Operating: Steel Mill

=== Events ===

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (9) Smith Homeland
* (18) Scotland
* (21) Botany Bay
* (23) The Pervasive Sea
* (27) Doldrums
* (29) James Pond
* (31) Lunaetic Homeland
* (32) Royal Hunting Ground

== Gazebo Dude Homeland ==
* Controller: '''Gazebo Dude'''
* Population: 208
* Maximum Beauty: 24

=== Production ===
* Grain: 4
* Metal: 13
* Petroleum: 14
* Natural Beauty: -7

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (9) Smith Homeland
* (15) Death's Valley
* (21) Botany Bay
* (23) The Pervasive Sea

== Jamuraa Homeland ==
* Controller: '''Jamuraa'''
* Population: 142
* Maximum Beauty: 24

=== Production ===
* Grain: 11
* Metal: 15
* Petroleum: 3
* Natural Beauty: -5

=== Buildings ===
* Operating: Farm
* Operating: Oil Well

=== Events ===

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (12) Londinium
* (14) Somewhere Over the Rainbow
* (16) Shangri-La
* (20) Sinon
* (21) Botany Bay
* (23) The Pervasive Sea
* (29) James Pond

== Purplebeard Homeland ==
* Controller: '''Purplebeard'''
* Population: 117
* Maximum Beauty: 24

=== Production ===
* Grain: 10
* Metal: 12
* Petroleum: 11
* Natural Beauty: -9

=== Buildings ===
* Oil well
* Operating: Oil well
* Operating: Farm
* Operating: Farm
* Operating: Farm

=== Events ===
Fomenting: Reproduction, 1 periods left

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (16) Shangri-La
* (19) Bacon
* (22) Your Mother
* (23) The Pervasive Sea
* (28) Castle Black

== Rodney Homeland ==
* Controller: '''Rodney'''
* Population: 139
* Maximum Beauty: 24

=== Production ===
* Grain: 11
* Metal: 15
* Petroleum: 15
* Natural Beauty: -17

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (13) Area 51
* (17) Greater Erg
* (20) Sinon
* (23) The Pervasive Sea

== Seventy-Fifth Trombone Homeland ==
* Controller: Uncontrolled
* Population: 100
* Maximum Beauty: 24

=== Production ===
* Grain: 10
* Metal: 6
* Petroleum: 2
* Natural Beauty: 6

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (12) Londinium
* (14) Somewhere over the Rainbow
* (23) The Pervasive Sea

== ShadowClaw Homeland ==
* Controller: '''Excalabur'''
* Population: 107
* Maximum Beauty: 24

=== Production ===
* Grain: 9
* Metal: 10
* Petroleum: 12
* Natural Beauty: -7

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (10) Tekneek Homeland
* (23) The Pervasive Sea
* (25) Sea of Serenity
* (29) James Pond
* (32) Royal Hunting Ground

== Smith Homeland ==
* Controller: '''Smith'''
* Population: 141
* Maximum Beauty: 24

=== Production ===
* Grain: 8
* Metal: 9
* Petroleum: 4
* Natural Beauty: 3

=== Constructions ===
* Operating: Oil Well
* Operating: Farm
* Constructing: Portable Mountain, 3 periods left

=== Events ===
*Fomenting: Hostile Takeover(Greater Erg), 2 periods left

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (2) Excalabur Homeland
* (3) Gazebo Dude Homeland
* (16) Shangri-La
* (17) Greater Erg
* (14) Somewhere over the Rainbow
* (21) Botany Bay
* (23) The Pervasive Sea
* (26) Munchkinland

=== In Transit ===
Basic Transport: Area 51, 5, 1 period left (smith)

Invasion: Chronos Phaenon Homeland, 6, ? periods left (Excalabur)

== Tekneek Homeland ==
* Controller: '''Excalabur'''
* Population: 23
* Maximum Beauty: 24

=== Production ===
* Grain: 14
* Metal: 14
* Petroleum: 1
* Natural Beauty: -5

=== Buildings ===
Constructing: Oil Well, 6 periods left

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (8) ShadowClaw Homeland
* (13) Area 51
* (14) Somewhere over the Rainbow
* (23) The Pervasive Sea

== Devil's Hole ==
* Controller: '''Excalabur'''
* Population: 110
* Maximum Beauty: 21

=== Production ===
* Grain: 3
* Metal: 5
* Petroleum: 5
* Natural Beauty: 8

=== Constructions ===
Operating: Tourist Destination

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (13) Area 51
* (16) Shangri-La
* (18) Scotland
* (23) The Pervasive Sea
* (30) Hundred Acre Woods

== Londinium ==
* Controller: '''Jamuraa'''
* Population: 94
* Maximum Beauty: 20

=== Buildings ===
* Constructing: Farm, 1 periods left

=== Production ===
* Grain: 6
* Metal: 10
* Petroleum: 4
* Natural Beauty: 0

=== Adjacent to ===
* (4) Jamuraa Homeland
* (7) 75th Trombone Homeland
* (21) Botany Bay
* (23) The Pervasive Sea

== Area 51 ==
* Controller: '''Excalabur'''
* Population: 104
* Maximum Beauty: 20

=== Production ===
* Grain: 5
* Metal: 3
* Petroleum: 5
* Natural Beauty: 7

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (6) Rodney Homeland
* (10) Tekneek Homeland
* (11) Devil's Hole
* (16) Shangri-La
* (23) The Pervasive Sea
* (31) Lunaetic Homeland

=== In transit ===
Invasion Transportation: Rodney Homeland, 21, ? periods left

== Somewhere over the Rainbow ==
* Controller: '''Jamuraa'''
* Population: 83
* Maximum Beauty: 20

=== Production ===
* Grain: 8
* Metal: 10
* Petroleum: 3
* Natural Beauty: -1

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (4) Jamuraa Homeland
* (7) 75th Trombone Homeland
* (9) Smith Homeland
* (10) Tekneek Homeland
* (16) Shangri-La
* (17) Greater Erg
* (21) Botany Bay
* (27) Doldrums
* (29) James Pond

== Death's Valley ==
* Controller: '''Excalabur'''
* Population: 123
* Maximum Beauty: 20

=== Production ===
* Grain: 4
* Metal: 1
* Petroleum: 2
* Natural Beauty: 13

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (3) Gazebo Dude Homeland
* (16) Shangri-La
* (20) Sinon
* (23) The Pervasive Sea

== Shangri-La ==
* Controller: '''Excalabur'''
* Population: 66
* Maximum Beauty: 20

=== Production ===
* Grain: 2
* Metal: 9
* Petroleum: 4
* Natural Beauty: 5

=== Adjacent to ===
* (4) Jamuraa Homeland
* (5) Purplebeard Homeland
* (9) Smith Homeland
* (11) Devil's Hole
* (13) Area 51
* (14) Somewhere over the Rainbow
* (15) Death's Valley
* (25) Sea of Serenity
* (28) Castle Black

== Greater Erg ==
* Controller: Occupied by Smith
* Population: 106 (20)
* Maximum Beauty: 20

=== Production ===
* Grain: 3
* Metal: 3
* Petroleum: 7
* Natural Beauty: 7

=== Constructions ===
* Operating: Fortification(smith)
* Constructing: Tourist Destination, 2 periods left

=== Adjacent to ===
* (6) Rodney Homeland
* (9) Smith Homeland
* (14) Somewhere over the Rainbow
* (29) James Pond
* (30) Hundred Acre Woods

== Scotland ==
* Controller: '''Excalabur'''
* Population: 144
* Maximum Beauty: 20

===Production===
* Grain: 9
* Metal: 6
* Petroleum: 10
* Natural Beauty: -5

=== Buildings===
Operating: Oil Well

Operating: Oil Well

===Adjacent to ===
* (2) Excalabur Homeland
* (11) Devil's Hole
* (21) Botany Bay
* (23) The Pervasive Sea
* (27) Doldrums

== Bacon ==
* Controller: '''Purplebeard'''
* Population: 84
* Maximum Beauty: 20

===Production===
* Grain: 9
* Metal: 8
* Petroleum: 2
* Natural Beauty: 1

===Buildings===
* Operating: Steel Mill
* Operating: Steel Mill
===Adjacent to ===
* (5) Purplebeard Homeland
* (21) Botany Bay
* (22) Your Mother
* (23) The Pervasive Sea
* (27) Doldrums
* (30) Hundred Acre Woods

== Sinon ==
* Controller: '''Jamuraa'''
* Population: 81
* Maximum Beauty: 20

=== Production ===
* Grain: 1
* Metal: 9
* Petroleum: 9
* Natural Beauty: 1

=== Adjacent to ===
* (4) Jamuraa Homeland
* (6) Rodney Homeland
* (15) Death's Valley
* (23) The Pervasive Sea

=== In Transit ===

== Botany Bay (Oceanic) ==
* Controller: Occupied by Purplebeard
* Population: 0 (1)
=== Adjacent to ===
* (2) Gazebo Dude Homeland
* (3) Excalabur Homeland
* (4) Jamuraa Homeland
* (9) Smith Homeland
* (12) Londinium
* (14) Somewhere over the Rainbow
* (18) Scotland
* (19) Bacon
* (27) Doldrums

== Your mother ==
* Controller: '''Purplebeard'''
* Population: 59
* Maximum Beauty: 20

=== Production: ===
* Grain: 8
* Metal: 3
* Petroleum: 10
* Natural Beauty: -1

=== Adjacent to ===
* (5) Purplebeard Homeland
* (19) Bacon
* (23) The Pervasive Sea
* (26) Munchkinland
* (27) Doldrums

== The Pervasive Sea (Oceanic) ==
* Controller: Occupied by Purplebeard
* Population: 0 (1)

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (2) Gazebo Dude Homeland
* (3) Excalabur Homeland
* (4) Jamuraa Homeland
* (5) Purplebeard Homeland
* (6) Rodney Homeland
* (7) Seventy-Fifth Trombone Homeland
* (8) ShadowClaw Homeland
* (9) Smith Homeland
* (10) Tekneek Homeland
* (11) Devil's Hole
* (12) Londinium
* (13) Area 51
* (15) Death's Valley
* (18) Scotland
* (19) Bacon
* (20) Sinon
* (22) Your Mother

== Cul-de-Sac ==
* Controller: Occupied by Smith
* Population: 113 (+2 smith)
* Maximum Beauty: 20

=== Production: ===
* Grain: 10
* Metal: 6
* Petroleum: 9
* Natural Beauty: -5

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (27) Doldrums

=== In Transit ===

== Sea of Serenity (Oceanic) ==
* Controller: Uncontrolled
* Population: 0

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (8) Shadowclaw Homeland
* (16) Shangri-la

== Munchkinland ==
* Controller: '''Purplebeard'''
* Population: 71
* Maximum Beauty: 20

=== Production ===
* Grain: 10
* Metal: 6
* Petroleum: 1
* Natural Beauty: 3

=== Buildings ===
* Operating: Fortification

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (9) Smith Homeland
* (22) Your Mother
* (27) Doldrums

== Doldrums (Oceanic) ==
* Controller: Occupied by Purplebeard
* Population: 0 (1)

=== Adjacent to ===
* (2) Excalabur Homeland
* (14) Somewhere over the rainbow
* (18) Scotland
* (19) Bacon
* (21) Botany Bay (Oceanic)
* (22) Your Mother
* (24) Cul-de-Sac
* (26) Munchkinland
* (28) Castle Black
* (32) Royal Hunting Grounds

== Castle Black ==
* Controller: '''Excalabur'''
* Population: 48
* Maximum Beauty: 20

=== Production ===
* Grain: 7
* Metal: 5
* Petroleum: 3
* Natural Beauty: 5

=== Adjacent to ===
* (5) Purplebeard Homeland
* (16) Shangri-La
* (27) Doldrums (Oceanic)

== James Pond (Oceanic) ==
* Controller: None.

=== Adjacent to ===
* (2) Excalabur Homeland
* (4) Jamuraa Homeland
* (8) ShadowClaw Homeland
* (14) Somewhere Over the Rainbow
* (17) Greater Erg

== Hundred Acre Woods ==
* Controller: '''Purplebeard'''
* Population: 26
* Maximum Beauty: 20

=== Production ===
* Grain: 1
* Metal: 2
* Petroleum: 6
* Natural Beauty: 11

=== Adjacent to ===
* (19) Bacon
* (11) Devil's Hole
* (17) Greater Erg

== Lunaetic Homeland ==
* Controller: '''Lunaetic'''
* Population: 27
* Maximum Beauty: 24

=== Production ===
* Grain: 4
* Metal: 8
* Petroleum: 14
* Natural Beauty: -2

=== Adjacent to ===
* (1) Chronos Phaenon Homeland
* (2) Excalabur Homeland
* (12) Londinium

=== In transit ===
* Invasion Transportation: Smith Homeland, 20, ? periods left

== Royal Hunting Ground ==
* Controller: Occupied by Purplebeard
* Population: 51 (1)
* Maximum Beauty: 20

=== Production ===
* Grain: 10
* Metal: 5
* Petroleum: 9
* Natural Beauty: -4

=== Adjacent to ===
* (2) Excalabur Homeland
* (8) Shadowclaw Homeland
* (27) Doldrums (Oceanic)

Quick Reference

2005-10-20T19:46:21Z

Purplebeard: /* Excalabur */ Update

{{TOCRight}}

*The [[Commodities Market]]
*The [[World]]
*The [[Ruleset]]

== Excalabur ==
* Population: 993
* Production Capacity ''plus Occupied territory production'':
** Grain: 72
** Metal: 67
** Petroleum: 57
** Natural Beauty: 21

* Territories '''Controlled''' and ''Occupied'': '''[[World#Excalabur Homeland|Excalabur Homeland]]''', '''[[World#Area 51|Area 51]]''', '''[[World#Devil's Hole|Devil's Hole]]''', '''[[World#Scotland|Scotland]]''', '''[[World#Shangri-La|Shangri-La]]''', '''[[World#Death's Valley|Death's Valley]]''', '''Castle Black''', '''Tekneek Homeland''', '''Chronos Phaenon Homeland''', '''ShadowClaw Homeland'''
* Territories Disputed: None

* Alliance: None
* At War with: None

== Gazebo Dude ==
* Population: 208
* Production Capacity ''minus 1 from war)'':
** Grain: 4 ''-1''
** Metal: 13 ''-1''
** Petroleum: 14 ''-1''
** Natural Beauty: -7 ''+7''

* Territories '''Controlled''' and ''Occupied'': '''[[World#Gazebo Dude Homeland|Gazebo Dude Homeland]]'''
* Territories Disputed: None.

* Alliance: Underdog Free Trade Association (UFTA)
* At War with: Purplebeard

== Jamuraa ==
* Population: 400
* Production Capacity ''plus ocuppied terr. production'':
** Grain: 26
** Metal: 44
** Petroleum: 19
** Natural Beauty: -5

* Territories '''Controlled''' and ''Occupied'': '''[[World#Jamuraa Homeland|Jamuraa Homeland]]''', '''[[World#Londinium|Londinium]]''', '''[[World#Somewhere over the Rainbow|Somewhere over the Rainbow]]''', '''[[World#Sinon|Sinon]]'''
* Territories Disputed: None

* Alliance: Overdog Free Trade Association (OFTA)
* At War with: None

== Purplebeard ==
* Population: 357
* Production Capacity ''plus ocuppied terr. production, minus 1 because of war''
** Grain: 38 ''-1''
** Metal: 31 ''-1''
** Petroleum: 30 ''-1''
** Natural Beauty: 5 ''+11 (most of my production capacities are set to 0)''

* Territories '''Controlled''' and ''Occupied'': '''[[World#Purplebeard Homeland|Purplebeard Homeland]]''', '''[[World#Bacon|Bacon]]''', '''[[World#Your mother|Your mother]]''', '''[[World#Munchkinland|Munchkinland]]''', '''[[World#Hundred Acre Woods|Hundred Acre Woods]]''', ''[[World#Botany Bay (Oceanic)|Botany Bay (Oceanic)]]'', ''[[World#Pervasive Sea (Oceanic)|Pervasive Sea (Oceanic)]]'', ''[[World#Doldrums (Oceanic)|Doldrums (Oceanic)]]'', ''[[World#Royal Hunting Ground|Royal Hunting Ground]]''
* Territories Disputed: None.

* Alliance: None
* At War with: Underdog Free Trade Association (UFTA)

== Rodney ==
* Population: 139
* Production Capacity ''Minus one because of the war'':
** Grain: 11 ''-1''
** Metal: 15 ''-1''
** Petroleum: 15 ''-1''
** Natural Beauty: -17 ''+17''

* Territories '''Controlled''' and ''Occupied'': '''[[World#Rodney Homeland|Rodney Homeland]]'''
* Territories Disputed:

* Alliance: Underdog Free Trade Association (UFTA)
* At War with: Purplebeard

== Smith ==
* Population: 144
* Production Capacity ''plus ocuppied terr. production, minus 1 because of the war''
** Grain: 8 ''+1''
** Metal: 9 ''+1''
** Petroleum: 4 ''+1''
** Natural Beauty: 3 ''+1''

* Territories '''Controlled''' and ''Occupied'': '''[[World#Smith Homeland|Smith Homeland]]''', ''[[World#Greater Erg|Greater Erg]]'','' [[World#Cul-de-Sac|Cul-de-Sac]]''
* Territories Disputed: None

* Alliance: Underdog Free Trade Association (UFTA)
* At War with: Purplebeard

== Lunaetic ==
* Population: 27
* Production Capacity
** Grain: 4
** Metal: 8
** Petroleum: 14
** Natural Beauty: -2

* Territories '''Controlled''' and ''Occupied'': '''[[World#Lunaetic Homeland|Lunaetic Homeland]]'''
*Territories Disputed: None

* Alliance: None
* At War with: None

== Unoccupied Territories ==
* [[World#Sea of Serenity (Oceanic)|Sea of Serenity (Oceanic)]]