Ruleset and Gamestate
This is the Ruleset for BlogNomic; all Apes 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; Section Three contains rules which apply in special cases; and Section Four 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.
Apes 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”.
If the Ruleset does not properly reflect all legal changes that have been made to it, any Ape may update it to do so.
Any human may apply to join BlogNomic (if they are not already an Ape) 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 Ape. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become an Ape.
An Ape may cease to be an Ape at any time by posting an entry to the BlogNomic weblog requesting such an action. A human who has ceased to be an Ape in this way may not become an Ape again within the following two weeks. An Ape may only change their name as a result of a proposal approving the change.
Some Apes are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Apes who wish to become Admins may sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation. New admins shall be given the GNDT configuration password when they become admins.
Some Apes 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”, “Apes”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Apes are not counted as Apes.
If a Proposal contains a provision that targets a specifically named Idle Ape, then that Idle Ape is considered to be Unidle solely for the purposes of enacting that specific provision
When an Ape 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 Ape Idled in a different dynasty), the Ape is given the default value for new Ape, if such a value exists.
An Admin may render an Ape Idle if that Ape has asked to become Idle in an entry or comment from the past four days, or if that Ape has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle an Ape if that Ape is Idle and 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 Ape who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.
Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.
Idle Admins can enact and fail Votable Matters.
BlogNomic is divided into a number of Dynasties. Each Dynasty may be headed by a single Ape, known as the Monolith. If there is no Monolith, the Dynasty is a Metadynasty.
A Votable Matter is a post which Apes may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.
Each Ape 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 Mortal’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-Ape never has a Vote, even if they were an Ape previously and had cast a valid Vote.
If an Ape other than the Monolith casts a vote of DEFERENTIAL, then the Vote of DEFERENTIAL is an indication of confidence in the Monolith. When the Monolith has a valid Vote other than VETO on a Votable Matter, then all votes of DEFERENTIAL on that Votable Matter are instead considered to be valid and the same as the Monolith's Vote for the purposes of other rules unless otherwise specified.
A Votable Matter is Popular if any of the following are true:
- It has a number of FOR Votes that exceed or equal Quorum.
- It has been open for voting for at least 48 hours, it has more than 1 valid Vote cast on it, and more valid Votes cast on it are FOR than are AGAINST.
A Votable Matter is Unpopular if any of the following are true:
- The number of Apes who are not voting AGAINST it is less than Quorum.
- It has been open for voting for at least 48 hours and it is not Popular.
Enacting and Failing
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 should mark their name, and are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Comments cannot be made on Enacted or Failed Votable Matters.
This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.
Any Ape may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Ape already has 2 Proposals pending, or has already made 3 Proposals that day).
Special Proposal Voting
When an Ape casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal Self-Killed, even if the author later changes their Vote. The Monolith may use VETO as a voting icon to cast a Vote on a proposal; when the Monolith casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Monolith later changes their Vote.
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 all of the following are true:
- It is Popular.
- It has been open for voting for at least 12 hours.
- 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 is Unpopular.
- It has been Vetoed or Self-Killed.
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 Apes actively disagree as to the interpretation of the Ruleset, or if an Ape feels that an aspect of the game needs urgent attention, then any Ape may raise a Call for Judgement (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.
A Pending CfJ may be Enacted by any Admin if all of the following are ture:
- It is Popular.
A Pending CfJ may be Failed by any Admin if any of the following are true:
- It is Unpopular.
- It specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities.
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.
This Rule may not be overruled by Dynastic Rules.
Victory and Ascension
If an Ape (other than the Monolith) 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.
If the game is not already in Hiatus and there is a pending DoV, 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 “Mortals”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.
Every Ape 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 by any Admin if any of the following is true:
- It is Popular, it has been open for at least 12 hours, and either the Monolith has Voted FOR it or it has no AGAINST Votes.
- It is Popular, and it has been open for at least 24 hours.
A Pending DoV may be Failed by any Admin if any of the following are true:
- It is Unpopular, and it has been open for at least 12 hours.
When a DoV fails and there are no pending DoVs, Hiatus ends.
When a DoV is enacted, all other pending DoVs are failed, and a new Dynasty begins with the Ape who made the DoV as its Monolith. That Ape may pass this role to another Ape at this point by making a post to that effect, if they wish. The Hiatus continues until the new Monolith makes an Ascension Address by posting an entry in the “Ascension Address” category - this should specify the Monolith's chosen theme for the new Dynasty, and may optionally specify that the terms Ape and Monolith will be replaced with theme-specific terms throughout the entire ruleset, and/or a number of dynastic rules to keep. Upon posting such an Ascension Address, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed.
A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it had at least one AGAINST vote, the Ape who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.
This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.
The following are BlogNomic’s rules of fair play. If any of these rules are found to have been broken, or if an Ape'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 non-Idle Ape within BlogNomic, and should announce publicly if they control both a non-Idle Ape and any Idle Apes.
- An Ape should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
- An Ape should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
- An Ape should not edit their own blog comments once posted, nor those of any other Ape.
- An Ape should not edit the "Entry Date" field of a blog post.
- An Ape should not make a DoV primarily to delay the game by putting it into Hiatus.
- An Ape should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).
- An Ape should not roll dice in the GNDT that are clearly associated with a particular action in the Ruleset, but with the intention to not use these rolled values to the best of their ability to resolve that action.
- An Ape should not deliberately and unreasonably prolong the performance of a game action once they have started it.
Each Ape has an amount of Food, which defaults to 0 and is tracked in the GNDT under a column named "Food".
Each Ape has an amount of Lifetime Actions, which defaults to 3 and is tracked in the GNDT under a column named “LA”.
Each Ape has a gender tracked in the GNDT, either male, female or runt, and defaulting to a randomly chosen value.
Each Ape has a Legacy, being a number tracked in the GNDT.
Each Ape has a Battle Status, being a value tracked in the GNDT that defaults to “No.”
At any time, an Ape may pay one Lifetime Action, to perform an action from the following list:
- Hunt: Roll DICEX, where X is equal to the number of Brawn genes this Ape has, plus 3, plus another 2 if the Ape is Large – Gain one less Food than the result.
- Forage: Gain 1 Food.
- Share: Lose one or more Food to have another Ape gain the same amount of Food.
- Investigate strangely glowing pond: Mutate yourself.
- Offer contaminated food: Lose two or more Food to have another Ape (here called the Recipient) gain the same amount of food. Mutate the Recipient an amount of times equal to half of the Food you lost, rounded down. This Action can only be performed if the Recipient does not have more Intelligence Genes than you.
- Push into glowing pond: Mutate another Ape (here called the Target). This Action can only be performed if you have more Brawn Genes than the Target. Large Apes can only be the Push Target of other Large Apes. You cannot use the Push Action on the same Target multiple times in one generation.
- Attack Neanderthals: Switch the Battle Status of your Ape to Yes. An Ape whose Battle Status is “Yes” is considered to be Fighting during the New Generation Event.
- Eat hearty meal: Lose two Food. Change your non-inherited trait to Brawn.
- Host wise guest: Lose two or more Food to have another Ape with more Intelligence Genes than you gain the same amount of Food. Change your non-inherited trait to Intelligence.
- Present Poem: Compose an original haiku, limerick, or sonnet and include it in a new post whose title begins with “Poem:”. Change your non-inherited trait to Charm. This action can only be performed if the Writing Tradition is in the Troop’s Culture.
- Show off moves: Change your non-inherited trait to Beautiful. You can only use this move if the Dance Tradition is in the Troop’s Culture and you have at least one Speed or Charm Gene.
The Troop of Apes has zero or more Traditions in its Culture, and the Culture may contain more than one copy of the same Tradition. The Culture of the Troop is listed in this rule as follows: Weaponry.
The names, Complexities and effects of Traditions are as follows, with their Complexity in brackets and their effect after the brackets:-
- Agriculture [Complexity 2] Whenever the Forage action is performed by an Ape, that Ape may gain 1 additional Food.
- Weaponry [Complexity 1] Whenever the Hunt action is performed by an Ape, that Ape may gain 1 additional Food.
- Coming of Age Ritual [Complexity 2] The first time each generation that an Ape Investigates strangely glowing pond, that Ape may choose to Mutate an additional time.
- Tool Use [1 Intellect] Apes with at least 1 Intellect spend 1 fewer Food (to a minimum of 1) when adding a Tradition to the Culture.
- Writing [2 Intellect] The Complexity of every Tradition is considered to be 1 lower (to a minimum of zero) when checking whether to remove it during a New Generation Event.
- Religion [4 Intellect] If Religion is added to the Culture when the Culture has no Religion Tradition, the Ape adding it gains 1 Legacy.
- Dance [1 intellect] Each Ape starts the Generation with one additional Lifetime Action
An Ape’s Intellect is the number of Intelligence genes that they have. As a Lifetime Action, an Ape whose Intellect equals or exceeds the Complexity of a Tradition may (as a Lifetime Action) pay 2 Food to add that Tradition to the Culture.
If a proposal has the [Cleanup] tag, it is known as a Cleanup Proposal. Cleanup Proposals ignore the “unless the Ape already has 2 Proposals pending, or has already made 3 Proposals that day” clause of the Proposals rule, and do not count as Proposals for the purposes of it. An Ape may not make more than two Cleanup Proposals per day.
If a Cleanup proposal would do anything other than fixing small errors, problems and layout issues in the ruleset, an Admin may fail it at any time.
Each Ape has Genetics, which is a list of six Genes, noted in the GNDT by as a list of the first two letters of the name of that Gene under a column named “Genetics” unless noted otherwise. For example: NoNoNoDeSp/In
The default Genetics is the one noted as NoNoNoBrSp/No.
The sixth Gene slot, separated by a slash, keeps track of an Ape’s non-inherited trait. This “Gene” slot defaults to No and can never be passed down to future generations. Non-inherited traits are not affected when an Ape Mutates.
The following are Genes and their effects:
- Nothing: This Gene does nothing.
- Speed: Positively affects the number of LA.
- Brawn: This Gene is involved in the Hunt action.
- Smell: Gain an additional Food when performing the Forage action.
- Deformed: Negatively affects the number of LA.
- Intelligence: This Gene is involved in the Intellect rules.
- Beautiful: This gene makes an ape look better
- Size: Male apes with this gene are considered to be Large.
- Charm: This Ape is considered to have one additional Food for each Intelligence, Brawn or Speed gene in their Genetics, and two extra Food if they are Large, for the purposes of calculating which Apes are Well-Fed.
The following is known as Mutating: randomly selecting one of the Genes of the thing which is Mutating, and setting it to be a randomly selected kind of Gene.
Some Genes are Legacy Marker genes. These occupy a slot in the Genetics of an Ape in the same way as other Genes, but are notated as an & symbol followed by two letters. Whenever an Ape is permitted or required to create a Legacy Marker, they add their own name (preceded by an & symbol) to the list of Genes in this rule, unless their name starts with the same two letters as an Ape who has already created a Legacy Marker, in which case they must instead add an & symbol followed by any two letters that are not used to denote the name of any other Gene when recorded in the GNDT, followed by their own name in brackets. That Ape is considered to own that Legacy Marker.
New Generation Events
If at least 72 hours have passed since the previous New Generation Event, any Ape may perform a New Generation Event as the following atomic action:-
- If there are no Fighting Apes, Increase the LA of the Neanderthals by DICE3 and skip to step five.
- Calculate the Ape Strength by summing the number of Brawn genes among all Fighting Apes and adding two for every Large Ape who is Fighting. If the Troop of Apes has the Weaponry Tradition in its culture, add one to the Ape Strength for each Fighting Ape. Calculate the Neanderthal Strength by multiplying the number of Brawn Genes they have by their LA. If the Neanderthals have the Weaponry Tradition, add one to the Neanderthal Strength for each of their LA.
- Take the absolute difference between the Ape Strength and the Neanderthal Strength. If the Ape Strength is greater than the Neanderthal Strength:
- Decrease the LA of the Neanderthals by the difference
- Increase the Legacy of each Fighting Ape by one
- Increase the Food of the Fighting Ape whose genes contributed the most to the Ape Strength by an amount equal to the difference between the Ape and Neanderthal Strengths. In case of a tie for greatest Strength contribution, distribute the increase in Food as evenly as possible among the tying Apes in question and ignore the remainder.
- If the Neanderthal Strength is greater than the Ape Strength:
- Set the Food of each Fighting Ape to zero.
- Increase the Legacy of the Neanderthals by 1.
- Mutate the Neanderthals.
- If there are any Traditions which have a Complexity equal to or lower than the number of the Neanderthals’ Intelligence Genes, and which the Neanderthals do not already have, give them a random Tradition from that set.
- Set the Food of the Neanderthals to the number of Genes in their Genetics which are not “Nothing”, then double it if they have the Agriculture Tradition.
- If the Neanderthals’ Food multiplied by their LA is higher than the total Food of all Apes, the Neanderthals gain 2 Legacy
- Set the Neanderthals’ LA to the total number of Apes
- Increase each Ape’s Food by the number of Beautiful Genes they have.
- If it is possible to do so: randomly select an Ape from the Well-Fed male Apes, then randomly select an Ape from the Well-Fed female Apes. If two Apes are chosen in this way, then they are the Progenitors for this Generation Event.
- If there are no Pregenitors, set all of the Ape’s Genetics to default and skip the next 3 steps of this action.
- Roll a DICE54321 in the GNDT
- For this step, ignore all Apes’ non-inherited traits and use only the first five Genes in all Apes’ Genetics. Using the page located at the following hyperlink https://jsfiddle.net/sn462coq/73/ (which is also located in the sidebar), fill out the form by putting the result of die in the previous step in the Random Seed box, the Genetics of one of the Progenitors in the Genetics A box, the Genetics of the other Progenitor in the Genetics B box and copy the names of unidle players from the sidebar into the Ape Names box, appending “Default” to the list.
- Press the Splice Genes button and set each Ape’s Genetics to the Genetics that appear to the right of their name in the output, appending “/No” to each Ape’s Genetics. Set the default Genetics to the Genetics that appears to the right of the text “Default”, appending “/No” to the Default Genetics.
- Increase the Legacies of this Event’s Progenitors by 1.
- The Food, LA and Battle Status of each Ape are set to default.
- For each ape, roll a DICE4. If a 1 is rolled for them there, that Ape Mutates.
- Divide the Apes into two equally sized groups, or into two groups where one group contains exactly one more Ape than the other, assigning Apes to these groups in a random manner. Then choose one group in a random manner and set the Genders of the Apes in it to Male, and set the Genders of the Apes in the other group to Female.
- For each Tradition in the Culture whose Complexity is higher than the Intellect of every Ape, remove that Tradition from the Culture.
- For each Ape, Increase their LA by 1 for each Speed gene they have. Decrease it by 1 for each Deformed gene they have. After this, if their LA is less than 1, set it to 1.
An Ape who does not have less Food than another Ape of the same gender is “Well-Fed”.
An Ape may spend 1 Legacy to select a Gene that was part of their own Genetics at the time of the most recent New Generation Event and add it to their current Genetics in the same Gene slot as it was last Generation.
The Neanderthals are a group of creatures that live across the valley. They are tracked as if they were an Ape in the GNDT, but do not otherwise count as an Ape.
The Neanderthals have Genetics, which is a list of five Genes, noted in the GNDT as a list of the first two letters of the name of each Gene in the Neanderthals’ “Genetics” column.
The Neanderthals have an amount of Food, tracked in the Neanderthals’ “Food” GNDT column. They also have an amount of Legacy, tracked in the Neanderthals’ “Legacy” GNDT column.
The Neanderthals have a number of Traditions, listed in this rule as follows: Weaponry.
The Neanderthals have a number of Lifetime Actions (LA for short) tracked in the Neanderthals’ “LA” GNDT column
If they have not done so since the most recent New Generation Event, any Ape may mark themselves as a Runt by setting their gender in the GNDT to “Runt”. If they do so, they may immediately change one of the slots in their Genetics to any Gene that is not in the same slot in any other Ape’s Genetics.
Special Case Rules can be active or inactive and default to active. The status of a Special Case rule is notated in the title of that rule ending in ”[X]” where X is the word Active or Inactive, denoting that Rule’s status. When a new dynasty is started, the Ascension Address may state any existing Special Case Rules that are set to inactive; any Special Case Rules not set in the Ascension Address become Active.
The text of Special Case Rules that are inactive shall be interpreted, for the purpose of play, to mean nothing.
Votable matters have zero or more tags. Tags are added by adding it to the title of a votable matter with the format “[X]” where [X] is the tag, for example “[Core] Wording Fix”. Votable Matters require the [Core] tag in order to make changes to the Core Rules, the [Special Case] tag in order to make changes to the Special Case Rules and the [Appendix] tag in order to make changes to the Appendix Rules. Votable Matters other than DoVs require the [Victory] tag in order to grant victory to an Ape.
Atomic Actions [Active]
When an Ape performs an Atomic Action, they must complete all its steps; they must complete them in order; and they may not take any other dynastic action until all such steps are complete. All of the steps of an Atomic Action are considered one action, as well as the steps of an Atomic Actions that is itself a step of a parent Atomic Action.
An Atomic Action may direct the performer to skip some of its steps, which the performer should do and in which case the skipped steps are considered completed for this rule.
If one or more steps of an Atomic Action were done incorrectly, the Ape must redo the Atomic Action. In redoing an Atomic Action, the Ape uses any legal steps that were already completed in the illegal Atomic Action and only redoes the illegal ones.
For instance if an Atomic Action consists of rolling a die in the GNDT and then doing steps based upon it’s result the Ape would have to reroll the die if they rolled the wrong one if the first place and any steps that depended upon the result of that die; however if all they did was take an illegal action later on, the die is still used in the redone action.
For the purposes of determining the ordering or legality of game actions the time of an Atomic Action shall be the time that it is completed. For Atomic Actions that are redone, the time of completion is the last redone step.
This rule cannot be overruled by the Dynastic Rules.
Seasonal Downtime [Active]
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”.
If there are fewer than five Apes, then BlogNomic is Dormant. While BlogNomic is Dormant, actions defined by dynastic rules may not be taken, and proposals may not be submitted.
No Orphan Variables [Active]
An Orphan Variable is a dynastic gamestate variable which has neither a location in which it’s tracked, nor a manner in which it it can be determined from other gamestate variables, specified in the Ruleset.
An Ape may not take any dynastic actions that are contingent on the specific value of an Orphan Variable.
Imperial Deferentials [Active]
If the Monolith has voted DEFERENTIAL on a proposal, that vote is instead considered to be valid and either FOR (if more Apes have voted FOR the proposal than have voted AGAINST it) or AGAINST (in all other cases).
Dynastic Distance [Active]
For the purposes of dynastic rules which do not deal with voting, The Monolith is not an Ape.
A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)
- "is able to"
- A blog comment published to the BlogNomic weblog at blognomic.com
- Core Proposal
- A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Apes.
- Daily Action
- If a game action is a Daily Action, each Ape able to perform it may take that action once each day, but not more than once every ten hours.
- Daily Communal Action
- A Daily Communal Action is a Daily Action that can only be performed by one Ape per day.
- References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 UTC, ending when the next day begins. It can never be 2 different days at the same instant.
- References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.
- Dynastic Proposal
- A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.
- Effective Vote Comment (EVC)
- A Mortal’s Effective Vote Comment with respect to a given Votable Matter means that Mortal’s Comment to that Votable Matter, if any, that contains that Mortal’s Vote on that Votable Matter.
- Flavour Text
- When posting a blog entry, an Ape 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. All GNDT columns that the Dynastic Rules explicitly mention are assumed to be Gamestate, as are all Wiki Pages that the Dynastic Rules explicitly mention except for dynastic histories and discussion pages.
- A blog post published to the BlogNomic weblog at blognomic.com
- Private Message
- A message sent via Blognomic’s Private Messages system at blognomic.com.
- Quorum of a subset of Apes is half the number of Apes in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Apes it is referring to, it is referring to a Quorum of all Apes.
- If used in a context of a Votable Matter, the word “Resolve” means to perform the act, as an Admin, of enacting or failing a Votable Matter. The world “Resolution” means then the act of doing so. If used in any other context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words
- Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.
- "is required to"
- "is recommended that"
- Sibling Rule
- Two rules are “siblings” of each other if they are both direct subrules of the same rule.
- The BlogNomic Slack is located at blognomic.slack.com. Apes may request an invite to the Slack while logged in by clicking the button in the sidebar.
- Slack Channel
- A Slack Channel is any channel on the BlogNomic Slack. To reference a Slack Channel, use a hash (#) followed by the name of that channel. (For example, #random.)
- Story Post
- A Story Post is an entry in the “Story Post” category.
- The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.
- A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.
- Table of Contents
- The directory of section headings that is generated by the MediaWiki software for most pages in the wiki.
- Table of Contents.
- 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, a DEF http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and a crossed-out circle http://blognomic.com/images/vote/seal.gif shall represent a vote to 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 Ape able to perform it may take that action once each week, but not more than once every twenty-four hours.
- Weekly Communal Action
- A Weekly Communal action is a Weekly Action that can only be performed by one Ape per week.
- The BlogNomic Wiki at http://wiki.blognomic.com
Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at http://blognomic.com. Any Ape may post to the blog at any time, but may only make official posts to the blog when the Ruleset allows it. Posts following the format specified by a rule are considered official posts. Any single official post cannot be of two different types of official post unless a rule explicitly states otherwise.
An official post may only be removed as allowed by the Ruleset. An official post may be altered by its author if it is less than two hours old and either no Ape has commented on it or (if it is a Votable Matter) if all comments on it contain no voting icons; 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. An official blog post that has the status of Enacted or Failed cannot change categories. An official blog post’s status may never be altered except in accordance with the rules that define that official post.
A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following two exceptions: Firstly, 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. Secondly, if a post by a New Ape is not in any category but follows the wording of a Proposal, in that it has written changes the gamestate and or ruleset, and if it has been posted for less than six hours, then any admin may change it to be in the Proposal category. A New Ape is defined as an Ape who has been an Ape for fewer than seven days or an Ape that has unidled in the past seven days after being idle for at least 3 months.
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 Ape may update any Ape's data via the GNDT, whenever the Ruleset permits it.
All updates to the GNDT are logged. For gamestate which is tracked in a specific place (such as the GNDT or a wiki page), any alteration of that gamestate as a result of a Mortal’s action is (and can only be) applied by editing that data in that place. One GNDT or wiki update may contain one or more alterations, or one alteration may be split over multiple updates, as long as it is clear what is happening and the alterations 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 Ape may correct the GNDT to comply with the Gamestate.
If an Ape 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, Apes are encouraged to raise a Call for Judgement instead. Apes shall be assigned a password for the GNDT when they join the Nomic.
The GNDT can be used to generate random results.
- The DICEN command can be used to generate a random number between 1 and N.
- The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
- The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
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 Ape 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.
If a number or other game variable is selected 'at random' or 'randomly' from a range of possible values, its value shall always be taken from a uniform probability distribution over the entire range of possible values, unless otherwise specified. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified. If a selection is explicitly specified as being “secretly” random, the Ape making this determination may do so using a private method of their choosing, instead of the GNDT.
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 Apes to transfer a numeric value only allows them to transfer that value from themselves to another Ape (of their choice unless otherwise stated).
- An Ape 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 game variable has no defined starting value, then that starting value is the nearest legal value to zero that it may take (for numerical variables, defaulting to positive if tied), blank (for a text string or list that may be blank), the alphabetically earliest legal text string it may take (for a text string which may not be blank, with the digits 0 through 9 considered to precede “A”), or the list which is alphabetically earliest from the set of lists with the fewest elements (for lists which may not be blank, and considering each list to be a single unpunctuated text string, with the digits 0 through 9 considered to precede “A”).
- Invalid values for game variables can never be used, even if the values stored in the GNDT remain valid. (for example, if X appears in a formula referring to a value that is a non-negative integer, X must be used as a non-negative integer)
- DICEN cannot be rolled in the GNDT if N is 22 or more digits long.
Rules and Proposals
- If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
- If a wiki page becomes gamestate as a result of a proposal enacting, that page shall - unless otherwise specified - be reverted to whatever state it was in at the time of that proposal's submission (and if the page did not exist at that time, it shall be blanked).
- Where a Proposal would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
- Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
- Unless otherwise specified, a new Dynastic rule shall be placed at the end of the Dynastic Rules.
- If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Ape A gains 1 point”), that step is ignored for the purposes of enactment. Once a proposal has been enacted, it can have no further direct effect on the gamestate.
- For the purpose of all rules, time in Blognomic is in UTC.
- All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
- Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.
- An Ape may not take more than one dynastic game action at the same time (excluding any actions which have been ongoing for more than three hours).
- Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.
- Within the ruleset, a word only refers to the name of an Ape if it is explicitly stated that it refers to an Ape's name.
- 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.
- Subrules can be referred to by a name which incorporates name of the rule they are a subrule of. Example: a subrule of the rule “Gin” is a “Gin Rule”, however the rule “Gin” is not a “Gin Rule” because it’s not a subrule of the rule “Gin”.
- When referring to a proposal, the name used in reference to a specific proposal may be simplified by not including braces and any text between the opening and closing braces. i.e. a proposal named “Changes [Core]” could instead be referred to by the name “Changes”.
- If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
- The Appendix has precedence over any Rule;
- A Dynastic Rule has precedence over a Core Rule, unless that Core Rule explicitly says it can’t be overruled by a Dynastic Rule;
- If both contradicting parts are Core Rules, or if both of them are Dynastic Rules, the part with more limited scope applies. (e.g. if the rules “Apes may Kick each other” and “Apes may not kick each other on Tuesdays” exist, and it is Tuesday, Apes may not Kick each other.)
- If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Apes may Punch a Spaceman on Friday” and “Apes may not Punch Spacemen on Friday”, then Apes may not Punch Spacemen on Friday.)
- Special Case Rules have equal precedence as Dynastic Rules, unless that Special Case Rule explicitly says it can’t be overruled by a Dynastic Rule.