Returning players! Wiki accounts were reset in late 2014. If you haven't played since then and wish to edit the wiki, you'll need a fresh account.


From BlogNomic Wiki
Jump to: navigation, search

Core Rules

Ruleset and Gamestate

This is the Ruleset for BlogNomic; all Explorers 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.

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

If the Ruleset does not properly reflect all legal changes that have been made to it, any Explorer may update it to do so.


Any human may apply to join BlogNomic (if they are not already an Explorer) by registering at via the Register link in the sidebar, and then making a post making clear their wish to be a Explorer. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become an Explorer.

An Explorer may cease to be an Explorer at any time by posting an entry to the BlogNomic weblog requesting such an action. A human who has ceased to be an Explorer in this way may not become an Explorer again within the following two weeks. An Explorer may only change their name as a result of a proposal approving the change.

Some Explorers are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Explorers 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 Explorers

Some Explorers 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”, “Explorers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Explorers are not counted as Explorers.

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

When an Explorer 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 Explorer Idled in a different dynasty), the Explorer is given the default value for new Explorer, if such a value exists.

An Admin may render an Explorer Idle if that Explorer has asked to become Idle in an entry or comment from the past four days, or if that Explorer 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 an Explorer if that Explorer 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 Explorer 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.


BlogNomic is divided into a number of Dynasties. Each Dynasty may be headed by a single Explorer, known as the Expedition Leader. If there is no Expedition Leader, the Dynasty is a Metadynasty.

Votable Matters

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

Each Explorer 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. An Explorer’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-Explorer never has a Vote, even if they were an Explorer 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). Comments cannot be made on Enacted or Failed Votable Matters.

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


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

Special Proposal Voting

When an Explorer 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 Expedition Leader may use VETO as a voting icon to cast a Vote on a proposal; when the Expedition Leader casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Expedition Leader later changes their Vote.

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

Resolution of Proposals

The oldest pending 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 Explorers 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 Explorers actively disagree as to the interpretation of the Ruleset, or if an Explorer feels that an aspect of the game needs urgent attention, then any Explorer 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 an Explorer (other than the Expedition Leader) 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 “Explorers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Explorer 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 Expedition Leader 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 Explorers 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 Explorer who made the DoV as its Expedition Leader. That Explorer may pass this role to another Explorer at this point by making a post to that effect, if they wish. The Hiatus continues until the new Expedition Leader makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Expedition Leader's chosen theme for the new Dynasty, and may optionally specify that the terms Explorer and Expedition Leader 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 Explorer 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 an Explorer'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 non-Idle Explorer within BlogNomic, and should announce publicly if they control both a non-Idle Explorer and any Idle Explorers.
  • An Explorer 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 Explorer should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
  • An Explorer should not edit their own blog comments once posted, nor those of any other Explorer.
  • An Explorer should not edit the "Entry Date" field of a blog post.
  • An Explorer should not make a DoV primarily to delay the game by putting it into Hiatus.
  • An Explorer 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”.

Atomic Actions

When an Explorer performs an Atomic Action, they must complete all its steps; they must complete them in order; and they may not take any other action defined in the Ruleset until all such steps are complete. In addition, the Explorer performing an Atomic Action performs its steps as quickly as they are able.

If one or more steps of an Atomic Action were done incorrectly, the Explorer must redo the Atomic Action. In redoing an Atomic Action, the Explorer uses any legal steps that were already completed in the illegal Atomic Action and only redoes the illegal ones.

For instance if an Atomic Action consists of rolling a die in the GNDT and then doing steps based upon it’s result the Explorer would have to reroll the die if they rolled the wrong one if the first place and any steps that depended upon the result of that die; however if all they did was take an illegal action later on, the die is still used in the redone action.

If the Atomic Action was illegal due to a die that was wrong in the GNDT (for example, rolling a 1 on a DICE6 gives that Explorer a point and the rest do nothing and the Explorer rolls a DICE5 in the first one) and in redoing the Atomic Action they get the same effect as before (i.e. rolling an incorrect die and getting result X but then rolling the correct die and still getting result X) then the steps that depended upon that result are valid and don’t need to be redone. Steps that depend upon multiple dice which were done incorrectly must have each incorrect die have the same effect to be considered valid.

For the purposes of determining the ordering or legality of game actions the time of an Atomic Action shall be the time that it is completed. For Atomic Actions that are redone, the time of completion is the last redone step.

Dynastic Rules {Base Camp} (0 BTU)

Combos {Base Camp} (0 BTU)

Anytime that an Explorer wants to do 5 or more actions within an hour they may choose in lieu of doing all of those actions separately, which potentially causes confusion as to what is happening, to make a “Combo” blog post that cannot be edited after posting. The gamestate may be changed to reflect the results of the Combo once all of the actions are completed.

A Combo post is a numbered list of the actions taken, the first action is #1 each subsequent number of actions is increased by one. Each action and the portion of the gamestate changed from that action are kept on their own line. An Atomic action has lettering of it’s steps, refer to the example and note the curly braces vs the parenthesis.

   Example Combo
   1 [action one] ([gamestate before action] -> [gamestate after action])
   2 [action two] ([gamestate before action] -> [gamestate after action])
   3 [atomic action] {[gamestate before atomic action]}
   3a [first atomic substep] ([gamestate before substep] -> [gamestate after substep])
   3b [second atomic substep] ([gamestate before substep] -> [gamestate after substep]) {[gamestate after atomic action]}
   4 [action four] ([gamestate before action] -> [gamestate after action])
   etcetera . . .

If any actions require a die roll or other random event that is visible to the public, Explorers must make those rolls before posting the combo with a note stating which step the roll is for and what action they are taking and the title of their Combo. Explorers may not make multiple rolls in the GNDT for the same step. Explorers cannot have two or more rolls in the GNDT with Combo titles that are different unless all but one of the Combo titles have been posted and include that roll.

Each action of a Combo happens in their own second, substeps of an Atomic Action happen all at the same second as the parent step. The first action happens at the time the Combo is posted.

Tags {Base Camp} (0 BTU)

Tags are put in the title of the votable matter with the format “[X]” where X is the tag. Votable matters with tags in their titles are considered to have those tags. Tags which are not defined anywhere are invalid. Votable matters cannot have invalid tags.

Votable matters have at least one tag, if no tags are given the defaults are used. Proposals default to [Dynastic] and [Gamestate], DoV default to [Victory] and [Gamestate] and other Votable matters default to the [Gamestate] tag. CfJ default to every tag.

Some valid tags are:

  • Victory
  • Dynastic
  • Gamestate
  • Core
  • Appendix

Tags, other than [Victory] and [Gamestate], correspond to a rules which in the ruleset’s table of contents are prefixed with a string containing only numerals. For each tag which corresponds to a section in the ruleset, votable matters can only make changes to that tag’s corresponding ruleset section if they have that tag.

Votable matters can only affect the gamestate if they have the [Gamestate] tag. Votable matters can only give an Explorer victory if they have the [Victory] tag.

The partial list of valid tags is maintained as follows:

  • tags, other than [Victory] and [Gamestate], which do not have a section in the ruleset they correspond to are not valid and should be removed from the list.
  • rules which have a prefix in the ruleset’s Table of Contents that contain only numerals and don’t have a corresponding tag should have a tag added to the list. Adding a tag to the list is done by taking the section name that needs a tag and adding it to the list of valid tags. Then if the most recently added tag has the word “Rules”, remove that word from the tag unless that is the only word in the tag.

Supplies {Base Camp} (0 BTU)

Every Explorer has a number of Dog Sleds and a number of Supplies, both of which are tracked in the GNDT. The number of Dog Sleds defaults to 1, the number of Supplies defaults to 10.

The maximum amount of Supplies an Explorer can have is ten times the amount of Dog Sleds they have.

Explorers may transfer supplies or dog sleds to the other Explorers at the same camp. Explorers may transfer supplies to their current camp.

Camps {Base Camp} (0 BTU)

Every Explorer is located at a Camp. This is tracked as a String under “Location” in the GNDT and defaults to “Base Camp”. Camps along with their state are tracked on the wiki page called “Camps”. Each Camp has an amount of Supplies and a Latitude. Latitude is an angle which ranges from 66° to 90° (both inclusive). In addition, each section tracking a Camp can have a Description, which is a subsection of their Section on the “Camps” page.

Camps have temperatures tracked on the Camps wikipage. The default temperature for a Camp is 0 BTU.

As a daily action, an Explorer may take X Supplies from the Camp they are located at. If they do, their Debt increases by X.

Temperature {Base Camp} (0 BTU)

All Dynastic Rules have a Temperature. Temperature is a value in Blognomickian Temperature Units, which is an integer (which can be negative) and can be employed as XXX BTU, where XXX is the temperature value in Blognomickian Temperature Units.

The default Temperature for any entity that has Temperature is -500 BTU.

The list of entities which have Temperature are:

  • Dynastic Rules
  • Camps

A Temperature of -1000 BTU or lower is Extremely Cold. A Temperature of -500 BTU or lower is Very Cold.

If the Temperature of any Rule is different than the default, that Temperature must be tracked in the Rule’s title as a string which is “(XXX BTU)” which is located at the end of the Rule’s name, where XXX is that Rule’s Temperature. For example: “Eiffel Tower (-232 BTU)”

Exploration {Base Camp} (0 BTU)

Each Explorer has a non-negative integer Square Miles Charted, which is tracked in the GNDT.

Dog Teams {Base Camp} (0 BTU)

Each Explorer belongs to a particular Dog Team, represented by a single capital letter from A through Z, tracked in the GNDT. An Explorer may change their Dog Team at any time if they share the same Camp as all other Explorers belonging to the Dog Team they are changing to. If all Explorers that belong to the same Dog Team are able to move to the same Camp, any Explorer that belongs to that Dog Team may move all of that team’s Explorers to that Camp.

Supplies {Base Camp} (0 BTU)

If an Explorer has one or more Dog Sleds, they may change their camp to either the camp with the next highest latitude or the camp with the next lowest latitude, both relative to their current camp, by spending 1 Supplies. They cannot take this action if they have zero or less supplies.

Explorers must spend 1 supplies each time they do an action which defined in rules that are Very Cold. Explorers must spend 1 supplies each time they do an action which defined in rules that are Extremely Cold. If an Explorer has zero or less supplies, they cannot take actions which are defined in rules that are Very Cold.

Camp Rules {Base Camp} (0 BTU)

Each Dynastic rule can be located in a Camp. This is tracked on the Camps wikipage. It is also tracked in the title of the rule, located before the temperature of that rule, with the name of the camp enclosed in in curly braces “{NAME OF CAMP}”. The default Camp for a rule is Base Camp. The Temperature of a Dynastic Rule is the same as the Camp that it is located in. Dynastic Rules which are not in one or more Camps have a temperature of -500 BTU.

Background {Base Camp} (0 BTU)

Each Explorer (which isn’t the Expedition Leader) has none or two Backgrounds, which is privately tracked by the Expedition Leader, and Explorers default to having no Backgrounds. The Backgrounds an Explorer may have, and the powers (if any) that they have for having such a Background are the following:

  • Handyman:
  • Adventurer:
  • Scholar:
  • Military:
  • Spy:
  • Cultist: When a Cultist becomes such, or upon private request to the Expedition Leader for a reminder, the Expedition Leader shall privately communicate to them the Secret Creed in a timely fashion.

If an Explorer has no Backgrounds, they can, at-will but once ever during this Dynasty, privately request the Expedition Leader their Backgrounds. The Expedition Leader then can and shall grant them two (secretly random and different) Backgrounds in a timely fashion, and privately communicate to the requesting Explorer what their new Backgrounds are.

The Secret Creed contains one number and five words. For example: “13, copper explain ill-fated truck neat”. The content of the Secret Creed is privately tracked by the Expedition Leader.

Debt {Base Camp} (0 BTU)

Each Explorer has a Debt value, which starts at 0 and is tracked in the GNDT under “Debt”.



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

"is able to"
A blog comment published to the BlogNomic weblog at
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 Explorers.
Daily Action
If a game action is a Daily Action, each Explorer 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 Explorer per 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.
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)
An Explorer’s Effective Vote Comment with respect to a given Votable Matter means that Explorer’s Comment to that Votable Matter, if any, that contains that Explorer’s Vote on that Votable Matter.
Flavour Text
When posting a blog entry, an Explorer 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.
Any information which the Ruleset regulates the alteration of. All GNDT columns that the Dynastic Rules explicitly mention are assumed to be Gamestate, as are all Wiki Pages that the Dynastic Rules explicitly mention except for dynastic histories and discussion pages.
IRC Channel
The Blognomic IRC channel is located at #nomic on the slashnet network (
"is permitted to"
May not
"is not permitted to"
A blog post published to the BlogNomic weblog at
Private Message
A message sent via Blognomic’s Private Messages system at
Quorum of a subset of Explorers is half the number of Explorers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Explorers it is referring to, it is referring to a Quorum of all Explorers.
If used in a context of a Votable Matter, the word “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
Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.
"is required to"
"is recommended that"
Sibling Rule
Two rules are “siblings” of each other if they are both direct subrules of the same rule.
The BlogNomic Slack is located at Explorers 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.
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.
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.
Table of Contents
The directory of section headings that is generated by the MediaWiki software for most pages in the wiki.
Table of Contents.
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 shall represent a Vote FOR, an X shall represent a Vote AGAINST, an IMP shall represent a Vote of DEFERENTIAL, and an Imperial Seal shall represent the Imperial Veto.
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 Explorer 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 Explorer per week.
The BlogNomic Wiki at

Gamestate Tracking

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at Any Explorer may post to the blog at any time, but may only make official posts to the blog when the Ruleset allows it. Posts following the format specified by a rule are considered official posts. Any single official post cannot be of two different types of official post unless a rule explicitly states otherwise.

An official post may be altered or removed by its author if it is less than six hours old and either no Explorer has commented on it or all comments on it contain no voting icons; 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 two exceptions: Firstly, 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. Secondly, if a post by an Explorer who has been an Explorer for fewer than seven days contains the word “Proposal” in its title, but is not a Proposal, and if it has been posted for less than an hour, then any admin may change it to be in the Proposal category.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at Any Explorer may update any Explorer's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. For gamestate which is tracked in a specific place (such as the GNDT or a wiki page), any alteration of that gamestate as a result of an Explorer’s action is (and can only be) applied by editing that data in that place. One GNDT or wiki update may contain one or more alterations, or one alteration may be split over multiple updates, as long as it is clear what is happening and the alterations 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 Explorer may correct the GNDT to comply with the Gamestate.

If an Explorer 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, Explorers are encouraged to raise a Call for Judgement instead. Explorers 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 DICEN 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 Explorer 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.


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 Explorers to transfer a numeric value only allows them to transfer that value from themselves to another Explorer (of their choice unless otherwise stated).
  • An Explorer 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 selection is explicitly specified as being “secretly” random, the Explorer making this determination may do so using a private method of their choosing, instead of the GNDT.
  • 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)
  • DICEN cannot be rolled in the GNDT if N is 22 or more digits long.

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


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


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


  • Within the ruleset, a word only refers to the name of an Explorer if it is explicitly stated that it refers to an Explorer's name.


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