Ruleset and Gamestate
This is the Ruleset for BlogNomic; all Shuttles 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.
Shuttles 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 Shuttle. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Shuttle.
A Shuttle may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Shuttle may not rejoin the game within two weeks after having left. A Shuttle may only change their name as a result of a proposal approving the change.
Some Shuttles are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Shuttles 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 Shuttles 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”, “Shuttles”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Shuttles are not counted as Shuttles.
If a Proposal contains a provision that targets a specifically named Idle Shuttle, then that Idle Shuttle is considered to be Unidle solely for the purposes of enacting that specific provision
When a Shuttle 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 Shuttle Idled in a different dynasty), the Shuttle is given the default value for new Shuttle, if such a value exists.
An Admin may render a Shuttle Idle if that Shuttle has asked to become Idle in an entry or comment from the past four days, or if that Shuttle 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 Shuttle if that Shuttle 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 Shuttle who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.
Admins who are unidling themselves should, in their first EVC following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.
BlogNomic is divided into a number of Dynasties. Each Dynasty may be headed by a single Shuttle, known as the Traffic Warden. If there is no Traffic Warden, the Dynasty is a Metadynasty.
A Votable Matter is a post which Shuttles may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.
Each Shuttle 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 Shuttle’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-Shuttle never has a Vote, even if they were a Shuttle 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 Shuttle may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Shuttle already has 2 Proposals pending, or has already made 3 Proposals that day).
Special Proposal Voting
When a Shuttle 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 Traffic Warden may use VETO as a voting icon to cast a Vote on a proposal; when the Traffic Warden casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Traffic Warden later changes their Vote.
If a Shuttle other than the Traffic Warden casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Traffic Warden. When the Traffic Warden 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 Traffic Warden'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 Shuttles 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 Shuttles actively disagree as to the interpretation of the Ruleset, or if a Shuttle feels that an aspect of the game needs urgent attention, then any Shuttle 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 Shuttle (other than the Traffic Warden) 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 “Shuttles”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.
Every Shuttle 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 Traffic Warden 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 Shuttles 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 Shuttle who made the DoV as its Traffic Warden. That Shuttle may pass this role to another Shuttle at this point by making a post to that effect, if they wish. The Hiatus continues until the new Traffic Warden makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Traffic Warden's chosen theme for the new Dynasty, and may optionally specify that the terms Shuttle and Traffic Warden 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 Shuttle 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 a Shuttle'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 Shuttle within BlogNomic.
- A Shuttle 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 Shuttle should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
- A Shuttle should not edit their own blog comments once posted, nor those of any other Shuttle.
- A Shuttle should not edit the "Entry Date" field of a blog post.
- A Shuttle should not make a DoV primarily to delay the game by putting it into Hiatus.
- A Shuttle 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”.
A Proxy is a non-Shuttle entity designated as such by the rules. Each Proxy has its own GNDT row. Proxies are considered to be Shuttles for the purpose of other Dynastic Rules, except where they explicitly refer to non-Proxy Shuttles.
If a rule allows a Shuttle to cause a Proxy to act, that Shuttle can update the gamestate on behalf of that Proxy as allowed by the rules. If a Shuttle needs to make comments or GNDT updates on behalf of a Proxy, they must start the comment with “PROXY (X):” where (X) is the name of the Proxy. Proxies cannot make blog posts.
Derelicts are a type of Proxy. Any Shuttle with the same Orbit as a Derelict may, as a Knock-On Action, cause that Derelict to take a GNDT action.
There are three Derelicts: MC Geran, MC Damanor and MC Keitalia.
Each Shuttle has an amount of Fuel, tracked in the "Fuel" column of the GNDT. New Shuttles start with 2 Fuel or the amount of Fuel the Traffic Warden has, whichever is higher.
If no Shuttle has done so yet this week, any Shuttle may Order Fuel. When they do, each Shuttle with less than 15 Fuel gains 3 Fuel. The Traffic Warden gains the 3 Fuel even if it has 15 or more Fuel. Each Shuttle may, as a separate weekly action, gain 4 Fuel if they are the author of a Proposal that became enacted in the last 7 days but after the last time they took this action (or after the start of the dynasty if they have never taken this acton).
There are four Moons: Io, Europa, Ganymede and Callisto. Each Moon has an Orbital Size: 5 for Io, 10 for Europa, 20 for Ganymede and 1 for Callisto.
Each Shuttle has an Orbit, tracked in the GNDT. An Orbit is a Moon (tracked as the first letter of the Moon's name) followed by an Orbit Number from 1 to the Moon's Orbital Size. New Shuttles start in Orbit G20.
Orbits with the same Moon are equivalent modulo the Moon’s Orbital Size; that is, if an Orbit would have an Orbit Number larger than its Moon’s Orbital Size or less than 1, instead divide its Orbit Number by the Orbital Size and set the Orbital Number to the remainder, or to the Orbital Size if the remainder is 0.
Only the Traffic Warden may have orbit C1.
Each Shuttle has a Bay, which may contain zero or more tonnes of each Substance which a rule allows to be added to a Shuttle Bay. A Shuttle’s Bay contents are tracked in the “Bay” column of the GNDT, in a suggested format of “1 Sulphur, 2 Ice”. Shuttles default to having an empty Bay.
Space Elevators are a type of Structure. If a Shuttle's Orbit contains a Space Elevator, it may spend 1 Fuel to take the following action corresponding to its Orbit’s Moon:
- Io: Mine Sulphur, the Shuttle adding 1 tonne of Sulphur to its Bay.
- Europa: Mine Ice, the Shuttle adding 1 tonne of Ice to its Bay.
- Ganymede: Mine Iron or Ice, the Shuttle adding 1 tonne of the chosen Substance to its Bay.
- Callisto: If the Shuttle has at least 2 tonnes of Sulphur, 2 tonnes of Iron and 2 tonnes of Ice in its Bay, that Shuttle achieves victory.
Each Shuttle has between one and three Thrusters, tracked in the GNDT in the column ‘Engine’. A Thruster is a valid dice formula with a minimum value of at least 1 and a maximum value of at most 12. A DICEX Thruster may also be considered to be a 1DICEX Thruster. Thrusters may not be of the form XDICE1 for any number X.
New Shuttles start with a DICE4 Thruster. A Shuttle cannot under any circumstances lose or trade away its last Thruster.
A Thruster is Overcharged if its maximum value is at least 61% of the Orbital Size of its Shuttle’s Moon. As a special exception, DICE4 and 2DICE2 Thrusters are not considered Overcharged in Io Orbits.
A Shuttle may spend 1 Fuel to Maneuver. They roll the dice for each of their non-Overcharged Thrusters that they have that they have not used to change Orbits earlier that day, or in the last 10 hours. If there are no such Thrusters, they cannot Maneuver. They then select the result of one roll and increase their Orbit Number by that amount. The Shuttle may then optionally perform a single Knock-On Action.
As a daily action, a Shuttle may spend 2 Fuel to Hover. It increases its Orbit Number by one. The Shuttle may then optionally perform a single Knock-On Action.
An Orbital Dockyard is a type of Structure. If a Shuttle’s Orbit contains an Orbital Dockyard, that Shuttle may spend a quantity of Substances the total Market Value of which (on that Moon) is $5 or more to replace one of their own XDICEY Thrusters with an ADICEB Thruster, where “A” and “B” are positive integers whose sum is equal to “X” plus “Y”.
Orbits can contain things other than shuttles. These are tracked in the subsection of the "Orbit Contents" wiki page corresponding to that orbit. If there is an Orbit without a subsection on the Orbit Contents page, any Shuttle may add an empty subsection to it for that Orbit.
The Orbit Contents wiki page is considered gamestate and may only be modified in ways allowed by the rules.
Structures are one category of object that an Orbit might contain. An Orbit can contain at most one Structure; if an Orbit contains a Structure, any attempt to add additional Structures fails.
Non-Structure, non-Shuttle objects in orbit are Satellites. A Satellite may have Attributes, values that are tracked in parentheses with the Satellite in the Orbit Contents page.
A Container is a kind of Satellite. It has an Attribute, Storage, that is an amount of Fuel or a Substance. As a Knock-On Action, a Shuttle with the same Orbit as a Container add its Storage to their Fuel (if its Storage are Fuel) or Bay(otherwise) and destroy the Container.
The Traffic Warden may, as a daily action, choose a moon and add a Container to up to two random Orbits around it, each with up to 3 Fuel, 3 Sulfur, 3 Ice or 10 Iron in its Storage.
A Magnetic Booster is a type of Satellite. It has two attributes: Cost, which is a non-negative number, and Destination, which is an Orbit. A Shuttle in the same orbit as a Magnetic Booster may, as a daily action, spend Fuel equal to its Cost to change their Orbit to the Booster's Destination.
A Flag is a type of Satellite. It has one Attribute, Owner, which is the name of a Shuttle or Idle Shuttle. If a Flag’s Owner leaves the game, the Traffic Warden becomes its Owner.
If an Orbit has no Flag, any Shuttle with that Orbit may spend 1 Iron to create a Flag in that Orbit with them as the Owner. If an Orbit has a Flag, any Shuttle with that Orbit may spend 1 Sulfur to Deface that Flag as a Knock-On Action, changing its Owner to any Shuttle (but not an idle Shuttle).
Anything which can be stored in a Bay or is found in a Container is a Substance. If a Substance is listed in the table below, it is Saleable; otherwise it is Unsaleable. Each Saleable Substance has a Minimum Worth between $1 and $5 per tonne and a Maximum Worth between the Minimum Worth and $8 per tonne; these are tracked privately by the Traffic Warden. Each substance may also have a Market Value per tonne, also measured in $, and which may be different for each Moon. Market Value is tracked in the table below. Unsaleable Substances have no Market Value on any Moon.
As a weekly action, for each Saleable Substance and each Moon, the Traffic Warden should privately choose a random number between that Substance’s Minimum Worth and Maximum Worth, inclusive, to be that Substance’s Market Value in $ for that Moon. (The Market Value of Iron is not chosen randomly and is instead always $1.) The Traffic Warden shall then update the table below to reflect the current Market Value.
A Trading Post is a type of Structure. If a Shuttle’s Orbit contains a Trading Post, that Shuttle may exchange any amount of one Substance in their Bay for an amount of another Substance that is of equal or lesser worth. A Shuttle may only do this if the last trade they made was not at the same trading post. An amount of Substance’s total worth is calculated as its Market Value in that Orbit times the quantity of Substance.
As a Knock-On Action, a Shuttle can Deflect another Shuttle in the same orbit. They decrease the other Shuttle’s Orbit Number by 1 and increase their own Orbit Number by 1. They may then take a bonus Knock-On Action. If they do, they must skip any further Knock-On Actions that the bonus Knock-On Action would permit.
Once per dynasty, Each Shuttle may spend X fuel to gain a DICEX Thruster, where X is a number between 3 and 8, inclusive. Shuttles with more than one Thruster and Proxies cannot take this action.
Each Shuttle may belong to a single Hivemind, tracked in the GNDT. A Shuttle may leave their Hivemind at any time.
Each Hivemind has a Charter, tracked in the “Hivemind Charters” wiki page. Each Charter should contain:
- The circumstances under which a Shuttle may join that Hivemind.
- The circumstances under which a Shuttle may cause another Shuttle in the Hivemind to act.
- If the Hivemind is Awarded Victory, how to decide which of its members achieve victory.
Each Hivemind also has a unique name, its section title in the Hivemind Charters page.
A Shuttle may join a Hivemind if that Hivemind has fewer than (Quorum - 2) members, its Charter allows them to join it, and they have not left a Hivemind in the past 24 hours. Also, Derelicts may leave their Hivemind and join a different one as a daily action, if the new Hivemind's Charter allows it.
A Shuttle may cause another Shuttle in the same Hivemind to take an action, as if that other Shuttle were a Proxy, under circumstances permitted by their Hivemind’s Charter, with one exception: they cannot cast a Vote by Proxy even if the Charter and Proxy rules permit it.
If a rule Awards Victory to a Hivemind, for the remainder of the dynasty, its members may achieve victory as described by its charter.
A Hivemind with no members is Defunct.
If at least 29 Orbits have Flags whose owner is the same Shuttle, that Shuttle achieves victory. If at least 30 Orbits have Flags whose non-idle owners are all members of the same Hivemind, this rule awards victory to that Hivemind.
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 Shuttles.
- Daily Action
- If a game action is a Daily Action, each Shuttle able to perform it may take that action once each day, but not more than once every ten hours.
- 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)
- A Shuttle’s Effective Vote Comment with respect to a given Votable Matter means that Shuttle’s Comment to that Votable Matter, if any, that contains that Shuttle’s Vote on that Votable Matter.
- Flavour Text
- When posting a blog entry, a Shuttle 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 Shuttles is half the number of Shuttles in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Shuttles it is referring to, it is referring to a Quorum of all Shuttles.
- 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.
- 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 Shuttle 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 Shuttle 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 Shuttle 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. No entry may be more than one of the following official types of post: Votable Matters, and Idling Post.
If no Shuttle 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 Shuttle may update any Shuttle'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 Shuttle may correct the GNDT to comply with the Gamestate.
If a Shuttle 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, Shuttles are encouraged to raise a Call for Judgement instead. Shuttles 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 Shuttle 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 Shuttles to transfer a numeric value only allows them to transfer that value from themselves to another Shuttle (of their choice unless otherwise stated).
- A Shuttle who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
- If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
- If a number or other game variable is selected 'at random' or 'randomly' from a range of possible values, its value shall always be taken from a uniform probability distribution over the entire range of possible values, unless otherwise specified. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
- If a game variable has no defined starting value for new Shuttles, or for existing Shuttles upon the variable’s creation, then that starting value is zero (for numerical variables) or blank (for a text string or list).
- 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, Shuttle 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 a Shuttle if it is explicitly stated that it refers to a Shuttle'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 “Shuttles may Kick each other” and “Shuttles may not kick each other on Tuesdays” exist, and it is Tuesday, Shuttles may not Kick each other.)
- If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Shuttles may Punch a Spaceman on Friday” and “Shuttles may not Punch Spacemen on Friday”, then Shuttles may not Punch Spacemen on Friday.)