Ruleset and Gamestate
This is the Ruleset for BlogNomic; all Orcs 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.
Orcs 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”.
Any human may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post making clear their wish to be a Orc. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become an Orc.
An Orc may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. An Orc may not rejoin the game within two weeks after having left. An Orc may only change their name as a result of a proposal approving the change.
Some Orcs are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Orcs 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 Orcs 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”, “Orcs”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Orcs are not counted as Orcs.
If a Proposal contains a provision that targets a specifically named Idle Orc, then that Idle Orc is considered to be Unidle solely for the purposes of enacting that specific provision
When an Orc 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 Orc Idled in a different dynasty), the Orc is given the default value for new Orc, if such a value exists.
An Admin may render an Orc Idle if that Orc has asked to become Idle in an entry or comment from the past four days, or if that Orc 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 Orc if that Orc 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 Orc 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 Orc, known as the Overlord. If there is no Overlord, the Dynasty is a Metadynasty.
A Votable Matter is a post which Orcs may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.
Each Orc 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 Orc’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-Orc never has a Vote, even if they were an Orc previously and had cast a valid Vote.
Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.
Whenever an Admin resolves a Votable Matter, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).
This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.
Any Orc may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Orc already has 2 Proposals pending, or has already made 3 Proposals that day).
Special Proposal Voting
When an Orc 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 Overlord may use VETO as a voting icon to cast a Vote on a proposal; when the Overlord casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Overlord later changes their Vote.
If an Orc other than the Overlord casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Overlord. When the Overlord has a valid Vote other than VETO on a Proposal, then all votes of DEFERENTIAL are instead considered to be valid and the same as the Overlord'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 Orcs 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 Orcs actively disagree as to the interpretation of the Ruleset, or if an Orc feels that an aspect of the game needs urgent attention, then any Orc 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 Orc (other than the Overlord) 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 “Orcs”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.
Every Orc 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 Overlord 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 Orcs 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 Orc who made the DoV as its Overlord. That Orc may pass this role to another Orc at this point by making a post to that effect, if they wish. The Hiatus continues until the new Overlord makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Overlord's chosen theme for the new Dynasty, and may optionally specify that the terms Orc and Overlord 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 Orc 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.
The following are BlogNomic’s rules of fair play. If any of these rules are found to have been broken, or if an Orc'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 Orc within BlogNomic.
- An Orc 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 Orc should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
- An Orc should not edit their own blog comments once posted, nor those of any other Orc.
- An Orc should not edit the "Entry Date" field of a blog post.
- An Orc should not make a DoV primarily to delay the game by putting it into Hiatus.
- An Orc should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).
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”.
An Orc (The Attacker) may Attack a non-Dead Creature by expending one AP and then performing the following in order:
- Determine X by the following formula, Y+Z=X where Y is the result of DICE20 being rolled in the GNDT and Z is the Attacker’s dexterity. If X is less than the Creatures dexterity no further steps are performed.
- If the Creature is Stunned, it ceases to be Stunned.
- The Orc decreases the Creature’s Health by X+Y where X is the result of DICE10 being rolled in the GNDT and Y is the Attackers’s Strength
- Decrease the Attacker’s Health by the Creatures strength.
- If the Creature is Dead, then the attacker may remove all Loot from the Creature’s sub-rule and distribute it as he or she wishes amongst the Orcs who have Wounded that Creature, distributing no more than one Item per Orc in this way, and distributing as much of the Loot as is possible. (Any Loot which cannot be distributed in this way is returned to the Creature, with the exception of Potions, which are lost.)
Orcs and Creatures have numerical Stats with define their physical attributes. The Stats are Strength, Dexterity, and Constitution. Stats are tracked in the GNDT. Orcs stats default to 2.
An Orc may Train a Stat by spending 1 AP and increasing that Stat by 1, unless after doing so the Stat would have more than twice the value of any other of that Orc’s Stats.
Orcs and Creatures have a numerical amount of Health which may be a negative number. An Orc may not have more health than they have Constitution. If an action would give an Orc more health than they have Constitution, it is instead set to their Constitution. An Orc is considered to be Mortally Wounded if their health is equal to or less than 0. If an Orc is Mortally Wounded they may not perform any action defined by the dynastic rules other than Rest. An Orc may Rest by spending 1 AP and then Increasing their Health by X where X is the result of DICEZ being rolled in the GNDT where Z is 1/2 of their Constitution rounded up.
A creature or Orc is said to take damage when that creature or Orc’s health is reduced.
A creature or Orc is said to deal damage when that creature or Orc reduces the health of a creature or Orc.
Orcs have a numerical amount of Action Points or AP which is tracked in the GNDT and defaults to 3. As a Daily Communal Action, an Orc may increase each Fatigued Orc’s AP by 1. An Orc is Fatigued if their AP is less than the total of their Strength and Dexterity, and also less than 10.
There are a number of Creatures who roam these lands, challenging even the most skilled of warriors. Creatures are listed as sub-rules to this rule. Each Creature has Stats and Loot. If an Orc causes a Creature to gain or lose Health, they should update that Creature’s sub-rule to reflect the change. When an Orc causes a Creature to lose Health, they may Wound it by updating that Creature’s sub-rule to include the sentence “Wounded by (name).”, where “(name)” is the Orc’s own name.
If (and only if) a Creature has a Health of zero or below, then that creature is Dead.
Creatures may have one or more Statuses, tracked in their rules as a sentence of the form “(Name) is (Status)”, where “(Name)” is the Creature’s Name and “(Status)” is a single-word Status. If a Creature “becomes” something, it gains that something as a Status (unless it already has that Status). Some Statuses have specific effects, as follows:
- Stunned. If a Creature is Stunned, its Dexterity is considered to be halved (rounding up) for all rules outside of its own.
That Pesky Dragon
That Pesky Dragons’s stats are: Strength-5 Dexterity-25 Constitution-100. Its loot is The Golden Crown. It’s Health is 100. The Dragon has a Ranged Attack.
That Angry Scorpion
That Angry Scorpion’s stats are: Strength-1 Dexterity-15 Constitution-10. Its loot is a Poison Barb and a Potion of Strength. Its Health is 20.
When an Orc’s Health is decreased as a result of that Orc Attacking That Angry Scorpion, that Orc loses 1 Strength (to a minimum of zero).
Training Dummy’s stats are: Strength-1 Dexterity-5 Constitution-1. Its loot is. Its Health is -9.
This is the list of Orcs who have beaten Training Dummy: Kevan, Brendan, IceFromHell, GenericPerson, Clucky, Quirck.
If an Orc reduces Training Dummy’s Health from above 0 to 0 or below, they must add their own name to the list of Orcs who have beaten Training Dummy above. If an Orc’s name appears in the list of Orcs who have beaten Training Dummy, that Orc may not Attack Training Dummy.
If Training Dummy is Dead and has no Loot, any Orc may set the Dummy’s Health to 1 and its Loot to a Potion of Dexterity.
Wounded by Brendan. Wounded by IceFromHell. Wounded by GenericPerson. Wounded by Clucky. Wounded by Quirck.
That Grimy Kobold
That Grimy Kobold’s stats are: Strength-1 Dexterity-15 Constitution-12. Its loot is -. Its Health is 0.
Wounded by Kevan. Wounded by Clucky.
When an Orc deals damage to That Grimy Kobold, that damage is reduced by 1 (to a minimum of 1).
That Greedy Leprechaun
That Greedy Leprechaun’s stats are: Strength-1 Dexterity-20 Constitution-3. Its loot is two Bags of Gold. Its Health is 20.
When an Orc who has more than zero Resources is dealt damage by That Greedy Leprechaun, the Orc loses all of their Resources and the Leprechaun gains one Bag of Gold for its Loot.
Orcs may hold any number of items. Items have an effect that may be activated by the Orc who holds it. An Orc’s Items are tracked in the GNDT. The existent items and their affects are listed as sub-rules to this rule. If an Item has a Crafting Cost, an Orc may spend that Cost to add one instance of that Item to the Items held by that Orc.
The Golden Crown
Affect: The Orc who holds The Golden Crown has Achieved Victory.
Crafting Cost: 1 AP and 150 Resources.
Potion of Strength
Affect: An Orc who holds a Potion of Strength may cease holding it to gain 3 Strength.
Potion of Dexterity
Affect: An Orc who holds a Potion of Dexterity may cease holding it to gain 3 Dexterity.
Potion of Toughness
Affect: An Orc who holds a Potion of Toughness may cease holding it to gain 3 Constitution.
Affect: When an Orc who holds a Poison Barb causes a Creature to lose Health, they may cease holding the Poison Barb to decrease that Creature’s Health by a further 10.
Affect: while an Orc is holding this Item, when they are required to use their strength value, this value is considered to be their current strength plus 2.
This Item is a Weapon.
Crafting Cost: 1 AP and 5 Resources.
Affect: When a Creature deals damage to an Orc who holds a Wooden Shield, that damage is reduced by 1 (to a minimum of 1).
Affect: If a Creature is damaged by an Orc holding this item, that Creature becomes Stunned.
This item is a Weapon.
Crafting Cost: 1 AP and 10 Resources.
Bag of Gold
Affect: An Orc who holds a Bag of Gold may cease holding it to gain DICE10 Resources.
Affect: Holder’s Strength is considered to be increased by 4, for the purposes of all other rules.
This Item is a Weapon. Crafting Cost: 2 AP and 8 Resources.
Affect: Holder’s Dexterity is considered to be increased by 2, for the purposes of all other rules.
This Item is a Weapon. Crafting Cost: 1 AP and 5 Resources.
Affect: An Orc with a Long Bow is considered to have a Strength of zero for the purposes of the rule “Attacking”, and Creatures cannot deal damage to them unless they have a Ranged Attack.
This Item is a Weapon. Crafting Cost: 2 AP and 10 Resources.
Potion of Healing
Affect: An Orc who holds a Potion of Healing may cease holding it to set their Health to their Constitution.
Crafting Cost: 1 AP and 3 Resources.
Orcs have a numerical amount of Resources which is tracked in the GNDT and defaults to 0. An orc may spend 1 AP to gain an amount of Resources equal to DICEX, where X is that Orc’s Strength plus one.
When an Orc is required to take the result of a DICEX roll in the GNDT, they may instead choose to take a fixed vale of X/2 (rounding down) as the result of that roll.
Bring Out Your Dead!
An Orc who is holding no Items may Plunder the Corpse of a Dead Creature, by moving an Item from that Creature’s Loot to their own possession.
Orcs can only hold one Weapon at any given time. If an action would make an orc hold more than one weapon, that orc may choose one to keep and discard the rest.
As a Daily Action, an Orc may cease holding an item and place it in another Orc’s Inventory. No Orc may donate a Weapon in this way if the Orc they would give it to already holds a Weapon.
At any time, an Orc may spend X Resources to give another Orc X-1 Resources.
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 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 Orcs.
- Daily Action
- If a game action is a Daily Action, each Orc 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 Orc 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 Orc’s Effective Vote Comment with respect to a given Votable Matter means that Orc’s Comment to that Votable Matter, if any, that contains that Orc’s Vote on that Votable Matter.
- Flavour Text
- When posting a blog entry, an Orc 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, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.
- IRC Channel
- The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).
- "is permitted to"
- May not
- "is not permitted to"
- 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 of a subset of Orcs is half the number of Orcs in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Orcs it is referring to, it is referring to a Quorum of all Orcs.
- If used in a context of a Votable Matter, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words
- 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 blognomic.slack.com. Orcs 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.
- 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.
- 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 Orc 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 Orc per week.
- The BlogNomic Wiki at http://wiki.blognomic.com
Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at http://blognomic.com. Any Orc 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 Orc 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 Orc may update any Orc'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 Orc may correct the GNDT to comply with the Gamestate.
If an Orc 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, Orcs are encouraged to raise a Call for Judgement instead. Orcs shall be assigned a password for the GNDT when they join the Nomic.
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 Orc 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 Orcs to transfer a numeric value only allows them to transfer that value from themselves to another Orc (of their choice unless otherwise stated).
- An Orc 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, Orc 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 Orc if it is explicitly stated that it refers to an Orc's name.
- If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
- The Appendix has precedence over any Rule;
- A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
- If both contradicting parts are Core Rules, or if both of them are Dynastic Rules, the part with more limited scope applies. (e.g. if the rules “Orcs may Kick each other” and “Orcs may not kick each other on Tuesdays” exist, and it is Tuesday, Orcs may not Kick each other.)
- If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Orcs may Punch a Spaceman on Friday” and “Orcs may not Punch Spacemen on Friday”, then Orcs may not Punch Spacemen on Friday.)