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 144

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

Players 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 Player may update it to do so.

Players

Any human may apply to join BlogNomic (if they are not already a Player) 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 Player. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Player.

A Player may cease to be a Player at any time by posting an entry to the BlogNomic weblog requesting such an action. A human who has ceased to be a Player in this way may not become a Player again within the following two weeks. 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.

Idle Players

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

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

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

An Admin may render a Player Idle if that Player has asked to become Idle in an entry or comment from the past four days, 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, but should announce it in a post or comment when they do so. An Admin may Unidle a Player if that Player 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 Player 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 Player, known as the Emperor. If there is no Emperor, the Dynasty is a Metadynasty.

Votable Matters

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

Each Player 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 Player’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-Player never has a Vote, even if they were a Player 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.

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

Special Proposal Voting

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

If a Player other than the Emperor casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor'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 Players 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 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 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 Player (other than the Emperor) 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”, “Votable Matters”, “Calls for Judgement”, “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 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 Emperor 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 Players 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 Player who made the DoV as its Emperor. 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 Emperor makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Emperor's chosen theme for the new Dynasty, and may optionally specify that the terms Player and Emperor 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 Player 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 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 “Votable Matters,” “Gamestate Tracking” and “Call for Judgement”.

Dynastic Rules

Atomic Actions

When a Player 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 Player performing an Atomic Action should perform its steps as quickly as they are able.

If an hour has passed since a Player began an Atomic Action, but they have not completed it, all its steps are considered illegal and may be reverted by any Player, and the Atomic Action is not considered to have been performed.

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.

The Twelve Arcs

There are six Days, comprising a Sun Arc and a Moon Arc. Each Arc further comprises twelve Hours.

Each of the one hundred and forty four Hours can be Broken, Focused, Restored, or Lost. The initial state of all Hours is Broken. Each Hour may have a Predecessor as its Guardian: this is tracked on the wiki page by describing the Hour as “Broken by X” (or Focused or Restored by X), where X is the Guardian’s name.

Each Hour corresponds to a dynasty, tracked by having the Hour’s name on the State of the Arcs wiki page link to that dynasty’s wiki page. Each Hour may also describe a Moment. One may speak of the Hour of a particular dynasty or the dynasty of a particular Hour with the obvious meaning.

This information is tracked in the “State of the Arcs” wiki page.

All references to “days” and “hours” in the Core Rules and Appendix are considered to refer to periods of time in the real world, rather than those defined by this rule. If a dynastic rule refers to a “Real Day” or “Real Hour”, it refers to a period of time in the real world rather than the Days and Hours of this rule.

Escapement

Each Player, including the Emperor, has a number of Ticks; this is tracked in the GNDT. A Player who has never had their Ticks set before has one Tick.

Each Player has a number of Quartzes, tracked in the GNDT and defaulting to zero.

If the total Ticks among all Players other than the Emperor is greater than the Emperor’s Ticks, and the current date is after November 11th 2016, then: Time is Up, and the Timekeeper has achieved victory.

Timekeeper

One Player (or idle Player) may be the Timekeeper, and their identity is tracked privately by the Emperor. The Timekeeper cannot declare victory unless Time is Up. The Timekeeper should conceal the fact that they are the Timekeeper and lie about it if asked.

If there is no Timekeeper, then the Emperor may select any Player (or idle Player) other than themselves to be the Timekeeper, and inform them of this fact. The Emperor should only select an idle Player in this way if they have good reason to believe that Player will unidle during the dynasty.

Restoration of the Hours

Any player may, as a daily action, "restore an Hour," which is an Atomic Action with the following steps:

  1. The player increases their Ticks by one.
  2. The player posts a Story Post identifying a broken Hour, and including one sentence describing a significant or trivial game action that occurred during the dynasty of that Hour. Such a sentence should include a link to a blog post or wiki edit where that action occurred, if relevant.
  3. The Player marks the Hour of that dynasty as Focused, marks themselves as its Guardian, and adds the sentence as its Moment.
  4. If the Sentence named only a single Predecessor, and that Predecessor is named in the Moments of no other Hours, and that Predecessor is not the Player taking this action, then the Player taking this action may award themselves 1 Quartz. If no Quartz is awarded in this step, they must make a GNDT comment of “Done focusing”.
  5. If the chosen Hour is the only Focused Hour in that Day, or if the Chosen Hour is directly before or after a Restored Hour, then the Player taking this action may award themselves 1 Quartz. If no Quartz is awarded in this step, they must make a GNDT comment of “Done focusing”.

If an Hour is Focused and all Predecessors described in its Moment are Vouched For, then any Player may change that Hour from Focused to Restored and increase the Hour’s Guardian’s Quartzes by one and increase the Emperor’s Ticks by one. (A Predecessor is any human who has ever played BlogNomic. A Predecessor is Vouched For if they have been a Player during the current dynasty, or if they have made a comment on an official post that was posted during the current dynasty, or if they have posted a public message anywhere on the internet during the current dynasty which contains the word “BlogNomic”.)

Time Warp Victory

If a group of three Players have a total of at least 48 Quartzes between them, and if two of those Players have nominated the third as that group’s Governor by making a blog post or comment to that effect, then that Governor has achieved victory. This is known as a Time Warp victory.

When a theme is chosen for a new dynasty as a result of a Time Warp victory, it must be the theme of a Restored Hour.

Remembering Hours

If an Hour has been Focused but not Restored, any Player may Summon Memories of it in the hopes that it will be Restored. Summoning Memories is an Atomic Action, in which the Player pays 1 Quartz via the GNDT, then leaves a comment on the Story Post for the Focused Hour in question that includes the phrase "I remember." A Player may only Summon Memories of any given Hour once.

Should an Hour for which a Player has Summoned Memories become Restored, that Player may—only once per any given Hour, and within 24 Real Hours of it becoming Restored—award themselves 3 Quartz.

If a Player has Summoned Memories of an Hour, that Hour cannot be Restored until the most recent Summoned Memories of it are more than 24 Real Hours old. A Player may not Summon Memories on an Hour if there is a Story Post that Focused it which is more than 168 Real Hours old.

Destruction of the Hours

The Emperor may, as a Daily Action, “destroy an Hour,” which is an Atomic Action with the following steps:

  1. The Emperor decreases their Ticks by one.
  2. The Emperor posts a Story Post identifying a broken Hour, and including one sentence naming a Predecessor who idled out during the dynasty of that Hour.
  3. The Emperor marks the Hour of that dynasty as Lost, marks themselves as its Guardian, and adds the sentence as its Moment.
  4. The Emperor increases each other player’s Quartz by one.

Crystal Victory

The number of Settings in a Day are equal to the number of Broken and Lost Hours it has.

If a Player has a number of Quartzes equal to or greater than the number of Settings in a Day, and if that Player is the Guardian of more Hours in that Day than any other Player, then that Player has achieved victory. This is known as a Crystal Victory.

Whiling Away the Hours

As a Daily Action, the Emperor may make the GNDT comment “Whiling away: DICE144” and thereby While Away an Hour. The outcome of such a die roll corresponds to an Hour, as ordered on the [State of the Arcs] wiki page.

  • If the Hour so rolled is Broken, the Emperor’s Ticks decrease by one.
  • If the Hour so rolled is Lost, the Emperor’s Ticks are decreased by twelve, and each other Player gains one Quartz.
  • If the Hour so rolled is Focused, the Ticks of each player besides the Emperor and the Guardian of that Hour increase by one.
  • If the Hour so rolled is Restored, the Guardian of that Hour gains one Quartz, and the Emperor’s Ticks increase by one.


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 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 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 ten hours.
Daily Communal Action
A Daily Communal Action is a Daily Action that can only be performed by one Player 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 Player’s Effective Vote Comment with respect to a given Votable Matter means that Player’s Comment to that Votable Matter, if any, that contains that Player’s Vote on that Votable Matter.
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. 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 (irc.slashnet.org).
May
"is permitted to"
May not
"is not permitted to"
Post
A blog post published to the BlogNomic weblog at blognomic.com
Private Message
A message sent via Blognomic’s Private Messages system 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 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
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. Players 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 Player 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 Player 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. 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. Any single official post cannot be of two different types of official post unless a rule explicitly states otherwise.

If no Player 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. 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 Judgement instead. Players 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 Player 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 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. 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 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 Player if it is explicitly stated that it refers to a Player's name.

Prioritisation

  • 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 “Players may Kick each other” and “Players may not kick each other on Tuesdays” exist, and it is Tuesday, Players may not Kick each other.)
  4. If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Players may Punch a Spaceman on Friday” and “Players may not Punch Spacemen on Friday”, then Players may not Punch Spacemen on Friday.)