Returning players! Wiki accounts were reset in late 2014. If you haven't played since then and wish to edit the wiki, you'll need a fresh account.

Ruleset 114

From BlogNomic Wiki
Jump to navigation Jump to search

Core Rules

Ruleset and Gamestate

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

MNs 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 via the Register link in the sidebar, and then making a post making clear their wish to be a MN. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a MN.

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

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

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

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

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

An Admin may render a MN Idle if that MN has asked to become Idle in an entry or comment from the past four days, or if that MN 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 provided they’ve made a post or comment declaring their intent to do so in the past four days. An Admin may Unidle a MN if that MN 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 MN who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.


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

Votable Matters

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

Each MN 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 MN’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-MN never has a Vote, even if they were a MN 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 MN may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the MN already has 2 Proposals pending, or has already made 3 Proposals that day).

Special Proposal Voting

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

If a MN other than the Speaker casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Speaker. When the Speaker 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 Speaker'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 MNs 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 MNs actively disagree as to the interpretation of the Ruleset, or if a MN feels that an aspect of the game needs urgent attention, then any MN 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 MN (other than the Speaker) 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 “MNs”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

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


MUST: The Government of Blognomic is shut down. No MN can win.

This rule may only be amended or repealed by a Proposal if that Proposal was made by a member of the Majority, AND if over 60% of the votes cast on it were FOR it.

The Sequester

MUST: There exists, on the wiki page titled Sequester, a ruleset. Its contents have no effect on the gamestate unless the gamestate has become Polarised. If the gamestate is Polarised, then all rules in the Sequester are treated as being part of the Ruleset, with the same status as Dynastic Rules.

MUST: Unless specifically otherwise stated by another rule or enacted proposal, the gamestate becomes Polarised at 9am on November 3rd 2013. If the gamestate is Polarised then any player may update this rule at any time to reflect this fact. The gamestate is currently Polarised.

MUST: If the gamestate is not Polarized, The Sequester page of the wiki may be edited once per day by each MN. An edit made to the Sequester page by an MN may add content but never remove it, unless it violates a clause of this rule or the change is an effect of the passage of a Voteable Matter. If an MN edits the Sequester page of the wiki and adds content, that MN may also delay when the gamestate becomes Polarised by 6 hours, updating the previous paragraph as necessary. If an MN edits the Sequester page of the wiki and removes content, that MN may also accelerate when the gamestate becomes Polarised by 6 hours, updating the previous paragraph as necessary.

MUST: No rule on the Sequester page may directly award Victory to any MN, nor may they directly edit or repeal any Core Rule of the Ruleset.

MUST: As a Weekly Action, an MN may make a Repeal Request, a story post that contains only the name of exactly one rule on the Sequester wiki page (The commentary need not be blank). The title of this post must contain the word “REPEAL”. If, after exactly 24 hours, a committee that the posting MN is a part of has all voted FOR and there are fewer total AGAINST votes than FOR votes, the Repeal Request passes. Otherwise it fails. If a Repeal Request passes, any MN may remove the rule in the Sequester named in that Repeal Request.

Only the MN who posted a passing Repeal Request may remove the rule in the Sequester named in that Repeal Request.

Disorder in the House

MUST: Each MN may Ignore one paragraph of some dynastic rule. Which paragraph they are Ignoring is tracked in the GNDT column “Ignoring” by recording the number of the rule, then a dash, followed by the number of the paragraph in that rule which they are Ignoring. By default, no paragraph is Ignored, and it’s tracked as “-”. A MN may only change which rule they are Ignoring if they have Ignored the same rule continuously for the last 96 hours.

MUST: If an MN is Ignoring a paragraph of a dynastic rule, they treat the ruleset as if it did not contain that paragraph, except for any definitions that paragraph contains. Any other MN who is not Ignoring that paragraph does not treat the ruleset as if it did not contain that paragraph, unless they take an action which is affected by a paragraph and affects an MN who is Ignoring that paragraph. In that case, treat that paragraph as not existing for the purposes of affecting MNs which Ignore it only.

MUST: However, voters on a Declaration of Victory shall base their votes on the perspective of the author of that Declaration of Victory with respect to ignored paragraphs. Also, an Admin enacting a Proposal or Call for Judgment shall carry out any modifications it makes to their Ignored paragraph. This paragraph takes precedence over the other parts of this rule.

MUST: Any paragraph of any dynastic rule may be headed by a “MUST:” header. If a paragraph is headed with “MUST:”, it may not be Ignored.

Ain’t No Party

Each MN is a member of a block of like-minded MNs. Political affiliations are defined by physical orientation from the Speaker in the Chamber; MNs can therefore be either Sunwards (SW) or Widdershins (WS). Each MN’s Orientation is tracked in the GNDT.

An MN with no Orientation may set their Orientation at any time.

Whichever Orientation has the most MNs is the Majority. The other Orientation is the Minority.

Circular Representation

There is a GNDT column called “Endorsement” whose legal values are the names of all MNs. A MN is said to Endorse the MN named in that column. This represents the other MN whom that MN trusts most to uphold their interests. A MN may change their Endorsement to any valid MN as a weekly action. A MN who Endorses an invalid target (such as a MN who is ignoring this paragraph) may change their Endorsement to any other MN at any time. A MN’s Endorsement defaults to the MN immediately above them in the GNDT, with the top MN defaulting to the bottom MN.

An MN may not Endorse himself.

If a MN becomes Idle, all MNs who Endorse them have their Endorsement changed to the that of the MN who became Idle. If this would cause a MN to have an illegal Endosement value, their Endorsement is instead reset to its default value.

MUST: A Committee is a group of at least three MNs who each endorse another MN in the group.


If a MN (the Follower) has Endorsed the same MN (the Leader) for at least 24 hours, the Follower may change the paragraph they Ignore to match the paragraph the Leader is Ignoring.



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
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 MNs.
Daily Action
If a game action is a Daily Action, each MN 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 MN’s Effective Vote Comment with respect to a given Votable Matter means that MN’s Comment to that Votable Matter, if any, that contains that MN’s Vote on that Votable Matter.
Flavour Text
When posting a blog entry, a MN 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 (
"is permitted to"
May not
"is not permitted to"
A blog post published to the BlogNomic weblog at
Private Message
A message sent via Blognomic’s Private Messages system at
Quorum of a subset of MNs is half the number of MNs in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of MNs it is referring to, it is referring to a Quorum of all MNs.
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 shall represent a Vote FOR, an X shall represent a Vote AGAINST, an IMP shall represent a Vote of DEFERENTIAL, and an Imperial Seal 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 MN 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 MN, but only if it has not been performed (by any MN) already in the same week.
The BlogNomic Wiki at

Gamestate Tracking

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at Any MN 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 MN 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 Any MN may update any MN'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 MN may correct the GNDT to comply with the Gamestate.

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

Random Generators

The GNDT can be used to generate random results.

  • The DICEN command can be used to generate a random number between 1 and N.
  • The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
  • The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
  • The VEGGIE command will return a random result from the following: Potato, Carrot, Triffid, Pumpkin.

Any changes to the potential outcomes of the GNDT’s random result commands must be made by proposal; and any proposal that seeks to nominate a change to this rule must first identify an active MN 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 MNs to transfer a numeric value only allows them to transfer that value from themselves to another MN (of their choice unless otherwise stated).
  • A MN 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 MNs, or for existing MNs 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.
  • Unless explicitly stated otherwise, a wiki page shall be blanked when it becomes gamestate.
  • 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.


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


  • If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
  1. The Appendix has precedence over any Rule;
  2. A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
  3. If both contradicting parts are a Core Rule, or if both of them are a Dynastic Rule, the part with more limited scope applies. (e.g. if the rules “MNs may Kick each other” and “MNs may not kick each other on Tuesdays” exist, and it is Tuesday, MNs may not Kick each other.)
  4. If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “MNs may Punch a Spaceman on Friday” and “MNs may not Punch Spacemen on Friday”, then MNs may not Punch Spacemen on Friday.)