Core Rules

Ruleset and Gamestate

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

Admins may correct obvious spelling and typographical mistakes in the Ruleset at any time, including replacing Spivak and gender-specific pronouns with the singular “they”. Musicians may correct obvious spelling and typographical mistakes in their own Pending Proposals at any time

Musicians

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

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

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

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

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

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

An Admin may render a Musician Idle if that Musician has asked to become Idle in an entry or comment from the past four days, or if that Musician 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 Musician if that Musician 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 Musician 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 Musician, known as the Frontman. If there is no Frontman, the Dynasty is a Metadynasty.

Proposals

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

Special Proposal Voting

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

If a Musician other than the Frontman casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Frontman. When the Frontman 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 Frontman’s Vote for the purposes of other rules unless otherwise specified.

Resolution of Proposals

The oldest pending Proposal may be enacted by any Admin (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) 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 Musicians 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 Musicians may cast Votes on, such as a Proposal, a Call for Judgment or a Declaration of Victory.

Each Musician 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 Musician’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-Musician never has a Vote, even if they were a Musician 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 Judgment or Declarations of Victory.

Calls for Judgment

If two or more Musicians actively disagree as to the interpretation of the Ruleset, or if a Musician feels that an aspect of the game needs urgent attention, then any Musician may raise a Call for Judgment (abbreviated CfJ) by posting an entry in the “Call for Judgment” 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 Musician (other than the Frontman) 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 “Musicians”, “Votable Matters”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

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

Koen’s Band

The Frontman does not count as a Musician for the purposes of any other Dynastic Rule, except where that Rule specifically refers to the Frontman.

A Note of Discord

At the creation of this rule, every active Musician, and after that, each Musician that joins or unidles for the first time in this dynasty, will be randomly assigned a style, either Rock or Techno, and will then be notified of their style via private message by the Frontman, along with the name of another Musician, randomly selected, who has the same style as them, provided there is one.

Styles are secretly recorded by the Frontman.

In the Band

Musicians may be either Band Members or Hangers On. This is tracked as a “Band” field in the GNDT, noted as “Yes” if the Musician is a Band Member and “No” or “-” if they are a Hanger On. All Musicians start as Hangers On.

At any time, if the band has no members, the frontman must roll for dices I=DICEN J=DICE(N-1) K=DICE(N-2) L=DICE(N-3), where N is the number of Musicians. Then the Ith Hanger On as appears in the Current Active Player List becomes a Band Member, then the Jth Hanger On and so on, stopping if there are no Hangers On. When more than one Musician become Band Members this way, they are considered to have become Band Members simultaneously.

The Band Evolves

If at least a Quorum of Band Members Respect the same Hanger On and no Band Members have a Grievance against that Hanger On, then that Hanger On becomes a Band Member (and ceases to be a Hanger On).

If at least a Quorum of the Band Members have a Grievance against the same Band Member, and no Band Members Respect that Band Member, then that Band Member becomes a Hanger On (and ceases to be a Band Member).

Rotten Fruit

If at least two-thirds of the Hangers-On have a Grievance against the same Band Member, that Band Member ceases to be a Band Member unless there is a pending, unresolved Tour.

Respect and Grievance

Each Musician may Respect one Musician (or Idle Musician) and have a Grievance against one Musician (or Idle Musician). These are tracked as the name of a Musician, or the name of an Idle Musician, or “-” to represent no Musician, in the “Respect” and “Grievance” fields of the GNDT respectively. A Musician may not Respect themselves, nor have a Grievance against themselves. Musicians default to Respecting nobody and having a Grievance against nobody.

A Musician may change who they Respect and/or who they have a Grievance against, at any time.

Consonance

A Musician cannot have a Grievance against someone they Respect. If a Musician Respects another Musician, they cannot have a Grievance against anyone that Musician Respects. However, if a Musician X Respects a Musician Y and has a Grievance against a Musician Z, the Musician Y is allowed to change Y’s Respect to Z, in which case X ceases to have a Grievance.

Winning Hearts

If one Musician is Respected by every Musician they do not share a Style with, unless all Musicians have the same Style, the Frontman may cause that Musician to achieve victory by making a blog post saying so and listing the Style of every Musician. The Frontman SHOULD do so if he can.

Fame

Each Musician has a integer stat called “Fame” which is initially zero.

The frontman must resolve the Story Posts defined in this rule and its sub-rules in the order in which they became solvable.

Tour

If there is not currently a pending Tour posted, and if none of the Tours made in the past 7 days (if any were made) were initiated while the Band Members were the same set of Musicians as they are now, then any Band Member may make a Story Post with the title “Tour”. The Tour is considered pending until the set of Band Members changes or until it is either resolved or failed by the Frontman.

If at any time there is only one Band Member and a Tour is pending, it may be failed by the Frontman with a comment to the Tour saying so.

The Frontman may resolve a pending Tour at any time, provided there are at least two Band Members. When the Frontman resolves a pending Tour, one of these three situations will occur:

I - If there are at least two Band Members with different styles, the Frontman must decrease the Fame of the Band Member who made the Tour by one and make them a Hanger On.

II - If all Band Members have the same style and there is one and only one Band Member Showing Off, the Frontman must increase that Band Member's Fame by B where B is the number of Band Members.

III - If all Band Members have the same style and either none of them is Showing Off or at least two of them are Showing Off, the Frontman must increase the Fame of every Band Member not Showing Off by C, where C is half the number of Band Members, rounded up.

When situation II or situation III occurs, each active Band Member will be randomly assigned a style, either Rock or Techno, which will replace their previous style. Each Band Member will then be notified of their style via private message by the Frontman, along with the name of another Musician, randomly selected, who has the same style as them. All Band Members then become Hangers On (and thus cease to be Showing Off).

Immediately after resolving a Tour, the Frontman must make a comment to the Tour specifying which of the three situations occurred.

Jam Session

As a weekly action, each Musician may either start a Jam Session or Join an existing Jam Session. To start a Jam Session, a Musician posts a Story Post with “Jam Session” in its title. To Join a Jam Session, a Musician makes a comment to that Jam Session’s Story Post stating that they are doing so. A Musician who has started or Joined a Jam Session is a member of that Jam Session.

Band Members cannot start Jam Sessions. A Musician cannot Join a Jam Session if that Jam Session has ended, if they are already a member of that Jam Session, if they are a Band Member or if a member of that Jam Session has a Grievance against them.

As soon as is practical after a Jam Session has been posted for 48 hours, the Frontman shall end that jam session by making a comment on its Story Post saying that it’s over. If the Jam Session has three or more members who are not Band Members, he shall then inform each member of that Jam Session who is not a Band Member of the style of a random other member of that Jam Session who is not a Band Member.

Cover Show

If there is not currently a pending Cover Show posted, and if none of the Cover Show made in the past 7 days (if any were made) were started while the Band Members were the same set of Musicians as they are now, then any Hanger On may start a Cover Show by making a Story Post with the title “Cover Show”. The Cover Show is considered pending until the set of Band Members changes (either by a Musician switching from Band Member to Hanger On or vice versa or by a Band Member going idle) or until it is resolved by the Frontman.

To Join a Cover Show, a Musician makes a comment to that Cover Show’s Story Post stating that they are doing so. A Musician who has started or Joined a Cover Show is a member of that Cover Show. A Musician cannot Join a Cover Show if that Cover Show has been resolved, if they are already a member of that Cover Show, if they are a Band Member or if a member of that Cover Show has a Grievance against them.

The Frontman may resolve a pending Cover Show either if it has been pending for 48 hours or if it has at least 4 members. When the Frontman resolves a pending Cover Session, one of these 3 situations will occur:

I - If there are less than 4 members in the Cover Show, each such member loses F Fame, where F equals 4 minus the number of members in the Cover Show.

II - if there at least 4 members in the Cover Show and all of them have the same style, then the following occurs, in this order:

a. the frontman must reassign each Band Member a new style via the process used for new Musicians.

b. all current Band Members become Hangers On (and thus cease to be Showing Off, if any was) and, simultaneously, all the members of the Cover Show become Band Members.

c. the frontman must increase the Fame of each of the new Band Members by C where C is the number of Band Members, divided by two, rounded up.

d. the frontman must reassign each Band Member a new style via the process used for new Musicians and all Band Members then become Hangers On.

III - Otherwise, the Frontman must decrease by one the Fame of each member of the Cover Show whose style is not the same as the Musician who started the Cover Show.

In any of the 3 cases, the frontman must make a comment on the pending Cover Show as to which way he resolved it.

Assets

Each Musician may possess up to one Asset. Asset ownership is tracked in the GNDT. New Musicians start with no Assets. If a Musician has no Assets, they may gain an Asset of their choice from those available.

If a Hanger On possesses an Asset which no Band Member possesses, then that Hanger On may change the Respect of any Band Member to any other Musician, so long as this does not change any Musician’s Respect or Grievance to an illegal value (as set out in the rule entitled “Respect and Grievance”). A Musician may only change the Respect of one Musician via this rule in each 48 hour period.

A list of all available Assets follows:

Rehearsal Space
Sweet Ride
Uncle at a Record Label
Groupie magnet
Fake ID
Home recording equipment

Showing Off

A Band Member may choose to Show Off by sending a PM to the Frontman. That Band Member is considered to be Showing Off until they cease to be a Band Member or the ruleset states otherwise.

Negatives and nulls shouldn't be discriminated against

As soon as is practical after this rule has been created, and until a Musician's Fame has reached 10, the Frontman must repeat the following actions: - Roll a DICEN, where N is the number of Musicians; let K be the result. - Add 1 to the Kth Musician's Fame, where Musicians are sorted alphabetically.

All dice must be rolled within the GNDT; however, for conveniency issues, the Frontman may roll the dice ten by ten; if too many dice are rolled, the extra rolls are ignored.

Then, the Musician whose Fame is 10 must make a post containing the name of one Musician who shares their style (or the assertion that no Musician shares their style), followed by the name of one Musician who doesn't share their style (or the assertion that no Musician shares their style).

If both guesses are correct, that Musician then achieves Victory.

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

Daily Action: If a game action is a Daily Action, each Musician 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 Musician’s Effective Vote Comment with respect to a given Votable Matter means that Musician’s Comment to that Votable Matter, if any, that contains that Musician’s Vote on that Votable Matter.

Flavour Text: When posting a blog entry, a Musician 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 Musicians is half the number of Musicians in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Musicians it is referring to, it is referring to a Quorum of all Musicians.

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

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.

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 Musician 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 Musician, but only if it has not been performed (by any Musician) 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 Musician 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 Musician 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 Musician may update any Musician'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 Musician may correct the GNDT to comply with the Gamestate.

If a Musician 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, Musicians are encouraged to raise a Call for Judgment instead. Musicians 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 Musicians to transfer a numeric value only allows them to transfer that value from themselves to another Musician (of their choice unless otherwise stated).
A Musician 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 Musicians, or for existing Musicians 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”.

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 Musician if it is explicitly stated that it refers to a Musician'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 “Musicians may Kick each other” and “Musicians may not kick each other on Tuesdays” exist, and it is Tuesday, Musicians may not Kick each other.)
If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Musicians may Punch a Spaceman on Friday” and “Musician may not Punch Spacemen on Friday”, then Musicians may not Punch Spacemen on Friday.)

Ruleset 99

Contents