Core Rules

Ruleset and Gamestate

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

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

Bakers

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 Baker. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Baker.

A Baker may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Baker may not rejoin the game within two weeks after having left. A Baker may only change their name as a result of a proposal approving the change.

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

Some Bakers are Idle, and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules “Ruleset and Gamestate”, “Bakers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Bakers are not counted as Bakers.

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

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

An Admin may render a Baker Idle if that Baker has asked to become Idle in an entry or comment from the past four days, or if that Baker 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. An Admin may Unidle a Baker if that Baker 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 Baker who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.

Dynasties

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

Proposals

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

Special Proposal Voting

When a Baker casts an explicit vote AGAINST their own Proposal, this renders the Proposal Self-Killed, even if the author later changes their Vote. The Simon may use VETO as a voting icon to cast a Vote on a proposal; when the Simon casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Simon later changes their Vote.

If a Baker other than the Simon casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Simon. When the Simon 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 Simon’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 could not be Enacted without either one of the Votes AGAINST it being changed, or the set of Bakers being changed, or by awaiting the passage of time.
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.

Votable Matters

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

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

Calls for Judgement

If two or more Bakers actively disagree as to the interpretation of the Ruleset, or if a Baker feels that an aspect of the game needs urgent attention, then any Baker 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 Baker (other than the Simon) 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 “Bakers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

Every Baker 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 Simon 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 it could not be Enacted without either at least one of the Votes AGAINST it being changed, or the set of Bakers being changed, or by awaiting the passage of time.
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 Baker who made the DoV as its Simon. That Baker may pass this role to another Baker at this point by making a post to that effect, if they wish. The Hiatus continues until the new Simon makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Simon's chosen theme for the new Dynasty, and may optionally specify that the terms Baker and Simon will be replaced with theme-specific terms throughout the entire ruleset, and/or a number of dynastic rules to keep. Upon posting such an Ascension Address, the ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it has a number of AGAINST Votes that exceed Quorum, the Baker 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 Baker'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 Baker within BlogNomic.
A Baker 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 Baker should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
A Baker should not edit their own blog comments once posted, nor those of any other Baker.
A Baker should not edit the "Entry Date" field of a blog post.
A Baker should not make a DoV primarily to delay the game by putting it into Hiatus.
A Baker 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

Pies

Each Baker has a collection of Pies tracked in the GNDT in a column called “Pies”. Pies come in a number of different Flavors which are listed below. For each Baker, Pies field of the GNDT contains a comma separated list containing the number of Pies that Baker has in each flavor in the order the Flavors are listed below. (So if the Flavors are “Apple”, “Rhubarb” and “Cherry” a worker with a Pies field of “3, 2, 0.5” has three Apple Pies, two Rhubarb Pies, and half a Cherry Pie). Bakers can only have non-negative amounts of each flavor of pie. The total number of Pies a Baker has is the sum of the number of pies of each Flavor he has, and is tracked for convenience in a GNDT column called “Total”. Bakers start with zero of each flavor of pie by default. When a Baker joins the dynasty for the first time, they gain a number of Empty Pies equal to the minimum Total number of pies held by any other Baker.

The Flavors of Pie are as follows:

Apple, Cream, Empty, Dutch Apple, Portal, Warp, Magnetic

Pie Quota

Whenever a Baker has more than 10 Pies of a certain flavor, the number of their Pies of that flavor is set to 10.

A Baker cannot have more than 20 Pies in total. If performing some action would result in at least one Baker having more than 20 Pies, that action may not be performed.

Upgrades

As a daily action, a baker may pick one of the Upgrades listed below and perform it. When a baker performs an upgrade, they must first spend all of the Input Pies listed for the Upgrade (if any exist) and then (provided they were able to spend the required Input Pies) they receive all of the Output Pies for the chosen Upgrade.

The possible upgrades are as follows:

Input: none. Output: 1 Empty Pie
Input: 1 Empty Pie. Output: 1 Apple Pie
Input: 1 Apple Pie. Output: 1 Dutch Apple Pie
Input: 1 Empty Pie. Output: 1 Cream Pie
Input: 2 Empty Pies. Output: 1 Portal Pie
Input: 1 Empty Pie. Output: 2 Warp Pies
“Input: 1 Empty Pie, 1 Warp Pie. Output: 1 Magnetic Pie

If a Baker does not perform this action during a day, they gain one Empty Pie at the end of that day unless this is prohibited by the “Pie Quota” rule.

The Holy Circle

Each Baker may have a spot in the Holy Circle, tracked in the GNDT in a column called “Position”. A Baker is said to be in the Holy Circle if their Position is a positive integer. A Baker is said to be outside the Holy Circle if their Position is “Out”. Two Bakers in the Holy Circle cannot have the same Position.

If there is a positive integer N such that a) no Baker has Position N and b) some Baker has position N+1, that Baker’s position immediately becomes N. Whenever a Baker unidles or joins the dynasty for the first time their Position becomes the smallest positive integer which is not currently a Position held by another Baker, unless they are unidling and held the position of “Out” when they became idle, in which case their position remains Out.

The Distance between two Bakers in the Holy Circle with Positions A and B, with B bigger than A, is equal to the minimum of B - A and A + T - B where T is the number of Bakers in the Holy Circle. (Distance is commutative, so if B is less than A it would be equal to the minimum of A - B and B + T - A). Two Bakers in the Holy Circle are Adjacent if the Distance between them is 1. The distance between a Baker and himself is zero.

Holy War

Each Baker has a number of Hits, which is a non-negative integer tracked in a GNDT column called “Hits”.

If a Baker (the Attacker) possesses a Cream Pie, they may reduce their number of Cream Pies by one, pick another Baker (the Target) in the same location as himself (other than himself) and roll a DICE(N+1) where N is the distance between the two Bakers. If the result is a 1 or N + 1, the Target is hit in the face by the Pie and their Hits are increased by one.

The Holy Dance

If a Baker (the Attacker) posseses a Portal Pie, the Baker may reduce their number of Portal Pies by one, and roll a DICEN where N is the number of Bakers in the Holy Circle. The Baker whose Position is equal to the result of the die roll is the Target. The Attacker and the Target then swap Positions and Pies. The Target then gains two Empty Pies.

Time Out

If a Baker’s Hits is ever greater than or equal to 8, the Baker’s Position becomes Out. If a Baker’s position is Out, they cannot target or be targeted as part of “The Holy War” or “The Holy Dance”. If a Baker’s position is Out, their Location becomes the Graveyard, and then their location cannot be changed by any means while they remain Out

If a Baker’s position is Out, they may, as a weekly action, remove three of their Hits. If as a result their Hits become less than 8, their Position is immediately set to the smallest positive integer which is not currently a Position held by another Baker.

If there is only one Baker who is in the Holy Circle and who has neither unidled nor registered in the last 7 days, that Baker has achieved victory.

Out of Sight, Out of Mind

If a Baker’s position is Out, then they may not be the trader or the tradee of any trade as part of the rule “Trading”.

If a Baker becomes out while they are the trader or the tradee of any pending trade, then any such trade is immediately cancelled.

Locations

Each Baker has a Location which is tracked in the GNDT in a column called “Location”. All Bakers start in the Foyer. A Baker’s location may also be “Apple Farm”, “Creamatorium”, “Science Lab”, or “Graveyard”, or "Far Away".

If a Baker’s Location is the Apple Farm, the “Input: none, Output: 1 Apple Pie” upgrade becomes available to that Baker when choosing an upgrade for the upgrade action.

If a Baker’s Location is the Creamatorium, the upgrades “Input: 1 Apple Pie, Output: 2 Cream Pies” and “Input: 1 Dutch Apple Pie, Output: 4 Cream Pies” both become available to that Baker when choosing an upgrade for the upgrade action.

If a Baker’s Location is the Science Lab, if he is targeted by a Portal Pie neither is Position or Pies swap with the attacker.

If a Baker’s Location is the Graveyard and he is not Out, He may name an Out Baker, spend 1 Cream Pie (provided he has one) and roll a DICE3. If the result is a 1, the targeted Baker’s hits increase by one.

A Baker with at least one Warp pie may spend a Warp pie (i.e., reduce their number of Warp pies by exactly one) to take one of the following actions:

Change their current Location to any other valid Location, provided neither the starting nor ending location is Far Away
Change their Location from Foyer to Far Away
Change their Location from Far Away to Foyer

Only one of the above actions may be chosen per Warp Pie spent, and the action chosen may be executed only once per Warp Pie spent.

A Baker (the User) may spend 1 Magnetic pie to force another Baker (the Target) to perform one (and only one, per Magnetic pie spent) of the above Warp pie actions, provided the current location of the User is either the starting or ending Location of the Target.

Trading

As a daily action, a Baker (“the trader”) may request to trade their pies with one other Baker (“the tradee”) by making a post with TRADE, in all caps, in the title. The post must specify, the name of the tradee, which pies they wish to give, and the which pies they want to receive.

The trade is considered Pending until the trader cancels the trade by making a comment to the post containing the text “CANCEL”, in all caps, or the tradee accepts the trade by making a comment to the post containing the text “ACCEPT”, in all caps. Once a trade is canceled or accepted, it ceases to be pending. A non-Pending trade cannot be canceled nor accepted.

If the tradee accepts the trade, and if at that time the trader possesses all the pies they wished to give and the tradee possesses all the pies the trader wished to receive, then the pies the trader wished to give are transferred from the trader to the tradee, and the pies the trader wished to receive are transferred from the tradee to the trader.

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

Daily Action: If a game action is a Daily Action, each Baker able to perform it may take that action once each day, but not more than once every ten hours.

Day: References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 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 Baker’s Effective Vote Comment with respect to a given Votable Matter means that Baker’s Comment to that Votable Matter, if any, that contains that Baker’s Vote on that Votable Matter.

Flavour Text: When posting a blog entry, a Baker may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.

Gamestate: Any information which the Ruleset regulates the alteration of.

IRC Channel: The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).

May: "is permitted to"

May not: "is not permitted to"

Post: A blog post published to the BlogNomic weblog at blognomic.com

Quorum: Quorum of a subset of Bakers is half the number of Bakers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Bakers it is referring to, it is referring to a Quorum of all Bakers.

Resolve/Resolution: 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

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.

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 Baker able to perform it may take that action once each week, but not more than once every twenty-four hours.

Weekly Communal Action: If a game action is a Weekly Communal Action, it can be performed by any Baker, but only if it has not been performed (by any Baker) already in the same week.

Wiki: The BlogNomic Wiki at http://blognomic.com/wiki/index.php?title=Main_Page

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 Baker 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 Baker has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception: Whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish.

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

If a Baker 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, Bakers are encouraged to raise a Call for Judgement instead. Bakers shall be assigned a password for the GNDT when they join the Nomic.

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 Bakers to transfer a numeric value only allows them to transfer that value from themselves to another Baker (of their choice unless otherwise stated).
A Baker who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one or more of those values to an illegal value.
If a rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
If a number or other game variable is selected 'at random' or 'randomly' from a range of possible values, its value shall always be taken from a uniform probability distribution over the entire range of possible values, unless otherwise specified.
If a game variable has no defined starting value for new Bakers, or for existing Bakers 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.
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.

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 Baker if it is explicitly stated that it refers to a Baker's name.

Prioritisation

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 a Core Rule, or if both of them are a Dynastic Rule, the part with more limited scope applies. (e.g. if the rules “Bakers may Kick each other” and “Bakers may not kick each other on Tuesdays” exist, and it is Tuesday, Bakers may not Kick each other.)
If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Bakers may Punch a Spaceman on Friday” and “Baker may not Punch Spacemen on Friday”, then Bakers may not Punch Spacemen on Friday.)

Ruleset 103

Contents