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.

Ruleset 89

From BlogNomic Wiki
Jump to: navigation, search

Core Rules

Ruleset and Gamestate

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

Players

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

A Player may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Player may only change their name as a result of a proposal approving the change.

Some Players are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Players 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 Players 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 Players are not counted as Players. Admins may render a Player Idle if that Player has asked to become Idle or if that Player 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 Player at their request, and Idle Admins may de-idle themselves at any time, unless the idle Player in question asked to become (or rendered themselves) Idle within the previous 4 days, and within the current dynasty. The Player’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 Players receive, if such a value exists.

Proposals

Any Player may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Player 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 Player 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 Player is the Chairman).

If the Player who authored a Votable Matter has not cast a Vote on it, their Vote is counted as FOR. If a Player uses more than one Voting Icon in comments on a Votable Matter, their Vote is the last voting icon they use. If a Player leaves the game or goes Idle, their Vote is no longer valid. If a Player 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 Chairman. The Vote will count as the same as the Chairman’s Vote. If the Chairman 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 Chairman and counts as an explicit Vote of abstention. If there is no Chairman, or the Vote is made by the proposal’s author on their own proposal and the Chairman 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 Chairman 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 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 Player who proposed it has Voted AGAINST it.
  • The Chairman 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 Chairman 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 Chairman 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 Players actively disagree as to the interpretation of the Ruleset, or if a Player feels that an aspect of the game needs urgent attention, then any Player 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 Players 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 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, Calls for Judgment, and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at http://blognomic.com. Any Player 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.

If no Player 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. Any Player may update any Player'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 Player may correct the GNDT to comply with the Gamestate.

If a Player 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, Players are encouraged to raise a Call for Judgment instead. Players 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 Player, known as the Chairman.

The Chairman may Vote to VETO any Proposal.

Victory and Ascension

If a Player (other than the Chairman) 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 “Players”, “Voting”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

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

Dynastic Rules

Leaping

If a player’s piece is in a station that is adjacent to another player’s piece, and they move by any legal means to the station on the same line that is adjacent to the same player’s piece on the other side, without that player having moved in the interim, then they have successfully leaped that player. A player may only leap another player as a weekly action; if a player cannot legally leap another player due to this restriction then they may undertake the actions that would normally constitute a leap, provided that they are otherwise legal, but that action is not considered to have been a leap.

Whenever a player leaps another player, they may remove one letter of their choice from that player’s trail.

Whenever a player moves their piece to a station that is at the end of a single line (i.e. any station that has only one other station directly adjacent to it - for example, Amersham or Morden, but not Ealing Broadway or Barking), they may add an asterisk (*) to their trail immediately before the letter that they would add for that station. If a player has an asterisk in their trail and are leaped then the leaping player must remove the asterisk instead of removing any other letter. An asterisk can be ignored for the purposes of making letter combinations in a trail (e.g. UNL*OCK would have the same effect as UNLOCK).

Board and Pieces

Mornington Crescent is a board game played on the London Underground map as it exists at blognomic.com/images/tubemap.gif. The Board consists of a number of Stations situated on a number of Lines.

A Station is a named location on the Board which is marked by either a notch on a single line, notches on several lines, a white circle, multiple white circles which are joined, an accessibility symbol, multiple accessibility symbols which are joined, or one or more accessibility symbols joined to one or more white circles.

All Stations are either Interchange or Standard, but not both. Any Station marked with one or more white circles is an Interchange Station. Any Station marked with one or more notches is a Standard Station. A Station marked by one or more accessibility symbols is Interchange if it is on multiple lines, or has a British Rail logo next to its name. Otherwise, Stations marked by accessibility symbols are Standard.

Stations which are marked by an accessibility symbol are Disabled Access. The Non-Disabled Access Interchange Station which is labeled both “Bank” and “Monument” is named Bank. There is no station named “Monument”.

Each Player has a Piece, the location of which is tracked in the GNDT as “Location”. A Piece’s location may either be “Off the Board” (notated as “-”), or at a single Station. If a Piece is at a Station, that Station’s name in the GNDT should be followed by its Line Code, in brackets. A Station’s Line Code is an alphabetical list of the first letters of each Line it is situated on (except that the Central Line is notated as “T”, the London Overground as “O” and the DLR as “R”). For example: “Barbican (CHM)”.

All Players’ Pieces begin located Off the Board.

The Washington DC Metro map (washingtondcstay.com/sitebuildercontent/sitebuilderpictures/Metromap.gif) is gamestate and is considered part of the Board, except that no Station on the Washington DC Metro map is an eligible starting location for any Player’s Piece nor may a Player’s Piece be moved to a Station on the Washington DC Metro map by operation of a rule that permits an Off The Board Piece to be moved to a Station. The Lines on the Washington DC Metro map may be referred to by the first letter of the color of that line, in lowercase (i.e., r for Red Line; o for Orange Line; b for Blue Line, g for Green Line and y for Yellow Line).

Mornington Crescent

If a single Player’s Piece is located at Mornington Crescent, that Player has achieved victory.

Tickets

Each Player has a value “Tickets”, a non-negative integer tracked in the GNDT. All Players begin with 0 Tickets. As a weekly action, a Player may set the number of Tickets he owns to 7.

Location Hopping

As a weekly action, a player may Hop by rolling 2DICE7 in the gndt. After obtaining the result, they may immediately spend any number of Tickets to increase or decrease the result by the same amount, as long as this does not cause the result to go below 2 or above 14. After this step, they must move their Piece to a Station of their Choice on the Line that corresponds to the (modified) result of the roll on the list in this rule. If they do not perform this step within one hour of making the dice roll, any Player may do it for them, but no Tickets may be spent in this case, and no Hop may result in a Piece moving more than once.

The results of the dice rolls correspond to the lines as follows:

  • 2 - District
  • 3 - Piccadilly
  • 4 - Hammersmith & City
  • 5 - Jubilee
  • 6 - Circle
  • 7 - DLR
  • 8 - Waterloo & City
  • 9 - Metropolitan
  • 10 - Victoria
  • 11 - Central
  • 12 - Bakerloo
  • 13 - London Overground
  • 14 - Northern

Movement

As a daily action, a Player may make either of the following moves:-

  • If their Piece is Off the Board, they may move their Piece to any Unoccupied Station other than Mornington Crescent.
  • If their Piece is at a Station (the “Origin”), they may move their Piece to any Unoccupied Station which shares one or more Lines with that Origin.
  • If their piece is on or off the board, they may move to any Unoccupied Station they have listed in their photo album by spending tickets equal to the number of lines the station is situated on.
  • If their Piece is located at Tower Hill or Tower Gateway, they may move their Piece to Tower Hill or Tower Gateway.
  • If their Piece is located at Bow Road or Bow Church, they may move their Piece to Bow Road or Bow Church.
  • If their Piece is located at South Kenton, they may move their Piece to Northwick Park. (this is the Top Secret Passage, and is one-way)
  • They may move their Piece to the current location of their Piece.

A Station is Unoccupied if there are no Pieces present at that Station.

Oddities

Stations may have Oddities. An Oddity is a particular rule related to that Station. All the Odd Stations are listed in Alphabetical Order in the wiki page called Check before you travel (that is part of the gamestate) as well as their Oddities.

Any Station with one or more Oddities or a pending Odd Proposal related to it shall be considered Odd.

A Normal (not Odd) Station may become Odd only by Odd Proposals. Odd Proposal are posted in the category “Proposal”, start with the word “Odd:” and do not count as Proposals for the purpose of the first sentence in rule 1.3 “Proposals”. The only effect of an Odd Proposal shall be adding an Oddity to a Normal Station. Any Player may only write Odd Proposals related to the Normal Station they are in, if any. That Station shall be named in the title of the Proposal.

Notwithstanding anything to the contrary in the Ruleset, if a Player Votes against their own Odd Proposal or the Chairman votes to VETO an Odd Proposal then that Odd Proposal may be failed at any time even if it is not then the oldest pending Proposal. If a Player makes an Odd Proposal and that Odd Proposal is failed while the Player’s Piece is still located at the Station to which that Odd Proposal related, then in addition to any other restrictions that may be applicable, that Player may not make any more Odd Proposals until that Player’s Piece moves.

Sightseeing

A Player’s Photo Album is a set of Stations. At any time, a Player may add the Station at which their Piece is located to their Photo Album, unless it is already there.

Players’ Photo Albums are tracked on the wiki page Photo Albums. Initially, all Players’ Photo Albums are empty.

Trails

Each player has a Trail, which is tracked in the GNDT. A player’s trail is a sequence of up to seven letters, with each letter being the first letter of a station that player has recently visited. Every a player’s moves their piece to a new station, that player must immediately add the first letter of the new station to the end of their trail; similarly, if a player ever moves another player’s piece to a new station, they must update that player’s trail in the same way. If this would cause the trail to contain more than seven letters, the oldest letter is removed.

When a trail contains a certain combination of letters in order, the player who possesses it may undertake certain specified actions. When such an action is undertaken the letters used to undertake it are removed from the trail. These are detailed below:

  • BOAT. If a player has a trail that contains the word BOAT, then they may immediately move their piece to any station that has a boat next to its name on the map.
  • UNLOCK. If a player has a trail that includes the word UNLOCK, they may cause one locked station to no longer be locked. To do this they must make a post to the blog stating that the station has become unlocked; the station is considered to be unlocked from the moment that the post is visible on the blog, but an admin should change the ruleset or gamestate to reflect this change as soon as is practically possible.
  • RELOCK. If a player has a trail that includes the word RELOCK, they my cause one unlocked station to no longer be unlocked. To do this they must make a post to the blog stating that the station has become locked; the station is considered to be locked from the moment that the post is visible on the blog, but an admin should change the ruleset or gamestate to reflect this change as soon as is practically possible.
  • LOCK. If a player has a trail that includes the word LOCK, they may cause exactly one station that is not locked to become locked. To do this they must make a post to the blog stating that the station has become locked; the station is considered to be locked from the moment that the post is visible on the blog, and an admin should change the ruleset or gamestate to reflect this change as soon as is practically possible.

If a Player’s trail ever includes the full name of a station then the player may remove those letters from their trail and move to that station. This does not count as a daily move.

Locked Stations

A player may never place their piece on a locked station. If a player’s move would require them to do so then they must instead place their piece Off the Board.

The following stations are locked:

  • Oxford Circus
  • Kings Cross St. Pancras
  • Embankment
  • Boston Manor

Any station which is not Locked is considered Open, and may also be referred to as Unlocked


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 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 Players.
Daily Action
If a game action is a Daily Action, each Player 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 Player's Effective Vote Comment with respect to a given Proposal means that Player’s Comment to that Proposal (if any) that contains that Player’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 Player 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 blognomic.com
Quorum
Quorum of a subset of Players is half the number of Players in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Players it is referring to, it is referring to a Quorum of all Players.
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 Player 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.
  • 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 Players to transfer a numeric value only allows them to transfer that value from themselves to another Player (of their choice unless otherwise stated).
  • A Player 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 Players, or for existing Players 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 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 Player if it is explicitly stated that it refers to a Player's name.