Difference between revisions of "Ruleset"

From BlogNomic Wiki
Jump to navigation Jump to search
(→‎Recipes: enacting "A Gargantuan Massacre")
(Enacting "Shooting the Moon")
Line 2: Line 2:
  
 
<div style="padding:8px;background:#ddd;">
 
<div style="padding:8px;background:#ddd;">
 +
 
= Core Rules =
 
= Core Rules =
  
 
== Ruleset and Gamestate ==
 
== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Cooks 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.
+
This is the '''Ruleset''' for BlogNomic; all Tesserers 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.
 
The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.
  
Cooks 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”.
+
Tesserers 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 Tesserer may update it to do so.
  
== Cooks ==
+
== Tesserers ==
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 '''Cook'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Cook.
+
Any human may apply to join BlogNomic (if they are not already a Tesserer) 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 '''Tesserer'''. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Tesserer.
  
A Cook may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Cook may not rejoin the game within two weeks after having left. A Cook may only change their name as a result of a proposal approving the change.
+
A Tesserer may cease to be a Tesserer at any time by posting an entry to the BlogNomic weblog requesting such an action. A human who has ceased to be a Tesserer in this way may not become a Tesserer again within the following two weeks. A Tesserer may only change their name as a result of a proposal approving the change.
  
Some Cooks are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Cooks 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 Tesserers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Tesserers 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 Cooks===
+
===Idle Tesserers===
  
Some Cooks 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”, “Cooks”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Cooks are not counted as Cooks.
+
Some Tesserers 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”, “Tesserers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Tesserers are not counted as Tesserers.
  
If a Proposal contains a provision that targets a specifically named Idle Cook, then that Idle Cook is considered to be Unidle solely for the purposes of enacting that specific provision
+
If a Proposal contains a provision that targets a specifically named Idle Tesserer, then that Idle Tesserer is considered to be Unidle solely for the purposes of enacting that specific provision
  
When a Cook 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 Cook Idled in a different dynasty), the Cook is given the default value for new Cook, if such a value exists.
+
When a Tesserer 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 Tesserer Idled in a different dynasty), the Tesserer is given the default value for new Tesserer, if such a value exists.
  
An Admin may render a Cook Idle if that Cook has asked to become Idle in an entry or comment from the past four days, or if that Cook has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Cook if that Cook 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 Cook who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.
+
An Admin may render a Tesserer Idle if that Tesserer has asked to become Idle in an entry or comment from the past four days, or if that Tesserer has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Tesserer if that Tesserer 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 Tesserer who would be Unidled asked to become (or rendered themselves) Idle within the previous four days, and within the current dynasty.
  
Admins who are unidling themselves should, in their first EVC following each unidling, highlight their changed idle status and any changes to quorum to have come about as a result of it.
+
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.
  
 
== Dynasties ==
 
== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Cook, known as the Restaurant Manager. If there is no Restaurant Manager, the Dynasty is a Metadynasty.
+
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Tesserer, known as the Master. If there is no Master, the Dynasty is a Metadynasty.
  
 
== Votable Matters ==
 
== Votable Matters ==
A '''Votable Matter''' is a post which Cooks may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.
+
A '''Votable Matter''' is a post which Tesserers may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.
 +
 
 +
===Votes===
 +
Each Tesserer 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 Tesserer’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-Tesserer never has a Vote, even if they were a Tesserer previously and had cast a valid Vote.
 +
 
 +
If a Tesserer other than the Master casts a vote of DEFERENTIAL, then the Vote of DEFERENTIAL is an indication of confidence in the Master. When the Master 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 Master'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 Tesserers who are not voting AGAINST it is less than Quorum.
 +
* It has been open for voting for at least 48 hours is not Popular.
  
Each Cook 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 Cook’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-Cook never has a Vote, even if they were a Cook previously and had cast a valid Vote.
+
=== Enacting and Failing ===
  
 
Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.
 
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).
+
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). 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.
 
This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.
  
 
== Proposals ==
 
== Proposals ==
Any Cook may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Cook already has 2 Proposals pending, or has already made 3 Proposals that day).
+
Any Tesserer may submit a '''Proposal''' to change the Ruleset or Gamestate, by posting an entry in the “Proposal” category that describes those changes (unless the Tesserer already has 2 Proposals pending, or has already made 3 Proposals that day).
  
 
=== Special Proposal Voting ===
 
=== Special Proposal Voting ===
  
When a Cook 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 Restaurant Manager may use VETO as a voting icon to cast a Vote on a proposal; when the Restaurant Manager casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Restaurant Manager later changes their Vote.
+
When a Tesserer 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 Master may use VETO as a voting icon to cast a Vote on a proposal; when the Master casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Master later changes their Vote.
 
 
If a Cook other than the Restaurant Manager casts a vote of DEFERENTIAL on a Proposal, then the Vote of DEFERENTIAL is an indication of confidence in the Restaurant Manager. When the Restaurant Manager 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 Restaurant Manager's Vote for the purposes of other rules unless otherwise specified.
 
  
 
=== Resolution of Proposals ===
 
=== Resolution of Proposals ===
  
The oldest pending [[#Proposals|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:
+
The oldest Pending [[#Proposals|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 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 is Popular.
* 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.
+
* 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:
+
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.
 
* It has been Vetoed or Self-Killed.
* The number of Cooks 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.
 
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 ==
 
== Calls for Judgement ==
If two or more Cooks actively disagree as to the interpretation of the Ruleset, or if a Cook feels that an aspect of the game needs urgent attention, then any Cook may raise a '''Call for Judgement''' (abbreviated CfJ) by posting an entry in the “Call for Judgement” category.
+
If two or more Tesserers actively disagree as to the interpretation of the Ruleset, or if a Tesserer feels that an aspect of the game needs urgent attention, then any Tesserer 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.
+
A Pending CfJ may be Enacted by any Admin if all of the following are ture:
  
Any CfJ that specifies neither changes to the Gamestate or Ruleset nor corrections to any gamestate tracking entities may be failed by any Admin.
+
* 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.
 
This Rule may not be overruled by Dynastic Rules.
  
 
== Victory and Ascension ==
 
== Victory and Ascension ==
If a Cook (other than the Restaurant Manager) 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 a Tesserer (other than the Master) 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 “Cooks”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.
+
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 “Tesserers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.
  
Every Cook may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.
+
Every Tesserer 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:
+
A Pending DoV may be Enacted by any Admin 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 Restaurant Manager has Voted FOR it or it has no AGAINST Votes.
+
* It is Popular, it has been open for at least 12 hours, and either the Master 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 is Popular, and it has been open for at least 24 hours.
* 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:
+
A Pending DoV may be Failed by any Admin if any of the following are true:
  
* It has been open for voting for at least 12 hours, and the number of Cooks who are not voting AGAINST it is less than Quorum.
+
* It is Unpopular, and it has been open for at least 12 hours.
* 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 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 Cook who made the DoV as its Restaurant Manager. That Cook may pass this role to another Cook at this point by making a post to that effect, if they wish. The Hiatus continues until the new Restaurant Manager makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Restaurant Manager's chosen theme for the new Dynasty, and may optionally specify that the terms Cook and Restaurant Manager 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.
+
When a DoV is enacted, all other pending DoVs are failed, and a new Dynasty begins with the Tesserer who made the DoV as its Master. That Tesserer may pass this role to another Tesserer at this point by making a post to that effect, if they wish. The Hiatus continues until the new Master makes an '''Ascension Address''' by posting an entry in the “Ascension Address” category - this should specify the Master's chosen theme for the new Dynasty, and may optionally specify that the terms Tesserer and Master 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 Cook who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.
+
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 Tesserer 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.
 
This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but can be overruled in other matters.
  
 
== Fair Play ==
 
== 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 Cook'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.
+
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if a Tesserer'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 Tesserer within BlogNomic, and should announce publicly if they control both a non-Idle Tesserer and any Idle Tesserers.
 +
* A Tesserer 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 Tesserer should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
 +
* A Tesserer should not edit their own blog comments once posted, nor those of any other Tesserer.
 +
* A Tesserer should not edit the "Entry Date" field of a blog post.
 +
* A Tesserer should not make a DoV primarily to delay the game by putting it into Hiatus.
 +
* A Tesserer should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).
 +
* A Tesserer 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.
  
* A single person should not control more than one Cook within BlogNomic.
+
</div>
* A Cook 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 Cook should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
 
* A Cook should not edit their own blog comments once posted, nor those of any other Cook.
 
* A Cook should not edit the "Entry Date" field of a blog post.
 
* A Cook should not make a DoV primarily to delay the game by putting it into Hiatus.
 
* A Cook 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==
+
= Dynastic Rules=
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”.
+
 
 +
== Tessering ==
 +
 
 +
Every Tesserer has a value of “Power” tracked in the GNDT, which defaults to 0. A Tesser that has joined or unidled and has not unidle previously this dynasty gains power equal to ([the sum of all other Tessers’ power] + [2 * the number of shards])/[the number of Tessers - 1]. As a weekly communal action, a Tesserer may add 5 power to each Tesserer.
 +
 
 +
Anytime a Tesserer publishes a Story Post which is not a Combo, they may, in the title, put the following tag: [Tessered X], where X is a number less than or equal to their power. Any actions described in such a post will not be performed: instead, the text of the post will be added to a named “Tessers” of a Wiki page named “[[The Tesseract]]”. After X days have passed the action(s) must be performed following the rules of an Atomic Action, and the text removed form the wiki page. If the actions are not performed within 48 hours after X days have passed, the Instability of the Tesseract increases by X. A Tesserer may only have two such posts at a time.
 +
 
 +
The sum of the contents of a story post with the [Tessered X] tag is called a “Tessered Act”.
 +
 
 +
===Boosting===
 +
 
 +
A Tesserer may “Boost” the Tesseract by paying 2 power. This reduces the amount of power than must be paid in each unfullfilled Tessered Act by 1. The amount of power a Tessered Act’s cost is reduced by is tracked on The Tesseract wiki page.
 +
 
 +
== Tesseract ==
 +
 
 +
Also tracked on the Wiki page the Tesseract is a value call “Power Level” which starts a 0. Every time a post with the tag [Tessered X] is posted, the Power Level goes up by X.<br>
 +
 
 +
The Tesseract has an Instability, which starts at 0, tracked on its wiki page.  If the instability of the Tesseract rises above 5, all shards with the same affinity as the orientation of the Tesseract are removed from their owners and considered “Destroyed”. The instability of the tesseract is then set to 0. The orientation of the tesseract is set as determined by a DICE8 roll in the GNDT, where 1 is North, 2 is South, 3 is East, 4 is West, 5 is Up, 6 is Down, 7 is Ana, and 8 is Kata.
 +
 
 +
===Orientation===
 +
The Tesseract has 8 cells, named after the direction they initially are facing : North, South, East, West, Up, Down, Ana, Kata.
 +
 
 +
The Tesseract has an Orientation, tracked on its wiki page, that corresponds to the name of the cell it is resting on. The initial Orientation of the Tesseract is Down.
 +
 
 +
Each pair of opposing cells has an associated Affinity:
 +
*Water: North-South
 +
*Fire: East-West
 +
*Nature: Up-Down
 +
*Void: Ana-Kata
 +
 
 +
A Tesserer may spend a Shard to change the orienation of the Tesseract to one that has the same affinity as the Shard. This action is called “rotating” the Tesseract.
 +
 
 +
== Affinity ==
 +
 
 +
Each Tesser has an Affinity (or none), which can be one of the following:
 +
* Water: A Water Tesser cannot make proposals with the word “Water” in it.
 +
* Fire: A Fire Tesser cannot make proposals with the word “Fire” in it.
 +
* Nature: A Nature Tesser cannot make proposals with the word “Nature” in it.<br>
 +
* Void: A Void Tesser cannot make proposals with the word “Void” in it.
 +
 
 +
A Tesser’s Affinity is tracked in the GNDT, defaults to “none”, and if a Tesser hasn’t done so in this dynasty, they can change their Affinity from none to a different one.
 +
 
 +
Each Tesser has an amount of Shards, which are a magically created resource. Shards have an affinity, which is a Tesser Affinity. Each Tesser’s Shards are tracked in the GNDT by a capital letter of their affinity (FFWN for 2 Fire shards, 1 Water shards and 1 Nature Shard, for example). A Tesser can hold as many shards as they have Power. A Tesser can pay 3 Power to make a Shard of their Affinity. Tessers can freely give their Shards to other Tessers if that Tesser would be able to hold them. Tessers can freely discard their own Shards.
 +
 
 +
Tesserers can legally make proposals with their alignment with them, however, they have stricter requirements. They may pass only if the number of votes against equals zero.<br>
 +
Void and Nature are opposites.
 +
 
 +
===Void===
 +
Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added
 +
 
 +
===Fire===
 +
Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added
 +
 
 +
===Water===
 +
Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added
 +
 
 +
 
 +
===Nature===
 +
Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added
 +
 
 +
==Synonyms==
 +
“Tesser” and “Tesserer” are synonyms.
 +
 
 +
==Codices==
 +
The following comes from fragments (believed to be Folio 2) from The Fourth Orthocodex of G. Ray, Master Emeritus in Aeternum:<br>
 +
<blockquote>Each pair of different affinities has its own Face Action; each with a shorthand Symbol:<br>
 +
- Nature/Fire: Radiance (☀)<br>
 +
- Nature/Water: Abundance (♾)<br>
 +
- Water/Fire: Transition (♻)<br>
 +
- Water/Void: Carving (❖) [*, +]<br>
 +
- Fire/Void: Destruction (✖) [*]<br>
 +
- Nature/Void: Opposition (◑) [*]<br>
 +
 
 +
[+] see Folio 7 for discussion on naming of this Face Action.<br>
 +
[*] see Folio 9 for derivation of the symbology for these Face Actions.<br>
 +
</blockquote>
 +
The Fourth Orthocodex may be cited in brief as 'R4'.
 +
Text from R4 is not considered to be rules that Tesserers obey, unless otherwise specified.
 +
 
 +
 
 +
This footnote is considered by scholars to come from the Octocodex written by O. Sedecim, Second Corner. This is one of the few remaining fragments after O. Sedecim accidentally traveled through Interim. The following footnote is considered ruletext.
 +
<blockquote>
 +
A Tesser can perform Face Action by having the affinities that correspond to that Face Action participating and spending power equal to the number of affinities of the Face Action which don't match the Tessers' affinity. Participating affinities are the affinities of any Tessers that help in that action as well as the affinities of shards that participating Tessers possess; in case two or more Tessers perform a Face Action, they both pay this cost calculated with their own affinity.
 +
</blockquote>
 +
The Octocodex may be cited in brief as ‘O8’.
 +
Text from O8 is not considered to be rules that Tesserers obey, unless otherwise specified.
 +
 
 +
The following letter draft is suspected to be made by M. Opus, Archphilosopher Primo of the New Order and is considered ruletext:
 +
 
 +
<blockquote>Gee-whiz, Seddy, things have been crazy lately huh? Man. I don't know how I did this, but there's like crazy meta-meta-metaphysical arcanopotential in the loopgrinder of sizzleslash. Yeah, I know, crazy. Now, I'm not entirely sure this will work for you all the time (it has like, eh, 10% success rate?), but I'll let you all know just in case you want to try pulling it off.
  
</div>
+
If you've got like, eight of the same kind of shard, which isn't of the kind you're attuned to - you know, your affinity - you can use any spell. <em>Any spell</em>. Yep. But you've got to lose all of them in the process, but hey, if it works, it works. Oh, and if you fail, your Power kind of becomes, well. Null. Zero. Nada. I guess you can figure out from that why I'm retiring.
  
= Dynastic Rules =
+
So, how are the children? Last I heard, little *smudge* -s already tessering his fir- *smudge*</blockquote>
  
==Ingredients==
+
The rest of the letter has been lost to the ages.
  
Ingredients are items from the following list. An Ingredient’s properties are chosen by the Restaurant Manager, are fixed, and may be listed in brackets after their name in this list. (If an Ingredient has no properties listed, the Restaurant Manager should update this rule to include them.)
+
==Spells==
* Minced Meat (Sweetness 1, Sourness 0, Umami 5, Spicyness 2)
 
* Red Pepperoni (Sweetness 1, Sourness 0, Umami 0, Spicyness 5, Vegetarian)
 
* Tomato (Sweetness 3, Sourness 3, Umami 2, Spicyness 1, Vegetarian)
 
* Eggplant (Sweetness 2, Sourness 1, Umami 3, Spicyness 0, Vegetarian)
 
* Sugar (Sweetness 5, Sourness 1, Umami 3, Spicyness 0, Vegetarian)
 
* Lemon (Sweetness 4, Sourness 5, Umami 0, Spicyness 0, Vegetarian)
 
* Potato (Sweetness 3, Sourness 0, Umami 1, Spicyness 0, Vegetarian)
 
  
==Taste Buds==
+
By spending the cost in shards in brackets (noted here in Affinity initials, just like how they’re recorded in the GNDT, with an 'A' standing for any shard), you can perform the following spells:
  
Every Ingredient has the following Valued Properties with integer values from 0 to 5::
+
* [FWNV] Albedo: Gain 3 shards of affinities of your choice.
* Sweetness
+
* [FWNV] Nigredo: Destroy 3 shards of your choice.
* Sourness
+
*[V] Null and Void: Remove one tessered act of your choice from the list of tessered acts on the wiki page.
* Umami
+
*[N] Growth: Add one to the boost of any and all Tessered Acts on the wiki page you specify when casting this spell
* Spicyness
+
*[F] Heat: Boost all tessered Acts on the Tesseract wiki page by two and add 1 the the instability of the tesseract
 +
*[W] Eddy: change the ownership of a Tessered act to a Tesserer who is not yourself and who has less than two tessered acts. the boost of the Tessered Act is reduced by one
 +
*[FFFVVV] Summon Phoenix: If you have the least Power, switch your Power with that of who has the most Power.
 +
*[NNNWWW] Summon Leviathan: If you have the most Power, all other Tessers lose a shard of your choice and you gain that shard.
 +
*[A] Ashes to Ashes: Gain 2 power.
 +
*[P] Negate: Choose a Tesser other than yourself. If they have a shard of your affinity they lose it and gain a shard of their affinity and you gain a shard of your affinity.
 +
*[O] Gamble: You must wait until the Tesseract’s orientation changes before casting this spell again. Roll a DICE2, on a 1 gain a shard of the Tesseract’s orientation after it changes.
  
An Ingredient may or may not have one or more of the following Additional Properties:
+
<br>Y stands for a shard that is the same affinity as the performer. P stands for a shard that is the opposite affinity of the performer. O stands for a shard that is the same affinity as the Tesseract’s current position.
* Vegetarian
 
  
==Recipes==
+
===Archmaster’s Watch===
 +
Each Tesser is being watched by the Archmaster or not, and this is tracked in the GNDT. The Archmaster can only watch one Tesser at a time. A Tesser that is being Watched by the Archmaster cannot perform Forbidden Spells but gain 1 more Power whenever they gain Power as the Archmaster grants them extra tutelage (this doesn’t affect gains provided by this rule).
  
A Recipe consists of a name, a list of three to six Packages, and a list of between one and six Steps in sequence. A Step may either be: adding a quantity of one of the Package types listed in the Recipe, or using a piece of Equipment. The first step of a Recipe must always add a Package type.
+
A Tesser can pay 2 Power to Point to Someone and change who the Archmaster is watching to someone else other than themselves.
  
A Step is considered to add a quantity of a Package if it mentions the name and quantity of that Package; if the text of a Step also includes one (and only one) of the following verbs, then that Step has the corresponding effect when applied:
+
All Spells with the string “Summon” in them are Forbidden.
  
*'''Chop''': If this Step would add any Spiciness to the Recipe, it adds one additional Spiciness.
+
===Crafts===
*'''Reduce''': If this Step would add any Umami to the Recipe, it adds one additional Umami.
+
If the Tesseract’s Orientation is that of your Affinity, you make a Craft by paying the appropriate shard cost in brackets as listed here according to the usual Spell shard cost nomenclature. A Tesserer can hold 1 Craft per 10 Power they have. The Crafts a Tesserer has is noted in the GNDT in its own column titled “Crafts”. Crafts, the ability you gain for having them and their shard cost are the following:
*'''Drain''': If this Step would add any Sweetness to the Recipe, it adds one less Sweetness.
 
*'''Sprinkle''': If this Step would add any Sourness to the Recipe, it adds one less Sourness.
 
*'''Garnish''': This Step does not affect the Valued Properties of the Recipe (but still affects Additional Properties).
 
  
Recipes have the same Valued Properties as Ingredients do but with integer values from 0 to 10. These are calculated by starting them all at zero, then applying the Recipe’s Steps in sequence. When a Step adds a quantity of a Package, it increases the Valued Properties of the Recipe by the Valued Properties of the Ingredient that corresponds to that Package, multiplied by the quantity being added. When a Step uses a piece of Equipment, the effect of that Equipment is applied to the Recipe (unless the Cook who posted the Recipe does not possess that piece of Equipment at this time). If a Step would reduce a Recipe’s Valued Property below zero, it instead becomes zero; if it would increase a Recipe’s Valued Property above 10, it instead becomes 10.
+
[FW] Alcohol: The Tesserer who has this item can GET WASTED and optionally brag about how they don’t remember what happened last night. They lose all of their Shards and their Power becomes 5.
 +
[VN] Pesticide: A Tesserer with this item cannot have Nature Shards but each time they make a Void shard, they may roll a 1d3. If they roll a 1 with that, they gain another Void shard.
  
A Recipe has the Additional Property of Vegetarian until a Step causes a non-Vegetarian Ingredient to be added to it, at which point it ceases to be Vegetarian.
+
==Face Actions==
 +
This is a list of Face Actions, their effects and conditions.
 +
*Abundance: This may only be performed if the Instability is at 0. Every Tesser gains 5 power. The Tessers which participate also gain extra power equal to what they spent to perform this action. It is a daily action.
 +
*Radiance: Make a Tessered post that uses the power of the Tesseract as the maximum X value instead of your own power.
  
==Review==
+
==Trade==
 +
A Tesser may make a Trade Story post by putting the [Trade] tag in it’s title. In that post the author details a specific Tesser and they state what they want to trade, naming the amount and what it is. If within 2 days the named Tesser has accepted, indicated by commenting “SOLD” in the relevant post, the Tessers swap ownership of the detailed items.
  
The Restaurant Manager may post a Review if one has not been posted in the previous 6 days. A review is a Story Post that has the word “Review” in its title. In the Review he has to announce the name of the new Reviewer. He also has to announce how the last Reviewer rated the Entry Recipes of each Cook. Each Cook may post Recipes as comments beneath the newest Review blogpost. The last such post of each Cook is called the Entry Recipe and is rated in the next Review.
+
==Shards==
 +
A Tesser that has one of each type of shard may spend one power to commune with the Tesseract.<br>
 +
Each Tesser has an amount of Shards, which are a magically created resource. Shards have an affinity, which is a Tesser Affinity. Each Tesser’s Shards are tracked in the GNDT by a capital letter of their affinity (FFWN for 2 Fire shards, 1 Water shards and 1 Nature Shard, for example). A Tesser can hold as many shards as they have Power. A Tesser can pay 3 Power to make a Shard of their Affinity. Tessers can freely give their Shards to other Tessers if that Tesser would be able to hold them. Tessers can freely discard their own Shards.<br>
  
When the Restaurant Manager posts a Review, if any Cooks used Consumable Equipment in their Recipes, those Consumable Equipments are removed from those Cooks.
+
==Merit==
 +
The Tesserer named Diabecko has achieved victory.
  
===Interviews===
+
<!-- RULES GO ABOVE THIS COMMENT. DO NOT DELETE THE NEXT LINE WHEN CLEARING THE RULES FOR A NEW DYNASTY. --><br/>
 +
<div style="padding:8px;background:#bbb;">
  
When posting a Review, the Restaurant manager should disclose one of the Characteristics (a single Sweet Spot, Vegetarianism, or Favourite Ingredient if appliable) of the next Reviewer. They should pick which characteristic to reveal at random among the characteristics they have not yet revealed this way.
+
= Special Case =
 +
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.
  
==Equipment==
+
Special Case Rules that are inactive do not have an effect on the gamestate aside from existing as text in the ruleset.
  
Each piece of Equipment may have an effect on a Recipe, listed in brackets after the item’s name (in both the list and the inventories) on the [[Cooking Equipment]] page. By default, a piece of Equipment has no effect. Valid effects are:-
+
==Combos [Active]==
 +
Anytime that a Tesserer wants to do 5 or more actions within an hour they may choose in lieu of doing all of those actions separately, which potentially causes confusion as to what is happening, to make a “Combo” blog post that cannot be edited after posting. The gamestate may be changed to reflect the results of the Combo once all of the actions are completed.
  
* '''+X Property''' (where X is a number from 1 to 3 and Property is any Valued Property)
+
A Combo post is a numbered list of the actions taken, the first action is #1 each subsequent number of actions is increased by one. Each action and the portion of the gamestate changed from that action are kept on their own line. An Atomic action has lettering of its steps, refer to the example and note the curly braces vs the parenthesis.
* '''-X Property''' (where X is a number from 1 to 3 and Property is any Valued Property)
 
* '''Property becomes zero''' (where Property is any Valued Property)
 
* '''Property is doubled''' (where Property is any Valued Property)
 
  
If a Cook possesses a piece of Equipment which has no effect (the “Mystery” Equipment), they may discard any single piece of Equipment they Possess to give the Mystery Equipment any legal effect. (This effect applies to all instances of that Equipment possessed by Cooks.) If a Cook possesses no Equipment, they may gain any ten pieces of Equipment, so long as each gained piece has no effect.
+
Example Combo
 +
*1 [action one] ([gamestate before action] -> [gamestate after action])
 +
*2 [action two] ([gamestate before action] -> [gamestate after action])
 +
*3 [atomic action] {[gamestate before atomic action]}
 +
*3a [first atomic substep] ([gamestate before substep] -> [gamestate after substep])
 +
*3b [second atomic substep] ([gamestate before substep] -> [gamestate after substep]) {[gamestate after atomic action]}
 +
*4 [action four] ([gamestate before action] -> [gamestate after action])
 +
*etcetera . . .
  
==Supply chain==
+
If any actions require a die roll or other random event that is visible to the public, Tesserers must make those rolls before posting the combo with a note stating which step the roll is for and what action they are taking and the title of their Combo. Tesserers may not make multiple rolls in the GNDT for the same step. Tesserers cannot have two or more rolls in the GNDT with Combo titles that are different unless all but one of the Combo titles have been posted and include that roll.
Due to a mix-up in shipping, all the Ingredients currently being supplied to the restaurant are of foreign and mysterious origin. These are the labels on the Packages currently in the restaurant’s inventory:
 
  
*Shouting Man
+
Each action of a Combo happens in their own second, substeps of an Atomic Action happen all at the same second as the parent step. The first action happens at the time the Combo is posted.
*Coy Sun
 
*String Of Numbers
 
*The Bee
 
*Exploding Chair
 
*Girl On Bicycle
 
*Melted Cube
 
*Blushing Fork
 
*Shiny Shoes
 
*Boy With Hedgehog
 
  
Each type of Ingredient corresponds to at least one Package; more than one Package may correspond to the same Ingredient. The Restaurant Manager shall maintain a private list of these correspondences, which are fixed.
+
If there is a mistake in the summary of the gamestate in a combo and that mistake doesn’t make it impossible for the stated actions to have happened, the author of that combo may correct those mistakes by making a comment along the format “[# of step]: [corrected gamestate summary]”.
  
==The Reviewers==
+
==Tags [Active]==
There are six Reviewers:
+
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, 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 a Tesserer.
  
* Antonio Fusilli
+
==Atomic Actions [Active]==
* Bruce Haggis
 
* Chiaki Ramen
 
* Dominique Labaguette
 
* Esmeralda Paella
 
* Mad-Tongue Moody
 
  
Some Reviewers are Special. Reviewers who are not Special are Regular.
+
When a Tesserer performs an Atomic Action, they must complete all its steps; they must complete them in order; and they may not take any other action defined in the Ruleset until all such steps are complete. In addition, the Tesserer performing an Atomic Action performs its steps as quickly as they are able.
Each Reviewer has a Sweet Spot for each of the existing Valued Properties. A Sweet Spot is an integer comprised between 0 and 10 included. Each Reviewer may be Vegetarian. Each Regular Reviewer has one Favourite Ingredient, which is one of the Ingredients listed in rule Ingredients. All the characteristics of the Regular Reviewers (Sweet Spots, Vegetarianism, Favourite Ingredient) are fixed and they shall be kept track of by the Restaurant Manager, who should reveal them only when allowed by the Ruleset. If one or more of a Reviewer’s characteristics has not been determined yet, the Restaurant Manager may and should privately determine it using a method of their choice.
 
Mad-Tongue Moody is a Special Reviewer. His Characteristics are well known to the staff of every Restaurant in Town, and they are:
 
* All his Sweet Spots are 10
 
* He is not Vegetarian.
 
  
==Fame==
+
If one or more steps of an Atomic Action were done incorrectly, the Tesserer must redo the Atomic Action. In redoing an Atomic Action, the Tesserer uses any legal steps that were already completed in the illegal Atomic Action and only redoes the illegal ones.
Each Cook has a “References” field, tracked as a string in the GNDT, consisting in the first letters of the names of the Reviewers that have ever awarded that Cook a 5-star rating.
 
  
==Ratings==
+
For instance if an Atomic Action consists of rolling a die in the GNDT and then doing steps based upon it’s result the Tesserer 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.
  
A rating is a String comprised of exactly 5 characters, that can be any combination of plus signs (+), minus signs (-), or asterisks (*) (alias: Stars). Possible spacing and the order of characters in a Rating are irrelevant, and should be kept consistent between ratings (eg: by putting all the asterisks fist and all pluses at the end).
+
If the Atomic Action was illegal due to a die that was wrong in the GNDT (for example, rolling a 1 on a DICE6 gives that Tesserer a point and the rest do nothing and the Tesserer rolls a DICE5 in the first one) and in redoing the Atomic Action they get the same effect as before (i.e. rolling an incorrect die and getting result X but then rolling the correct die and still getting result X) then the steps that depended upon that result are valid and don’t need to be redone. Steps that depend upon multiple dice which were done incorrectly must have each incorrect die have the same effect to be considered valid.
  
The Restaurant Manager shall follow some set rules on how to determine the Rating based on the Recipe and on the Characteristics of the current Reviewer. These rules are applied in the following order and are as follows:
+
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.
  
*1. The Rating defaults to - - - - -.
+
==Seasonal Downtime [Active]==
*2. For each Valued Property of the recipe that is exactly equal to the Reviewer’s Sweet Spot for that Valued Property, one minus is changed to a Star.
+
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”.
*3. For each Valued Property of the recipe that exceeds the Reviewer’s Sweet Spot for that Valued Property, one minus is changed to a Plus.
 
*4. If the Recipe contains the Reviewer’s Favourite Ingredient and the Rating contains 4 or more Stars, set the Rating to * * * * *.
 
*4. If the Recipe contains the Reviewer’s Favourite Ingredient and the Rating contains at least one Plus, one Plus is changed to a Star.
 
*6. If the Recipe does not have the Additional Property Vegetarian and the Reviewer is a Vegetarian, replace all but two Stars with Minuses.
 
  
<div style="padding:8px;background:#ddd;"> <!-- DO NOT DELETE THIS LINE WHEN CLEARING THE RULES FOR A NEW DYNASTY -->
+
</div>
 +
<div style="padding:8px;background:#ddd;">
  
 
= Appendix =
 
= Appendix =
Line 242: Line 341:
  
 
;Core Proposal
 
;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 Cooks.
+
: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 Tesserers.
  
 
;Daily Action
 
;Daily Action
:If a game action is a Daily Action, each Cook able to perform it may take that action once each day, but not more than once every ten hours.
+
:If a game action is a Daily Action, each Tesserer 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 Tesserer per day.
  
 
;Day
 
;Day
Line 257: Line 359:
  
 
;Effective Vote Comment (EVC)
 
;Effective Vote Comment (EVC)
:A Cook’s Effective Vote Comment with respect to a given Votable Matter means that Cook’s Comment to that Votable Matter, if any, that contains that Cook’s Vote on that Votable Matter.
+
:A Tesserer’s Effective Vote Comment with respect to a given Votable Matter means that Tesserer’s Comment to that Votable Matter, if any, that contains that Tesserer’s Vote on that Votable Matter.
  
 
;Flavour Text
 
;Flavour Text
:When posting a blog entry, a Cook 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.
+
:When posting a blog entry, a Tesserer 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
 
;Gamestate
:Any information which the Ruleset regulates the alteration of, including all Wiki Pages, or GNDT columns, which the Dynastic Rules explicitly mention.
+
: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.
 
 
;IRC Channel
 
:The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).
 
  
 
;May
 
;May
Line 281: Line 380:
  
 
;Quorum
 
;Quorum
:Quorum of a subset of Cooks is half the number of Cooks in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Cooks it is referring to, it is referring to a Quorum of all Cooks.
+
:Quorum of a subset of Tesserers is half the number of Tesserers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Tesserers it is referring to, it is referring to a Quorum of all Tesserers.
  
 
;Resolve/Resolution
 
;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
+
: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
  
 
;Rule
 
;Rule
Line 297: Line 396:
 
;Sibling Rule
 
;Sibling Rule
 
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.
 
:Two rules are “siblings” of each other if they are both direct subrules of the same rule.
 +
 +
;Slack
 +
:The BlogNomic Slack is located at blognomic.slack.com. Tesserers 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
 
;Story Post
Line 306: Line 411:
 
;Subrule
 
;Subrule
 
:A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.
 
: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.
 +
 +
;TOC: Table of Contents.
  
 
;Vote
 
;Vote
Line 317: Line 426:
  
 
;Weekly Action
 
;Weekly Action
:If a game action is a Weekly Action, each Cook able to perform it may take that action once each week, but not more than once every twenty-four hours.
+
:If a game action is a Weekly Action, each Tesserer able to perform it may take that action once each week, but not more than once every twenty-four hours.
  
 
;Weekly Communal Action
 
;Weekly Communal Action
:A Weekly Communal action is a Weekly Action that can only be performed by one Cook per week.  
+
:A Weekly Communal action is a Weekly Action that can only be performed by one Tesserer per week.  
  
 
;Wiki
 
;Wiki
Line 327: Line 436:
 
== Gamestate Tracking ==
 
== 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 http://blognomic.com]. Any Cook may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|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.
+
Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [http://blognomic.com http://blognomic.com]. Any Tesserer may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|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.
  
If no Cook has commented on it, or if the only comments on it begin with “Note:” and contain no voting icons, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must be changed to reflect its status.
+
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 six hours old and either no Tesserer 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.
  
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.
+
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 Tesserer who has been a Tesserer for fewer than seven days contains the word “Proposal” in its title, but is not a Proposal, and if it has been posted for less than an hour, then any admin may change it to be in the Proposal category.
  
Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Cook may update any Cook's data via the GNDT, whenever the Ruleset permits it.
+
Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at [http://blognomic.com/gndt/generic.cgi?nomic=blog http://blognomic.com/gndt/generic.cgi?nomic=blog]. Any Tesserer may update any Tesserer'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 Cook may correct the GNDT to comply with the Gamestate.
+
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 Tesserer’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 Tesserer may correct the GNDT to comply with the Gamestate.
  
If a Cook 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, Cooks are encouraged to raise a Call for Judgement instead.
+
If a Tesserer 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, Tesserers are encouraged to raise a Call for Judgement instead.
Cooks shall be assigned a password for the GNDT when they join the Nomic.
+
Tesserers shall be assigned a password for the GNDT when they join the Nomic.
  
 
=== Random Generators ===
 
=== Random Generators ===
Line 346: Line 456:
 
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
 
* 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 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 Cook 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.
+
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 a Tesserer 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 Tesserer making this determination may do so using a private method of their choosing, instead of the GNDT.
  
 
==Clarifications==
 
==Clarifications==
Line 356: Line 467:
 
* Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
 
* 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.
 
* 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 Cooks to transfer a numeric value only allows them to transfer that value from themselves to another Cook (of their choice unless otherwise stated).
+
* 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 Tesserers to transfer a numeric value only allows them to transfer that value from themselves to another Tesserer (of their choice unless otherwise stated).
* A Cook 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.
+
* A Tesserer 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 rule implies that the result of any calculation should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the calculation is instead the result rounded towards 0.
* If a number or other game variable is selected 'at random' or 'randomly' from a range of possible values, its value shall always be taken from a uniform probability distribution over the entire range of possible values, unless otherwise specified. This value must be determined by an appropriate DICE roll in the GNDT, unless otherwise specified.
 
 
* If a game variable has no defined starting value, 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”).
 
* 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)
 
* 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===
 
===Rules and Proposals===
Line 369: Line 480:
 
* Rules which trigger upon the Resolution of a Votable Matter are the responsibility of the Admin who Resolves it.
 
* 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.
 
* 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”.
+
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Tesserer 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.
* The names of rules are not themselves rule text and have no effect other than being rule names.
 
* If the admin enacting a proposal reaches a step which cannot be applied immediately (eg. “two days after this proposal enacts, Cook 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.
 
  
 
===Time===
 
===Time===
Line 382: Line 491:
  
 
===Names===
 
===Names===
* Within the ruleset, a word only refers to the name of a Cook if it is explicitly stated that it refers to a Cook's name.
+
* Within the ruleset, a word only refers to the name of a Tesserer if it is explicitly stated that it refers to a Tesserer'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”.
  
 
===Prioritisation===
 
===Prioritisation===
Line 388: Line 501:
 
# The Appendix has precedence over any Rule;
 
# 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;
 
# 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 “Cooks may Kick each other” and “Cooks may not kick each other on Tuesdays” exist, and it is Tuesday, Cooks may not Kick each other.)
+
# 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 “Tesserers may Kick each other” and “Tesserers may not kick each other on Tuesdays” exist, and it is Tuesday, Tesserers may not Kick each other.)
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Cooks may Punch a Spaceman on Friday” and “Cooks may not Punch Spacemen on Friday”, then Cooks may not Punch Spacemen on Friday.)
+
# If two parts with the same scope contradict each other, the negative rule applies. (e.g. with “Tesserers may Punch a Spaceman on Friday” and “Tesserers may not Punch Spacemen on Friday”, then Tesserers 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.
  
 
</div>
 
</div>

Revision as of 20:45, 10 December 2017

Core Rules

Ruleset and Gamestate

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

Tesserers 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 Tesserer may update it to do so.

Tesserers

Any human may apply to join BlogNomic (if they are not already a Tesserer) 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 Tesserer. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Tesserer.

A Tesserer may cease to be a Tesserer at any time by posting an entry to the BlogNomic weblog requesting such an action. A human who has ceased to be a Tesserer in this way may not become a Tesserer again within the following two weeks. A Tesserer may only change their name as a result of a proposal approving the change.

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

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

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

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

An Admin may render a Tesserer Idle if that Tesserer has asked to become Idle in an entry or comment from the past four days, or if that Tesserer has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so. An Admin may Unidle a Tesserer if that Tesserer 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 Tesserer 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.

Dynasties

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

Votable Matters

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

Votes

Each Tesserer 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 Tesserer’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-Tesserer never has a Vote, even if they were a Tesserer previously and had cast a valid Vote.

If a Tesserer other than the Master casts a vote of DEFERENTIAL, then the Vote of DEFERENTIAL is an indication of confidence in the Master. When the Master 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 Master'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 Tesserers who are not voting AGAINST it is less than Quorum.
  • It has been open for voting for at least 48 hours 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 must also mark their name, and 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.

Proposals

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

Special Proposal Voting

When a Tesserer 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 Master may use VETO as a voting icon to cast a Vote on a proposal; when the Master casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Master 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 Tesserers actively disagree as to the interpretation of the Ruleset, or if a Tesserer feels that an aspect of the game needs urgent attention, then any Tesserer 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 a Tesserer (other than the Master) 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 “Tesserers”, “Votable Matters”, “Calls for Judgement”, “Gamestate Tracking” and “Victory and Ascension”.

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

Dynastic Rules

Tessering

Every Tesserer has a value of “Power” tracked in the GNDT, which defaults to 0. A Tesser that has joined or unidled and has not unidle previously this dynasty gains power equal to ([the sum of all other Tessers’ power] + [2 * the number of shards])/[the number of Tessers - 1]. As a weekly communal action, a Tesserer may add 5 power to each Tesserer.

Anytime a Tesserer publishes a Story Post which is not a Combo, they may, in the title, put the following tag: [Tessered X], where X is a number less than or equal to their power. Any actions described in such a post will not be performed: instead, the text of the post will be added to a named “Tessers” of a Wiki page named “The Tesseract”. After X days have passed the action(s) must be performed following the rules of an Atomic Action, and the text removed form the wiki page. If the actions are not performed within 48 hours after X days have passed, the Instability of the Tesseract increases by X. A Tesserer may only have two such posts at a time.

The sum of the contents of a story post with the [Tessered X] tag is called a “Tessered Act”.

Boosting

A Tesserer may “Boost” the Tesseract by paying 2 power. This reduces the amount of power than must be paid in each unfullfilled Tessered Act by 1. The amount of power a Tessered Act’s cost is reduced by is tracked on The Tesseract wiki page.

Tesseract

Also tracked on the Wiki page the Tesseract is a value call “Power Level” which starts a 0. Every time a post with the tag [Tessered X] is posted, the Power Level goes up by X.

The Tesseract has an Instability, which starts at 0, tracked on its wiki page. If the instability of the Tesseract rises above 5, all shards with the same affinity as the orientation of the Tesseract are removed from their owners and considered “Destroyed”. The instability of the tesseract is then set to 0. The orientation of the tesseract is set as determined by a DICE8 roll in the GNDT, where 1 is North, 2 is South, 3 is East, 4 is West, 5 is Up, 6 is Down, 7 is Ana, and 8 is Kata.

Orientation

The Tesseract has 8 cells, named after the direction they initially are facing : North, South, East, West, Up, Down, Ana, Kata.

The Tesseract has an Orientation, tracked on its wiki page, that corresponds to the name of the cell it is resting on. The initial Orientation of the Tesseract is Down.

Each pair of opposing cells has an associated Affinity:

  • Water: North-South
  • Fire: East-West
  • Nature: Up-Down
  • Void: Ana-Kata

A Tesserer may spend a Shard to change the orienation of the Tesseract to one that has the same affinity as the Shard. This action is called “rotating” the Tesseract.

Affinity

Each Tesser has an Affinity (or none), which can be one of the following:

  • Water: A Water Tesser cannot make proposals with the word “Water” in it.
  • Fire: A Fire Tesser cannot make proposals with the word “Fire” in it.
  • Nature: A Nature Tesser cannot make proposals with the word “Nature” in it.
  • Void: A Void Tesser cannot make proposals with the word “Void” in it.

A Tesser’s Affinity is tracked in the GNDT, defaults to “none”, and if a Tesser hasn’t done so in this dynasty, they can change their Affinity from none to a different one.

Each Tesser has an amount of Shards, which are a magically created resource. Shards have an affinity, which is a Tesser Affinity. Each Tesser’s Shards are tracked in the GNDT by a capital letter of their affinity (FFWN for 2 Fire shards, 1 Water shards and 1 Nature Shard, for example). A Tesser can hold as many shards as they have Power. A Tesser can pay 3 Power to make a Shard of their Affinity. Tessers can freely give their Shards to other Tessers if that Tesser would be able to hold them. Tessers can freely discard their own Shards.

Tesserers can legally make proposals with their alignment with them, however, they have stricter requirements. They may pass only if the number of votes against equals zero.
Void and Nature are opposites.

Void

Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added

Fire

Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added

Water

Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added


Nature

Text in this rule can only be changed via proposals by referring to its title and the text that is changed, removed or added

Synonyms

“Tesser” and “Tesserer” are synonyms.

Codices

The following comes from fragments (believed to be Folio 2) from The Fourth Orthocodex of G. Ray, Master Emeritus in Aeternum:

Each pair of different affinities has its own Face Action; each with a shorthand Symbol:

- Nature/Fire: Radiance (☀)
- Nature/Water: Abundance (♾)
- Water/Fire: Transition (♻)
- Water/Void: Carving (❖) [*, +]
- Fire/Void: Destruction (✖) [*]
- Nature/Void: Opposition (◑) [*]

[+] see Folio 7 for discussion on naming of this Face Action.
[*] see Folio 9 for derivation of the symbology for these Face Actions.

The Fourth Orthocodex may be cited in brief as 'R4'. Text from R4 is not considered to be rules that Tesserers obey, unless otherwise specified.


This footnote is considered by scholars to come from the Octocodex written by O. Sedecim, Second Corner. This is one of the few remaining fragments after O. Sedecim accidentally traveled through Interim. The following footnote is considered ruletext.

A Tesser can perform Face Action by having the affinities that correspond to that Face Action participating and spending power equal to the number of affinities of the Face Action which don't match the Tessers' affinity. Participating affinities are the affinities of any Tessers that help in that action as well as the affinities of shards that participating Tessers possess; in case two or more Tessers perform a Face Action, they both pay this cost calculated with their own affinity.

The Octocodex may be cited in brief as ‘O8’. Text from O8 is not considered to be rules that Tesserers obey, unless otherwise specified.

The following letter draft is suspected to be made by M. Opus, Archphilosopher Primo of the New Order and is considered ruletext:

Gee-whiz, Seddy, things have been crazy lately huh? Man. I don't know how I did this, but there's like crazy meta-meta-metaphysical arcanopotential in the loopgrinder of sizzleslash. Yeah, I know, crazy. Now, I'm not entirely sure this will work for you all the time (it has like, eh, 10% success rate?), but I'll let you all know just in case you want to try pulling it off.

If you've got like, eight of the same kind of shard, which isn't of the kind you're attuned to - you know, your affinity - you can use any spell. Any spell. Yep. But you've got to lose all of them in the process, but hey, if it works, it works. Oh, and if you fail, your Power kind of becomes, well. Null. Zero. Nada. I guess you can figure out from that why I'm retiring.

So, how are the children? Last I heard, little *smudge* -s already tessering his fir- *smudge*

The rest of the letter has been lost to the ages.

Spells

By spending the cost in shards in brackets (noted here in Affinity initials, just like how they’re recorded in the GNDT, with an 'A' standing for any shard), you can perform the following spells:

  • [FWNV] Albedo: Gain 3 shards of affinities of your choice.
  • [FWNV] Nigredo: Destroy 3 shards of your choice.
  • [V] Null and Void: Remove one tessered act of your choice from the list of tessered acts on the wiki page.
  • [N] Growth: Add one to the boost of any and all Tessered Acts on the wiki page you specify when casting this spell
  • [F] Heat: Boost all tessered Acts on the Tesseract wiki page by two and add 1 the the instability of the tesseract
  • [W] Eddy: change the ownership of a Tessered act to a Tesserer who is not yourself and who has less than two tessered acts. the boost of the Tessered Act is reduced by one
  • [FFFVVV] Summon Phoenix: If you have the least Power, switch your Power with that of who has the most Power.
  • [NNNWWW] Summon Leviathan: If you have the most Power, all other Tessers lose a shard of your choice and you gain that shard.
  • [A] Ashes to Ashes: Gain 2 power.
  • [P] Negate: Choose a Tesser other than yourself. If they have a shard of your affinity they lose it and gain a shard of their affinity and you gain a shard of your affinity.
  • [O] Gamble: You must wait until the Tesseract’s orientation changes before casting this spell again. Roll a DICE2, on a 1 gain a shard of the Tesseract’s orientation after it changes.


Y stands for a shard that is the same affinity as the performer. P stands for a shard that is the opposite affinity of the performer. O stands for a shard that is the same affinity as the Tesseract’s current position.

Archmaster’s Watch

Each Tesser is being watched by the Archmaster or not, and this is tracked in the GNDT. The Archmaster can only watch one Tesser at a time. A Tesser that is being Watched by the Archmaster cannot perform Forbidden Spells but gain 1 more Power whenever they gain Power as the Archmaster grants them extra tutelage (this doesn’t affect gains provided by this rule).

A Tesser can pay 2 Power to Point to Someone and change who the Archmaster is watching to someone else other than themselves.

All Spells with the string “Summon” in them are Forbidden.

Crafts

If the Tesseract’s Orientation is that of your Affinity, you make a Craft by paying the appropriate shard cost in brackets as listed here according to the usual Spell shard cost nomenclature. A Tesserer can hold 1 Craft per 10 Power they have. The Crafts a Tesserer has is noted in the GNDT in its own column titled “Crafts”. Crafts, the ability you gain for having them and their shard cost are the following:

[FW] Alcohol: The Tesserer who has this item can GET WASTED and optionally brag about how they don’t remember what happened last night. They lose all of their Shards and their Power becomes 5. [VN] Pesticide: A Tesserer with this item cannot have Nature Shards but each time they make a Void shard, they may roll a 1d3. If they roll a 1 with that, they gain another Void shard.

Face Actions

This is a list of Face Actions, their effects and conditions.

  • Abundance: This may only be performed if the Instability is at 0. Every Tesser gains 5 power. The Tessers which participate also gain extra power equal to what they spent to perform this action. It is a daily action.
  • Radiance: Make a Tessered post that uses the power of the Tesseract as the maximum X value instead of your own power.

Trade

A Tesser may make a Trade Story post by putting the [Trade] tag in it’s title. In that post the author details a specific Tesser and they state what they want to trade, naming the amount and what it is. If within 2 days the named Tesser has accepted, indicated by commenting “SOLD” in the relevant post, the Tessers swap ownership of the detailed items.

Shards

A Tesser that has one of each type of shard may spend one power to commune with the Tesseract.
Each Tesser has an amount of Shards, which are a magically created resource. Shards have an affinity, which is a Tesser Affinity. Each Tesser’s Shards are tracked in the GNDT by a capital letter of their affinity (FFWN for 2 Fire shards, 1 Water shards and 1 Nature Shard, for example). A Tesser can hold as many shards as they have Power. A Tesser can pay 3 Power to make a Shard of their Affinity. Tessers can freely give their Shards to other Tessers if that Tesser would be able to hold them. Tessers can freely discard their own Shards.

Merit

The Tesserer named Diabecko has achieved victory.


Special Case

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.

Special Case Rules that are inactive do not have an effect on the gamestate aside from existing as text in the ruleset.

Combos [Active]

Anytime that a Tesserer wants to do 5 or more actions within an hour they may choose in lieu of doing all of those actions separately, which potentially causes confusion as to what is happening, to make a “Combo” blog post that cannot be edited after posting. The gamestate may be changed to reflect the results of the Combo once all of the actions are completed.

A Combo post is a numbered list of the actions taken, the first action is #1 each subsequent number of actions is increased by one. Each action and the portion of the gamestate changed from that action are kept on their own line. An Atomic action has lettering of its steps, refer to the example and note the curly braces vs the parenthesis.

Example Combo

  • 1 [action one] ([gamestate before action] -> [gamestate after action])
  • 2 [action two] ([gamestate before action] -> [gamestate after action])
  • 3 [atomic action] {[gamestate before atomic action]}
  • 3a [first atomic substep] ([gamestate before substep] -> [gamestate after substep])
  • 3b [second atomic substep] ([gamestate before substep] -> [gamestate after substep]) {[gamestate after atomic action]}
  • 4 [action four] ([gamestate before action] -> [gamestate after action])
  • etcetera . . .

If any actions require a die roll or other random event that is visible to the public, Tesserers must make those rolls before posting the combo with a note stating which step the roll is for and what action they are taking and the title of their Combo. Tesserers may not make multiple rolls in the GNDT for the same step. Tesserers cannot have two or more rolls in the GNDT with Combo titles that are different unless all but one of the Combo titles have been posted and include that roll.

Each action of a Combo happens in their own second, substeps of an Atomic Action happen all at the same second as the parent step. The first action happens at the time the Combo is posted.

If there is a mistake in the summary of the gamestate in a combo and that mistake doesn’t make it impossible for the stated actions to have happened, the author of that combo may correct those mistakes by making a comment along the format “[# of step]: [corrected gamestate summary]”.

Tags [Active]

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, 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 a Tesserer.

Atomic Actions [Active]

When a Tesserer performs an Atomic Action, they must complete all its steps; they must complete them in order; and they may not take any other action defined in the Ruleset until all such steps are complete. In addition, the Tesserer performing an Atomic Action performs its steps as quickly as they are able.

If one or more steps of an Atomic Action were done incorrectly, the Tesserer must redo the Atomic Action. In redoing an Atomic Action, the Tesserer 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 Tesserer 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.

If the Atomic Action was illegal due to a die that was wrong in the GNDT (for example, rolling a 1 on a DICE6 gives that Tesserer a point and the rest do nothing and the Tesserer rolls a DICE5 in the first one) and in redoing the Atomic Action they get the same effect as before (i.e. rolling an incorrect die and getting result X but then rolling the correct die and still getting result X) then the steps that depended upon that result are valid and don’t need to be redone. Steps that depend upon multiple dice which were done incorrectly must have each incorrect die have the same effect to be considered valid.

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.

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

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 Tesserers.
Daily Action
If a game action is a Daily Action, each Tesserer 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 Tesserer per day.
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 Tesserer’s Effective Vote Comment with respect to a given Votable Matter means that Tesserer’s Comment to that Votable Matter, if any, that contains that Tesserer’s Vote on that Votable Matter.
Flavour Text
When posting a blog entry, a Tesserer 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. 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.
May
"is permitted to"
May not
"is not permitted to"
Post
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
Quorum of a subset of Tesserers is half the number of Tesserers in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Tesserers it is referring to, it is referring to a Quorum of all Tesserers.
Resolve/Resolution
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
Rule
Each individually numbered section of the ruleset is a rule, including sections that are sub-rules of other rules.
Shall
"is required to"
Should
"is recommended that"
Sibling Rule
Two rules are “siblings” of each other if they are both direct subrules of the same rule.
Slack
The BlogNomic Slack is located at blognomic.slack.com. Tesserers 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.
Subject
The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.
Subrule
A subrule is a type of rule that is nested within another rule. A proposal that specifically affects a rule affects all of its subrules; a proposal that specifically affects a subrule does not affect its parent rule or any other subrule of that rule, unless they are also explicitly cited as being affected by that proposal.
Table of Contents
The directory of section headings that is generated by the MediaWiki software for most pages in the wiki.
TOC
Table of Contents.
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 Tesserer 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 Tesserer per week.
Wiki
The BlogNomic Wiki at http://wiki.blognomic.com

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 Tesserer 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 six hours old and either no Tesserer 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.

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 Tesserer who has been a Tesserer for fewer than seven days contains the word “Proposal” in its title, but is not a Proposal, and if it has been posted for less than an hour, then any admin may change it to be in the Proposal category.

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

If a Tesserer 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, Tesserers are encouraged to raise a Call for Judgement instead. Tesserers 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.

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 a Tesserer 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 Tesserer making this determination may do so using a private method of their choosing, instead of the GNDT.

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 Tesserers to transfer a numeric value only allows them to transfer that value from themselves to another Tesserer (of their choice unless otherwise stated).
  • A Tesserer 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, Tesserer 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.

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 Tesserer if it is explicitly stated that it refers to a Tesserer'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”.

Prioritisation

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