BlogNomic Wiki - User contributions [en]

The Isle of Multa

2023-01-18T11:35:49Z

Tantusar: Wheeeeeee, Discord server admin stuff.

Most recent Production of Resources: '''17/01/23 14:09'''

Current Production of Resources results: '''5, 9'''

{| class="wikitable"
|-
! Visitor
| None
|-
! Ledger
| -
|}

{| class="wikitable sortable"
|-
! rowspan=2 | Settler
! colspan=5 | Domains
! rowspan=2 | Stockpile
! rowspan=2 | Alliances
! rowspan=2 | Settlement
! rowspan=2 | Faction
|-
! style="background-color:wheat; font-family:monospace" | R
! style="background-color:darkseagreen; font-family:monospace" | J
! style="background-color:slategrey; color:white; font-family:monospace" | S
! style="background-color:sienna; color:white; font-family:monospace" | W
! style="background-color:orangered; color:white; font-family:monospace" | B
|-
| Benbot || - || - || - || - || - || - || - || - || -
|-
| Chiiika || 6 || 10 || 2 || 8 || 11 || 5 Brick, 1 Rye, 2 Jute || - || - || -
|-
| Habanero || 8 || 9 || 3 || 6 || 11 || 5 Brick, 1 Jute, 1 Wood || - || - || -
|-
| Janet || 10 || 5 || 9 || 6 || 8 || - || - || - || -
|-
| JonathanDark || 8 || 10 || 11 || 6 || 3 || 1 Wood, 2 Jute || - || - || -
|-
| Josh || 10 || 6 || 5 || 8 || 4 || 1 Rye, 1 Jute || - || Church || -
|-
| Kevan || 2 || 11 || 10 || 6 || 8 || 1 Wood || - || - || -
|-
| Misty || 6 || 8 || 11 || 10 || 2 || 1 Rye || - || - || -
|-
| quirck || 3 || 5 || 8 || 6 || 9 || 1 Stone, 1 Brick || - || - || -
|-
| Raven1207 || 6 || 8 || 5 || 9 || 10 || 2 Wood, 1 Rye, 1 Stone || Misty || - || -
|-
| SingularByte || 8 || 5 || 3 || 6 || 11 || 1 Jute, 1 Wood || - || - || -
|-
|}

{| class="wikitable"
|-
! Faction !! Ostracising
|-
| Unaffiliated || -
|-
| Amber || -
|-
| Silver || -
|-
| Purple || -
|-
| Cobalt || -
|-
| Pirates || -
|-
|}

{| class="wikitable"
|-
! The Dice Deck
| 2, 3, 3, 4, 4, 4, 5, 5, 5, 6, 6, 6, 6, 7, 7, 7, 7, 7, 8, 8, 8, 8, 8, 9, 9, 10, 10, 10, 11, 11
|}

{| class="wikitable"
|-
! Injured
| -
|-
! Victims
| -
|}



[[Category:Gamestate Tracking]]

BN Wiki Main page

2022-02-25T14:30:40Z

Tantusar:

[[Category:Gamestate Tracking]]
{| class="wikitable"
|+ Maestro Team Members
! Name || SCP || Alliance
|-
| Brendan || 000 || -
|-
| Clucky || 000 || -
|-
| Darknight || 000 || -
|-
| Jumble || 000 || -
|-
| Kevan || 000 || -
|-
| MadisonSilver || 000 || -
|-
| Raven1207 || 000 || -
|-
| SupernovaStarbright || 000 || -
|-
| TyGuy6 || 000 || -
|}

BN Wiki Main page

2022-02-25T14:30:29Z

Tantusar: added gamestate tracking category

[[Category:Gamestate Tracking]]

{| class="wikitable"
|+ Maestro Team Members
! Name || SCP || Alliance
|-
| Brendan || 000 || -
|-
| Clucky || 000 || -
|-
| Darknight || 000 || -
|-
| Jumble || 000 || -
|-
| Kevan || 000 || -
|-
| MadisonSilver || 000 || -
|-
| Raven1207 || 000 || -
|-
| SupernovaStarbright || 000 || -
|-
| TyGuy6 || 000 || -
|}

The Game Board

2022-02-11T13:11:36Z

Tantusar: Initialise with category.

[[Category:Gamestate Tracking]]

Company Portal

2022-01-16T11:36:43Z

Tantusar: added gamestate tracking category

[[Category:Gamestate Tracking]]

File:Conveyor.gif

2021-08-09T16:56:36Z

Tantusar: Tantusar uploaded a new version of File:Conveyor.gif

File:Conveyor.gif

2021-08-09T16:52:32Z

Tantusar: Tantusar uploaded a new version of File:Conveyor.gif

File:Conveyor.gif

2021-08-09T16:48:06Z

Tantusar:

Generic Core Rules

2021-01-13T12:04:34Z

Tantusar: /* Enacting and Failing */ Fixed formatting.

=The BlogNomic Standard Ruleset=

This is a generic ruleset for Nomics based on the core ruleset used in BlogNomic (http://www.blognomic.com). It has been written by Josh Hadley, Kevan Davis and Thomas Chick, based on the contributions of the hundreds of players of BlogNomic from 2004 to 2021. This is version 1.0; the most recent version can be found at https://wiki.blognomic.com/index.php?title=Generic_Core_Rules.

It is shared under a Creative Commons BY-NC-SA (Attribution-NonCommercial-ShareAlike 4.0 International) 4.0 licence.

If you use it - please do let us know!

==Usage notes==
As written, this ruleset is optimal for online play. To make it appropriate for real-time or offline play, remove the rule Idle Players, and change the time thresholds in the rule Enacting and Failing from 48 hours to the duration of your choice (we would recommend at least half an hour but not more than two hours).

{{TOCRight}}

<blockquote>

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern the game as a persistent whole, and the round's rules, which cover the specific rules of gameplay for the current round.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Idle Players===
A player can be active or idle. By default they are active. If a player wishes to switch between active and idle, they must make an announcement in a gamestate channel to that effect. Once a player has been made idle they cannot become active again until five days have passed.

For the purposes of all Gamestate and the Ruleset, excluding the Rules “Ruleset and Gamestate”, “Players”, and any of those Rules’ subrules, idle players are not counted as players.

When a player becomes active, if they became idle in the same game, 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 player idled in a different game), the player is given the default value for new players, if such a value exists.

== Rounds ==
The game is divided into Rounds. Each Round may be headed by a single player, known as the Emperor. The Emperor is also a player for all core rules, but is not a player for all round rules, unless otherwise stated.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which player may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

A '''proposal''' is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending.

A '''Call for Judgement''' (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that starts with the text "CALL FOR JUDGEMENT:".

A '''Declaration of Victory''' (or “DoV”) is a type of Votable Matter used when a player believes that they have won the round. If a player (other than the Emperor) believes that they have achieved victory in the current round, they may make a DOV detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:". Every player may cast votes in response to that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

==Votes==
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

When a player casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Self-Killed'''. The Emperor may VETO a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed. Self-killing or vetoing a proposal cannot be reversed; once cast, such a vote cannot be changed.

===Enacting and Failing===
A votable matter can be enacted if more than half the players have voted FOR it, or if it's been open for voting for 48 hours and has more votes FOR than AGAINST. (Proposals which have been Vetoed or Self-Killed can never be enacted.)

A votable matter can be failed if half or more of the players have voted AGAINST it, or if it's been open for 48 hours and cannot otherwise be enacted, or if it is a '''proposal''' and has been Vetoed or Self-Killed.

'''Proposals''' must be resolved in chronological order, from oldest to newest.

'''CfJs''' and '''DoVs''' are processed like proposals, except that they do not need to be resolved in chronological order and Vetoing or Self-Killing them has no effect. If a DoV is failed, the player who posted it cannot make another DoV for 120 hours (5 days).

Whenever a '''proposal''' or '''CfJ''' is enacted, the enacting admin must make the prescribed changes to the ruleset or gamestate. Whenever a '''DoV''' is enacted then the procedure described in the rule Victory and Ascension takes place.

== Victory and Ascension ==
When a DoV is Enacted, the player who posted it has won, and if al players wish to continue, and a new round can begin in which the player who made the DoV becomes the Emperor. The New Emperor can optionally make an Ascension Address, which is an official post in whcih they set out the theme for the new round, and all round rules are repealed.

=Round Rules=

</blockquote>

User:Tantusar/Generic core sandbox

2020-11-28T14:03:01Z

Tantusar:

This is a copy of a copy of the core rules of BlogNomic that can be adapted to other settings

{{TOCRight}}

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern all games played under them, and the game rules, which cover the specific rules of gameplay for the current game.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Active and Idle Players===

A player can be '''active''' or '''idle'''. By default they are active. If a player wishes to switch between active and idle, they must make an announcement in a gamestate channel to that effect.

For the purposes of all Gamestate and the Ruleset, excluding the Rules “Ruleset and Gamestate”, “Players”, and any of those Rules’ subrules, idle players are not counted as players.

When a player becomes active, if they became idle in the same game, 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 player idled in a different game), the player is given the default value for new players, if such a value exists.

=== Emperor ===

Each game may be headed by a single player, known as the '''Emperor'''. Unless otherwise stated, the game rules treat the Emperor as though they are not a Player.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which players may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

=== Votes ===
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

=== 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 are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Further votes cannot be made on Enacted or Failed Votable Matters.

This rule cannot be overruled by Game Rules in its application to Calls for Judgement or Declarations of Victory.

On all Votable Matters, quorum is considered to be half of the number of all players, rounded down, plus one.

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 players who are not voting AGAINST it is less than quorum.
* It has been open for voting for at least 48 hours and it is not popular.

=== Proposals ===
A Proposal is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''Proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending, or has already made 3 Proposals that day.

==== Special Proposal Voting ====
When a player 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 Emperor may use VETO as a voting icon to cast a Vote on a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Emperor 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) 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 ===
A Call for Judgement (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that started with the text "CALL FOR JUDGEMENT:".

A Pending CfJ may be Enacted by any Admin if all of the following are true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

A player's ability to raise a CfJ may never be restricted. This Rule may not be overruled or superceded by Game Rules.

=== Victory and Ascension ===
If a player (other than the Emperor) believes that they have achieved victory in the current game, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:"

Every player may cast votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current game.

A pending DoV may be Enacted by any Admin if any of the following are true:

* It is Popular, it has been open for at least 12 hours, and either the Emperor 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.

If a DoV is Failed and it had at least one AGAINST vote, the player who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, all prior game events are considered to be legally and successfully undertaken, and the player who made the DoV is considered to have won the game.

If the game is played again, discard the contents of the Game Rules. The winner of the previous game is the Emperor.

This rule cannot be overruled by Game Rules as it relates to Declarations of Victory, but it can be overruled in other matters.

= Game Rules =

User:Tantusar/Generic core sandbox

2020-11-28T13:59:38Z

Tantusar: /* Official Entries and Votable Matters */

This is a copy of a copy of the core rules of BlogNomic that can be adapted to other settings

{{TOCRight}}

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern all games played under them, and the game rules, which cover the specific rules of gameplay for the current game.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Active and Idle Players===

A player can be '''active''' or '''idle'''. By default they are active. If a player wishes to switch between active and idle, they must make an announcement in a gamestate channel to that effect.

For the purposes of all Gamestate and the Ruleset, excluding the Rules “Ruleset and Gamestate”, “Players”, and any of those Rules’ subrules, idle players are not counted as players.

When a player becomes active, if they became idle in the same game, 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 player idled in a different Dynasty), the player is given the default value for new players, if such a value exists.

=== Emperor ===

Each game may be headed by a single player, known as the '''Emperor'''. Unless otherwise stated, the game rules treat the Emperor as though they are not a Player.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which players may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

=== Votes ===
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

=== 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 are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Further votes 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.

On all Votable Matters, quorum is considered to be half of the number of all players, rounded down, plus one.

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 players who are not voting AGAINST it is less than quorum.
* It has been open for voting for at least 48 hours and it is not popular.

=== Proposals ===
A Proposal is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''Proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending, or has already made 3 Proposals that day.

==== Special Proposal Voting ====
When a player 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 Emperor may use VETO as a voting icon to cast a Vote on a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Emperor 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) 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 ===
A Call for Judgement (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that started with the text "CALL FOR JUDGEMENT:".

A Pending CfJ may be Enacted by any Admin if all of the following are true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

A player's ability to raise a CfJ may never be restricted. This Rule may not be overruled or superceded by Dynastic Rules.

=== Victory and Ascension ===
If a player (other than the Emperor) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:"

Every player 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 are true:

* It is Popular, it has been open for at least 12 hours, and either the Emperor 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.

If a DoV is Failed and it had at least one AGAINST vote, the player who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, a new Dynasty begins in which the player who made the DoV becomes the Emperor, and all prior game events are considered to be legally and successfully undertaken.

The new Emperor will make an '''Ascension Address''', which is an official entry (but not a votable matter). This should specify the Emperor’s chosen theme for the new Dynasty, and it may optionally specify that the terms “player” and “Emperor” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new official entries may be made and no dynastic actions may be taken.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it can be overruled in other matters.

= Game Rules =

User:Tantusar/Generic core sandbox

2020-11-28T13:59:09Z

Tantusar: /* Emperor */

This is a copy of a copy of the core rules of BlogNomic that can be adapted to other settings

{{TOCRight}}

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern all games played under them, and the game rules, which cover the specific rules of gameplay for the current game.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Active and Idle Players===

A player can be '''active''' or '''idle'''. By default they are active. If a player wishes to switch between active and idle, they must make an announcement in a gamestate channel to that effect.

For the purposes of all Gamestate and the Ruleset, excluding the Rules “Ruleset and Gamestate”, “Players”, and any of those Rules’ subrules, idle players are not counted as players.

When a player becomes active, if they became idle in the same game, 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 player idled in a different Dynasty), the player is given the default value for new players, if such a value exists.

=== Emperor ===

Each game may be headed by a single player, known as the '''Emperor'''. Unless otherwise stated, the game rules treat the Emperor as though they are not a Player.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which player may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

=== Votes ===
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

=== 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 are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Further votes 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.

On all Votable Matters, quorum is considered to be half of the number of all players, rounded down, plus one.

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 players who are not voting AGAINST it is less than quorum.
* It has been open for voting for at least 48 hours and it is not popular.

=== Proposals ===
A Proposal is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''Proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending, or has already made 3 Proposals that day.

==== Special Proposal Voting ====
When a player 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 Emperor may use VETO as a voting icon to cast a Vote on a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Emperor 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) 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 ===
A Call for Judgement (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that started with the text "CALL FOR JUDGEMENT:".

A Pending CfJ may be Enacted by any Admin if all of the following are true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

A player's ability to raise a CfJ may never be restricted. This Rule may not be overruled or superceded by Dynastic Rules.

=== Victory and Ascension ===
If a player (other than the Emperor) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:"

Every player 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 are true:

* It is Popular, it has been open for at least 12 hours, and either the Emperor 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.

If a DoV is Failed and it had at least one AGAINST vote, the player who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, a new Dynasty begins in which the player who made the DoV becomes the Emperor, and all prior game events are considered to be legally and successfully undertaken.

The new Emperor will make an '''Ascension Address''', which is an official entry (but not a votable matter). This should specify the Emperor’s chosen theme for the new Dynasty, and it may optionally specify that the terms “player” and “Emperor” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new official entries may be made and no dynastic actions may be taken.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it can be overruled in other matters.

= Game Rules =

User:Tantusar/Generic core sandbox

2020-11-28T13:58:46Z

Tantusar: /* Active and Idle Players */

This is a copy of a copy of the core rules of BlogNomic that can be adapted to other settings

{{TOCRight}}

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern all games played under them, and the game rules, which cover the specific rules of gameplay for the current game.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Active and Idle Players===

A player can be '''active''' or '''idle'''. By default they are active. If a player wishes to switch between active and idle, they must make an announcement in a gamestate channel to that effect.

For the purposes of all Gamestate and the Ruleset, excluding the Rules “Ruleset and Gamestate”, “Players”, and any of those Rules’ subrules, idle players are not counted as players.

When a player becomes active, if they became idle in the same game, 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 player idled in a different Dynasty), the player is given the default value for new players, if such a value exists.

=== Emperor ===

Each game may be headed by a single player, known as the Emperor. Unless otherwise stated, the game rules treat the Emperor as though they are not a Player.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which player may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

=== Votes ===
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

=== 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 are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Further votes 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.

On all Votable Matters, quorum is considered to be half of the number of all players, rounded down, plus one.

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 players who are not voting AGAINST it is less than quorum.
* It has been open for voting for at least 48 hours and it is not popular.

=== Proposals ===
A Proposal is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''Proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending, or has already made 3 Proposals that day.

==== Special Proposal Voting ====
When a player 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 Emperor may use VETO as a voting icon to cast a Vote on a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Emperor 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) 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 ===
A Call for Judgement (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that started with the text "CALL FOR JUDGEMENT:".

A Pending CfJ may be Enacted by any Admin if all of the following are true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

A player's ability to raise a CfJ may never be restricted. This Rule may not be overruled or superceded by Dynastic Rules.

=== Victory and Ascension ===
If a player (other than the Emperor) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:"

Every player 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 are true:

* It is Popular, it has been open for at least 12 hours, and either the Emperor 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.

If a DoV is Failed and it had at least one AGAINST vote, the player who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, a new Dynasty begins in which the player who made the DoV becomes the Emperor, and all prior game events are considered to be legally and successfully undertaken.

The new Emperor will make an '''Ascension Address''', which is an official entry (but not a votable matter). This should specify the Emperor’s chosen theme for the new Dynasty, and it may optionally specify that the terms “player” and “Emperor” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new official entries may be made and no dynastic actions may be taken.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it can be overruled in other matters.

= Game Rules =

User:Tantusar/Generic core sandbox

2020-11-28T13:57:30Z

Tantusar: /* Players */

This is a copy of a copy of the core rules of BlogNomic that can be adapted to other settings

{{TOCRight}}

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern all games played under them, and the game rules, which cover the specific rules of gameplay for the current game.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Active and Idle Players===

A player can be Active or Idle. By default they are Active. If a Player wishes to switch between Active and Idle, they must make an announcement in a gamestate channel to that effect.

For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Players”, and any of those Rules’ subrules, Idle Players are not counted as Players.

When a player becomes Active, if they became Idle in the same game, 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 player idled in a different Dynasty), the player is given the default value for new players, if such a value exists.

=== Emperor ===

Each game may be headed by a single player, known as the Emperor. Unless otherwise stated, the game rules treat the Emperor as though they are not a Player.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which player may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

=== Votes ===
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

=== 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 are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Further votes 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.

On all Votable Matters, quorum is considered to be half of the number of all players, rounded down, plus one.

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 players who are not voting AGAINST it is less than quorum.
* It has been open for voting for at least 48 hours and it is not popular.

=== Proposals ===
A Proposal is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''Proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending, or has already made 3 Proposals that day.

==== Special Proposal Voting ====
When a player 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 Emperor may use VETO as a voting icon to cast a Vote on a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Emperor 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) 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 ===
A Call for Judgement (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that started with the text "CALL FOR JUDGEMENT:".

A Pending CfJ may be Enacted by any Admin if all of the following are true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

A player's ability to raise a CfJ may never be restricted. This Rule may not be overruled or superceded by Dynastic Rules.

=== Victory and Ascension ===
If a player (other than the Emperor) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:"

Every player 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 are true:

* It is Popular, it has been open for at least 12 hours, and either the Emperor 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.

If a DoV is Failed and it had at least one AGAINST vote, the player who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, a new Dynasty begins in which the player who made the DoV becomes the Emperor, and all prior game events are considered to be legally and successfully undertaken.

The new Emperor will make an '''Ascension Address''', which is an official entry (but not a votable matter). This should specify the Emperor’s chosen theme for the new Dynasty, and it may optionally specify that the terms “player” and “Emperor” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new official entries may be made and no dynastic actions may be taken.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it can be overruled in other matters.

= Game Rules =

User:Tantusar/Generic core sandbox

2020-11-28T13:56:31Z

Tantusar: /* Dynastic Rules */

This is a copy of a copy of the core rules of BlogNomic that can be adapted to other settings

{{TOCRight}}

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern all games played under them, and the game rules, which cover the specific rules of gameplay for the current game.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Active and Idle Players===

A player can be Active or Idle. By default they are Active. If a Player wishes to switch between Active and Idle, they must make an announcement in a gamestate channel to that effect.

For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Players”, “Dynasties”, “Fair Play”, and any of those Rules’ subrules, Idle Players are not counted as Players.

When a player becomes Active, if they became Idle in the same game, 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 player idled in a different Dynasty), the player is given the default value for new players, if such a value exists.

=== Emperor ===

Each game may be headed by a single player, known as the Emperor. Unless otherwise stated, the game rules treat the Emperor as though they are not a Player.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which player may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

=== Votes ===
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

=== 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 are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Further votes 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.

On all Votable Matters, quorum is considered to be half of the number of all players, rounded down, plus one.

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 players who are not voting AGAINST it is less than quorum.
* It has been open for voting for at least 48 hours and it is not popular.

=== Proposals ===
A Proposal is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''Proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending, or has already made 3 Proposals that day.

==== Special Proposal Voting ====
When a player 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 Emperor may use VETO as a voting icon to cast a Vote on a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Emperor 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) 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 ===
A Call for Judgement (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that started with the text "CALL FOR JUDGEMENT:".

A Pending CfJ may be Enacted by any Admin if all of the following are true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

A player's ability to raise a CfJ may never be restricted. This Rule may not be overruled or superceded by Dynastic Rules.

=== Victory and Ascension ===
If a player (other than the Emperor) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:"

Every player 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 are true:

* It is Popular, it has been open for at least 12 hours, and either the Emperor 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.

If a DoV is Failed and it had at least one AGAINST vote, the player who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, a new Dynasty begins in which the player who made the DoV becomes the Emperor, and all prior game events are considered to be legally and successfully undertaken.

The new Emperor will make an '''Ascension Address''', which is an official entry (but not a votable matter). This should specify the Emperor’s chosen theme for the new Dynasty, and it may optionally specify that the terms “player” and “Emperor” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new official entries may be made and no dynastic actions may be taken.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it can be overruled in other matters.

= Game Rules =

User:Tantusar/Generic core sandbox

2020-11-28T13:56:12Z

Tantusar: Initial commit.

This is a copy of a copy of the core rules of BlogNomic that can be adapted to other settings

{{TOCRight}}

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset'''; all players shall obey it. The Gamestate is defined as any information which the Ruleset regulates the alteration of.

The ruleset consists of two sections: the core rules, which govern all games played under them, and the game rules, which cover the specific rules of gameplay for the current game.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any player may update it to do so.

== Players ==
Any human may become a player by announcing their intent to do so in a gamestate channel.

Some players are '''Admins''', responsible for updating the Ruleset. Players who wish to become Admins may submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

===Active and Idle Players===

A player can be Active or Idle. By default they are Active. If a Player wishes to switch between Active and Idle, they must make an announcement in a gamestate channel to that effect.

For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Players”, “Dynasties”, “Fair Play”, and any of those Rules’ subrules, Idle Players are not counted as Players.

When a player becomes Active, if they became Idle in the same game, 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 player idled in a different Dynasty), the player is given the default value for new players, if such a value exists.

=== Emperor ===

Each game may be headed by a single player, known as the Emperor. Unless otherwise stated, the game rules treat the Emperor as though they are not a Player.

== Official Entries and Votable Matters ==
An official entry is any communication whose content or format is determined by the ruleset.

A '''Votable Matter''' is an official entry which player may cast Votes on, such as a Proposal, a Call for Judgement or a Declaration of Victory.

=== Votes ===
Each player may cast one vote on a Votable Matter by making a response to the official entry that comprises that Votable Matter, indicating FOR, AGAINST, or DEFERENTIAL. A player's valid vote on a Votable Matter is that player's most recent response to the official entry for that Votable Matter, and must, except when otherwise specified, be a vote of FOR or AGAINST, or VETO if the player is the Emperor. Additionally, if the author of a Votable Matter has not made a vote in response to that Votable Matter, then the author’s Vote is FOR. A non-player never has a Vote, even if they were a player previously and had cast a valid vote.

If a player other than the Emperor casts a vote of DEFERENTIAL, then the vote of DEFERENTIAL is an indication of confidence in the Emperor. When the Emperor 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 Emperor’s vote, unless otherwise specified.

=== 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 are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Further votes 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.

On all Votable Matters, quorum is considered to be half of the number of all players, rounded down, plus one.

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 players who are not voting AGAINST it is less than quorum.
* It has been open for voting for at least 48 hours and it is not popular.

=== Proposals ===
A Proposal is a kind of Votable Matter used to make changes to the ruleset or gamestate. Any player may submit a '''Proposal''' to change the Ruleset or Gamestate by making an official entry that starts with the text "PROPOSAL:", and which describes those changes, unless the player already has 2 Proposals pending, or has already made 3 Proposals that day.

==== Special Proposal Voting ====
When a player 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 Emperor may use VETO as a voting icon to cast a Vote on a Proposal; when the Emperor casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Emperor 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) 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 ===
A Call for Judgement (or CfJ) is a Votable Matter used if two or more players actively disagree as to the interpretation of the Ruleset, or if a player feels that an aspect of the game needs urgent attention. A player may raise a CfJ at any time by making an official entry that started with the text "CALL FOR JUDGEMENT:".

A Pending CfJ may be Enacted by any Admin if all of the following are true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

A player's ability to raise a CfJ may never be restricted. This Rule may not be overruled or superceded by Dynastic Rules.

=== Victory and Ascension ===
If a player (other than the Emperor) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by making an official entry that starts with the text "DECLARATION OF VICTORY:"

Every player 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 are true:

* It is Popular, it has been open for at least 12 hours, and either the Emperor 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.

If a DoV is Failed and it had at least one AGAINST vote, the player who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, a new Dynasty begins in which the player who made the DoV becomes the Emperor, and all prior game events are considered to be legally and successfully undertaken.

The new Emperor will make an '''Ascension Address''', which is an official entry (but not a votable matter). This should specify the Emperor’s chosen theme for the new Dynasty, and it may optionally specify that the terms “player” and “Emperor” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new official entries may be made and no dynastic actions may be taken.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it can be overruled in other matters.

= Dynastic Rules =

Great Sea

2020-09-11T14:46:52Z

Tantusar: Turn taken.

'''Round:''' 2

{| class="wikitable sortable"
|-
! Name !! Turn Timer !! Land !! Foliage !! Lists
|-
| Bais || 11 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Brendan || 25 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| card || 91 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Clucky || 97 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Cuddlebeam || 84 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| derrick || 60 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Jumble || 21 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Kevan || 1 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| pokes || 24 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Raven1207 || 94 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Riggdan || 66 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Tantusar || - || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|-
| Vovix || 90 || 5 || 0 || Brown {Land+0,Land+1,Land+1,Land+1,Land+2}, Green {Foliage+0,Foliage+1,Foliage+1,Foliage+1,Foliage+2}
|}

Mission Log

2020-09-07T13:06:55Z

Tantusar: It's the self-unidle of the century!

{| class="wikitable sortable"
|+Pathfinder Gamestate
|-
! Name !! Item 1 !! Item 2 !! Item 3 !! Stamina !! Prestige !! Location
|-
|| Cuddlebeam || Bone Scanner || - || - || 1 || 2 || The Cortex Desert
|-
|| derrick || Gamma Pistol || Bone Scanner || || 10 || 39 || Physiy Forest
|-
|| Josh || Fire Extinguisher || - || Wrench || 10 || 30 || Colle Rainforest
|-
|| pokes || Fire Extinguisher || - || - || 9 || 7 || Cuneg Taiga
|-
|| Raven1207 || Magnetic Gloves || - || - || 10 || 0 || The Cortex Desert
|-
|| Riggdan || Gamma Pistol || - || - || 10 || 7 || Branchin Mountains
|-
|| Tantusar || - || - || - || 7 || 0 || The Cortex Desert
|}

{| class="wikitable sortable"
|+Locations
|-
! Index !! Location !! Topology !! Discoveries !! Hazards !! Links
|-
|| 1 || The Cortex Desert || Desert || Gregite || Gregite || Qualifier Hills, Cresci Glacier, Branchin Mountains, Geosynchronous Rig, Physiy Forest
|-
|| 2 || Qualifier Hills || Hills || Trabite || Priora populum || Cortex Desert, Interu Hills
|-
|| 3 || Cresci Glacier || Glacier || Iterium || - || Cortex Desert, Colle Rainforest, Acari Hills
|-
|| 4 || Interu Hills || Hills || Priora populum || - || Qualifier Hills, Felicu Savannah, Trepi Forest
|-
|| 5 || Colle Rainforest || Rainforest || Arcti sordia || - || Cresci Glacier, Trecenta Mountains, Branchin Mountains, Acari Hills, Cuneg Taiga
|-
|| 6 || Branchin Mountains || Mountains || Mundium || - || Cortex Desert, Cuneg Taiga, Colle Rainforest
|-
|| 7 || Felicu Savannah || Savannah || Tremadon || Opisthos, Tremadon || Interu Hills, Hormi Hills
|-
|| 8 || Cuneg Taiga || Taiga || Teret necria || - || Branchin Mountains, Calle Rainforest
|-
|| 9 || Hormi Hills || Hills || Opisthos || - || Felicu Savannah, Campa Savannah
|-
|| 10 || Trecenta Mountains || Mountains || Celera alphum || - || Colle Rainforest
|-
|| 11 || Campa Savannah || Savannah || Tricha heliia || - || Hormi Hills, Heteru Grassland
|-
|| 12 || Trepi Forest || Forest || Stenium || - || Interu Hills, Quindene Forest
|-
|| 13 || Heteru Grassland || Grassland || Onera accipitrum || Onera accipitrum || Campa Savannah, Physiy Forest
|-
|| 14 || Physiy Forest || Forest || Turba cirrum || - || Heteru Grassland, Phryni Desert, The Cortex Desert
|-
|| 15 || Quindene Forest || Forest || Lampus || Lampus || Trepi Forest
|-
|| 16 || Acari Hills || Hills || Fricos || - || Cresci Glacier, Colle Rainforest
|-
|| 17 || Phryni Desert || Desert || Collos || - || Physiy Forest
|-
|| - || Geosynchronous Rig || Savannah || - || - || The Cortex Desert
|}

{| class="wikitable sortable"
|+Bases
|-
! Owner !! Location !! Gear
|-
|| The Computer || The Cortex Desert || Gamma Pistol (6), Rocket Fuel (5), Canister of Glarsh (10), Magnetic Gloves (4), Fire Extinguisher (3), Wrench (2)
|-
|| The Computer || Geosynchronous Rig || Pod (6)
|-
|| Josh || Colle Rainforest || Probe
|-
|| Derrick || Physiy Forest || Hallucinogenic Substance
|-
|| pokes || Cuneg Taiga ||
|}

Second Switch Ruleset

2020-08-05T06:19:42Z

Tantusar: "I guess the votes are being fixed by an actual player account"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for the BlogNomic WordPress test; all Designers shall obey it. Henceforth in this document, "BlogNomic" refers to the BlogNomic WordPress test at https://wp.blognomic.com, ''not'' the main BlogNomic game at https://blognomic.com, unless otherwise specified.

It comprises four Sections: 1) the “core rules” of BlogNomic, covering the essential elements of gameplay; 2) the rules of the current Dynasty; 3) rules which apply in special cases; and 4) the appendix, which complements and clarifies the Ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any Designer may update it to do so.

== Designers ==
Any active Designer of the main BlogNomic game at https://blognomic.com may sign up for a BlogNomic WordPress test account, using the same name and email address they use at the main BlogNomic game, at https://wp.blognomic.com/register. When they have saved their profile fields with “Player status” set to “Active” and appear as an active player in the sidebar, they become a Designer.

A Designer may only change their name as a result of a Proposal approving the change.

Some Designers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Admins at the main BlogNomic game shall become Admins of the BlogNomic WordPress test when they become a Designer of the BlogNomic WordPress test, unless they request otherwise, and any Admin at the main BlogNomic game may become an Admin of the WordPress Test game at any time by posting a notice to that effect. Upon the posting of such a notice, any other Admin should make the necessary profile changes at their earliest opportunity and comment to the Notice to confirm that they are complete. Designers of the main BlogNomic game who are not Admins there may not become Admins of the BlogNomic WordPress test.

===Idle Designers===

If a Designer is Idle, this is tracked by their "Designer status" profile field being set to "Idle", thus removing their name from the list of currently active Designers in the Sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Designers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Designers are not counted as Designers.

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

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

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

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to Quorum to have come about as a result of it.

Idle Admins can enact and fail Votable Matters.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Designer, known as the Lead Developer. If there is no Lead Developer, the Dynasty is a Metadynasty.

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

===Votes===
Each Designer may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter with the Vote field set to FOR, AGAINST, or DEFERENTIAL. Additional Vote field values may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. A Designer’s Vote on a Votable Matter is the vote field value that they have most recently used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not voted in a comment to the post, then the author’s Vote is FOR. A non-Designer never has a Vote, even if they were a Designer previously and had cast a valid Vote.

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

Throughout the Ruleset, the capitalization of Vote field values may differ from that used on the actual comment Vote field; these capitalization differences shall be considered irrelevant.

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 Designers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and it is not Popular.

=== Enacting and Failing ===

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin Resolves a Votable Matter, they should mark their name, and are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Comments cannot be made on Enacted or Failed Votable Matters.

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

===Tags===
Votable Matters must have the tag/s “Core”, “Special Case” and/or “Appendix” to amend the Core Rules, the Special Case Rules and/or the Appendix, respectively.

Votable Matters other than [[#Victory and Ascension|DoVs]] require the tag “Victory” in order to grant victory to a Designer.

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

=== Special Proposal Voting ===

When a Designer 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 Lead Developer may make a vote of VETO on a Proposal; when the Lead Developer casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Lead Developer later changes their Vote.

=== 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 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 Designers actively disagree as to the interpretation of the Ruleset, or if a Designer feels that an aspect of the game needs urgent attention, then any Designer 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 true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==

If a Designer (other than the Lead Developer) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by posting an entry in the “Declaration of Victory” category.

Every Designer may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty. If there is at least one pending DoV, BlogNomic is [[#hiatus|on Hiatus]].

A Pending DoV may be Enacted by any Admin if any of the following are true:

* It is Popular, it has been open for at least 12 hours, and either the Lead Developer 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.

If a DoV is Failed and it had at least one AGAINST vote, the Designer who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, and a new Dynasty begins in which the Designer who made the DoV becomes the Lead Developer.

The new Lead Developer will make an '''Ascension Address''' by posting an entry in the “Ascension Address” category. This should specify the Lead Developer’s chosen theme for the new Dynasty, and it may optionally specify that the terms “Designer” and “Lead Developer” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new DoV may be made and BlogNomic is on Hiatus.

Before an Ascension Address has been posted for a new Dynasty, the Lead Developer may pass the role of Lead Developer to another Designer by making a post to that effect.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it 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 Designer’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. Designers should vote against any DoV that relies on having broken a fair play rule.

* A single person should not control more than one non-Idle Designer within BlogNomic, and should announce publicly if they control both a non-Idle Designer and any Idle Designers.
* A Designer 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 Designer should not deliberately exploit bugs or unexpected behaviours in the software running the game (WordPress, MediaWiki or other blognomic.com scripts).
* A Designer should not edit their own blog comments once posted, nor those of any other Designer.
* A Designer should not edit the “Entry Date” field of a blog post.
* A Designer should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Designer 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 Designer should not roll dice 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 Designer must use their own name in the Dice Roller, when rolling dice.
* A Designer should not deliberately and unreasonably prolong the performance of a game action once they have started it.
* A Designer should not use a core, special case or appendix rules scam to directly or indirectly achieve victory.
</div>

= Dynastic Rules =

== Elementor Basics ==

When any of the following terms is used in reference to the contents of a page on https://wp.blognomic.com, they refer to their meaning in the Elementor page builder and [[https://docs.elementor.com/ its documentation]]:

* Section
* Column
* Widget
* Template

Any of the above terms may be preceded by the word “Elementor” for clarity.

When referring to the contents of a page on https://wiki.blognomic.com, including the Ruleset itself, these terms do not refer to their meaning in Elementor unless specified otherwise.

== The Second Switch Page ==

The page at [https://wp.blognomic.com/second-switch-page https://wp.blognomic.com/second-switch-page], if it exists, is known as the Second Switch Page or SSP, and is Gamestate. Its WordPress title shall be “Second Switch Page”.

The SSP shall consist of one or more Elementor Sections and their contents.

No SSP Sections may contain any Columns not authorized by the Ruleset. No SSP Columns may contain any Widgets not authorized by the Ruleset. No Designer, even Admins, may change the settings of SSP Sections or Columns from their default settings, except as explicitly permitted by the Ruleset.

The topmost Section on the SSP shall contain one Column, and that Column shall contain one “Page Title” Widget, set to display the page’s title. The settings of this widget may be changed at the discretion of the Lead Developer, provided that the settings do not break any rules.

All other SSP Sections shall collectively be known as the Canvas, and individually known as Canvas Sections.

=== The Canvas ===

Only Admins may edit the Canvas, and Admins may only edit it as the Ruleset allows.

All Canvas Sections shall contain between 2 and 4 Columns. All the columns within a Canvas Section must be equally wide, and all together must be the full width of the Section.

All of a Canvas Section’s Columns must contain at least one Widget.

New Widgets being added into empty Columns must follow the following algorithm (depicted [[:File:Second Switch Page Canvas algorithm.gif|here]]), unless otherwise permitted in the Ruleset:

# No Widget may be added to an empty Canvas until 2 Widgets are ready to be populated at the same time. (This is implied by the requirements that Canvas Sections must have at least 2 Columns, and that all Columns must have at least one Widget.)
# The order of Widgets will always be preserved left-to-right then top-to-bottom, in the order that their addition was required or requested.
# When 2 Widgets are ready to be added, the Admin editing the Canvas will create the first Canvas Section with a two-column layout, then add them.
# When the 3rd Widget is ready to be added, the Section will have 3 columns.
# When the 4th Widget is ready, the Section will have 4 columns.
# When the 5th Widget is ready, the Section will have 3 columns, and a new Section below it will have 2.
# When the 6th Widget is ready, the older Section and newer Section will both have 3 Columns.
# When the 7th Widget is ready, the older Section will have 4 Columns and the newer one 3.
# When the 8th Widget is ready, both older and newer Sections will have 4.
# When the 9th Widget is ready, the algorithm repeats the pattern started in step 6 above, with the “newer” Section now considered the “older” one, and another new Section created below it.

=== Designer Templates ===

All Designers may create one regular Elementor Template (not a Theme Builder or Popup Template), named “[Playername]’s Template”, where [Playername] is replaced by the Designer’s BlogNomic name. Such Templates are known as “Designer Templates”.

After creating their Designer Template, a Designer may make a blog post requesting an Admin to populate it into the Canvas, or, if they are an Admin, announcing that they will do so themselves. No Designer Template may be populated into the Canvas without such a post being made. The Admin should confirm that the Template abides by the Ruleset before populating it, and if it is found not to abide by the Ruleset, the Admin must decline to populate it and comment on the request explaining which rule they think it breaks and why. The creator of the Designer Template must then make a new post requesting that it be populated into the Canvas.

Designer Templates are populated into the Canvas by adding an Elementor “Template” Widget to an empty Column, then choosing the Template.

A Designer Template shall have only one Section, containing only one Column, and shall have no Widgets not permitted by the Ruleset. However, the Designer may change any of their Template’s Sections' settings, Columns' settings, and/or Widgets’ settings — except for Custom CSS, which must remain empty unless otherwise permitted — in any way not forbidden by the Ruleset.

No part of a Designer Template may ever exceed the bounds of its Column on the Canvas by any method, including but not limited to overly large fonts or relative/absolute positioning. This includes all browser widths; therefore, Designers should test their Templates at all browser widths and make width-specific adjustments as supported by Elementor if need be.

A Designer may edit their Designer Template as often as they wish if it is not yet populated into the Canvas. If it is populated into the Canvas, the Designer may edit it in any permissible way as a Daily Action. If a Designer Template on the Canvas is found to break a rule, the Designer may edit it at any time to make it conform to the rules, even if the rules regarding Daily Actions would prohibit it; however, such an edit still counts as a Daily Action for the purposes of determining whether a future edit to this template is legal. Such an edit must be announced in a blog post before being made, and may not make any changes not related to making the Designer Template conform to the rules.

Any Designer may challenge the legality of any other Designer’s Designer Template by making a post to the Votable Matter category tagged with “SSP”, and whose text explains the illegality and proposes a change to the Template to make it conform to the rules. If the post is Enacted, the proposed change shall be made by the enacting Admin. Such a Votable Matter is not required, however; if a Designer can be convinced in any informal way that their Template breaks the rules, they may simply announce their change and make it, as described above.

=== Permitted Widgets ===

A Designer Template shall have, as its topmost Widget, an Elementor “Heading” Widget, whose text must always be the same as the Designer Template’s name. The font size of this heading must be less than or equal to 24 pixels or 1.5 rems.

==== Icon Box or Image Box ====

A Designer Template may have one of the following: (1) up to two “Icon Box” Widgets, (2) up to two “Image Box” Widgets, or (3) an “Icon Box” Widget and an “Image Box” Widget. No image or icon within the chosen Widget may appear taller than 200 CSS pixels at any browser width. No text within it may have a font size greater than 24 pixels or 1.5 rems. Designers may create or upload any image to which they have distribution rights for use in an Image Box widget, so long as it does not violate any other rules.

==== Inventory ====

A Designer Template may have a single "Icon List" widget, with exactly three list items which unambiguously state the number of Products, Ideas, and Clients (collectively called Resources) owned by that Template's Designer. The icons of these three items shall be "Box", "Lightbulb", and "User" respectively. No text within this Widget may have a font size greater than 24 pixels or 1.5 rems.

== Income ==

When updating their Template, a Designer may increase the amount of a Resource they own by at most X, where X is the number of days since their last edit to the Template. This may only be done if the Template (prior to editing) contains an "Image Box" Widget or an "Icon Box" Widget matching that Resource.

An "Image Box" Widget is considered to match:

* Clients, if it contains an image which shows a person.
* Products, if it does not match Clients and contains an image which shows a man-made object.
* Ideas, if it does not match any other Resource.

An "Icon Box" Widget is considered to match a Resource if it contains the icon used to represent that Resource, as defined under "Inventory" in the "Permitted Widgets" subrule.

<br/>
<div style="padding:8px;background:#bbb;">

= Special Case =
'''Special Case Rules''' can be Active or Inactive. A Special Case Rule should be tagged with its status. Otherwise, its status is its Default Status.

Special Case Rules have a '''Default Status''', which can be Active or Inactive. If the title of a Special Case Rule includes an asterisk, (*) its Default Status is Inactive, otherwise, its Default Status is Active.

When a new Dynasty is started, the Ascension Address may list any number of existing Special Case Rules to be set to a status other than their respective Default Status. All other Special Case Rules are set to their respective Default Status.

The text of a Special Case Rule that is Inactive is flavour text.

==Seasonal Downtime [Active]==
On the 24th, 25th and 26th of December, BlogNomic is [[#hiatus|on Hiatus]]. In addition, game actions defined by the rules titled “Designers” and “Victory and Ascension” (with the exception of Voting in DoVs) may not be taken.

==Dormancy [Inactive]==
If there are fewer than five Designers, BlogNomic is [[#hiatus|on Hiatus]].

==Imperial Deferentials [Active]==
If the Lead Developer has voted DEFERENTIAL on a Proposal, that vote is instead considered to be valid and either FOR (if more Designers have voted FOR the Proposal than have voted AGAINST it) or AGAINST (in all other cases).

==Dynastic Distance [Active]==
For the purposes of dynastic rules which do not deal with voting, the Lead Developer is not a Designer.

==The Traitor [Active]==
The Traitor for a particular Dynasty may be a Designer (including an idle one), or may be nobody, and it defaults to being nobody. The Traitor’s identity in the current Dynasty is tracked privately by the Lead Developer, and the Lead Developer should not share this information with Designers other than the Traitor.

If there is no Traitor for the current Dynasty, and BlogNomic is not on Hiatus, the Lead Developer may secretly randomly select a Designer (other than the Lead Developer) and privately inform them that they are the Traitor for the current Dynasty.

A Traitor is under no obligation to honour any informal promises they have made with other Designers, nor to tell the truth to them, and is encouraged to betray other Designers in order to achieve victory.

</div>
<div style="padding:8px;background:#ddd;">

= 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. (e.g. 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 WordPress weblog at [https://wp.blognomic.com wp.blognomic.com]. A top-level comment is a comment which is not a reply to another comment.

;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 Designers.

;Daily Action
:If a game action is a Daily Action, each Designer 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 Designer 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 “DICEX” or “YDICEX” refer to X-sided dice and Y amount of X-sided dice, rolled using the Dice Roller.

;Dynastic Action
:An action that is defined in the Dynastic rules.

;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 Designer’s Effective Vote Comment with respect to a given Votable Matter is that Designer’s Comment to that Votable Matter, if any, that contains that Designer’s Vote on that Votable Matter.

;Commentary
:When posting a blog entry, a Designer 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.

;Flavour Text
:If a part of the ruleset is defined as being “flavour text”, it is gamestate and remains part of the ruleset document, but is not considered to have any meaning beyond being a string of characters. Designers are not required to obey flavour text and may not perform any action defined by it, and any statements that flavour text makes about gamestate are ignored.

;Gamestate
:Any information which the Ruleset regulates the alteration of. All wiki pages that the Dynastic Rules explicitly mention (except for dynastic histories and discussion pages) and any images or Templates contained within those Wiki Pages are assumed to be Gamestate.

;<span id="hiatus">Hiatus</span>
:If BlogNomic is on Hiatus, Dynastic Actions may not be taken, and Proposals may not be submitted or Resolved. If multiple rules require BlogNomic to be on Hiatus at any given time, BlogNomic will continue to be on Hiatus until no rules require it.

;Introduction: The introduction of a rule is the part of that rule’s text before any subrules.

;Post
:A blog post published to the BlogNomic WordPress weblog at [http://wp.blognomic.com wp.blognomic.com]

;Private Message
:A message sent via BlogNomic’s Private Messages system at wp.blognomic.com.

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

;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 subrules 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. Designers 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 (e.g. #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.

;Tag: A Post may have any number of tags applied to it using the WordPress interface. A Rule may have any number of tags applied to it. Rule tags are represented by appending to their title a comma-separated list of such tags, enclosed in square brackets.

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

;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 Designer 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 Designer per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

===Official Posts===

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [https://wp.blognomic.com https://wp.blognomic.com]. Any Designer may [https://wp.blognomic.com/wp-admin/post-new.php 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.

An official post may only be removed as allowed by the Ruleset.
An official post may be altered by its author if it is less than two hours old and either no Designer has commented on it or (if it is a Votable Matter) if all comments on it contain no votes; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post’s Status must be changed to reflect its status. An official blog post that has the status of Enacted or Failed cannot change categories. An official blog post’s status may never be altered except in accordance with the rules that define that official post.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following two exceptions: Firstly, whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish. Secondly, if a post by a New Designer is not in any category but follows the wording of a Proposal, in that it has written changes the gamestate and or Ruleset, and if it has been posted for less than six hours, then any Admin may change it to be in the Proposal category. A New Designer is defined as a Designer who has been a Designer for fewer than seven days or a Designer that has unidled in the past seven days after being idle for at least 3 months.

Any post that is or is made illegal as a result of an infraction against any of the prohibitions set out in this rule continues to be an Official Post but may no longer have any effect on the ruleset or the gamestate. If it is a Votable Matter then it is Unpopular, regardless of any other performance against criteria set out in the core rules. When it is resolved it may be marked as Illegal by the resolving admin. A post that is illegal in this manner cannot subsequently be made legal by any means.

===Representations of the Gamestate===

For gamestate which is tracked in a specific place (such as a wiki page), any alteration of that gamestate as a result of a Designer’s action is (and can only be) applied by editing that data in that place. One 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 wiki merely represents the Gamestate tracked there, and is not the same thing. In the event that the Gamestate and its representations are different, any Designer may correct the representations to comply with the Gamestate.

If a Designer feels that a representation of the gamestate (such as a wiki page) 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 alteration, Designers are encouraged to raise a Call for Judgement instead.

The historical fact of the occurrence of a defined game action is itself considered to be gamestate, tracked in the history of whatever resource is used to track the gamestate modified by that action, where possible, or in the wiki page [[Gamestate Modifications]] if this is not possible.

===Orphan Variables===

An Orphan Variable is a dynastic gamestate variable which has neither a location in which it’s tracked, nor a reasonable manner in which it can be determined from other gamestate variables, specified in the Ruleset.

A Designer may not take any dynastic actions that are contingent on the specific value of an Orphan Variable.

=== Random Generators ===
The Dice Roller at https://blognomic.com/dice/roll.php can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The CARD command will return a card with a random suit (either Hearts, Diamonds, Spades or Clubs) and a random value (either Ace, 2, 3, 4, 5, 6, 7, 8, 9, 10, Jack, Queen, King). A card with a value that is either Jack, Queen or King is a face card.

Any changes to the potential outcomes of the Dice Roller’s random result commands must be made by Proposal.

If a Proposal proposes a change to this rule that would require server-level access to the BlogNomic site to fully enact its effects, that Proposal must name a Designer with such access. Only a Designer with such access may Enact that Proposal. If that Proposal does not name a Designer with such access, that Proposal is Illegal.

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 Dice Roller, unless otherwise specified. If a selection is explicitly specified as being “secretly” random, the Designer making this determination may do so using a private method of their choosing, instead of the Dice Roller.

==Atomic Actions==

An Atomic Action combines otherwise separate game actions into a single action.

* All steps of an Atomic Action are considered one action, including the steps of an Atomic Action that is itself a step of a parent Atomic Action.
* When a Designer performs an Atomic Action, they must complete all its steps; they must complete them in order; and they may not take any other dynastic action, or achieve victory, until all the steps are complete.
* An Atomic Action may direct the Designer performing it to skip some of its steps, which the Designer must do and in which case the skipped steps are considered completed for this rule.
* If a Designer arrives at a step in an Atomic Action and they cannot perform that step, they undo all the steps they have performed of that Action and are considered never to have performed that Action.
* If one or more steps of an Atomic Action were done incorrectly, the Designer must redo the Atomic Action; for that purpose, the Designer uses any legal steps that have already been completed in the illegal Atomic Action and only redoes the illegal ones. (For example, if an Atomic Action consists of rolling a dice and then doing steps based upon its result, the Designer would have to reroll the dice only if they rolled the wrong one in the first place, and would then have to repeat any steps that depended upon the result of that dice; however, if they rolled the dice correctly but took an illegal step later on, the result of the original dice roll would still be used in the redone step.)
* 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.

==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, a Designer can spend only their own values, and a rule that allows Designers to transfer a numeric value only allows them to transfer that value from themselves to another Designer (of their choice unless otherwise stated).
* A Designer 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 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 a default value but no defined starting value, then its default value should also be considered a starting value. If a game variable has neither a default value nor a starting value, then both may be considered to be 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 the rules that define a game variable are amended, and some previously valid values become invalid as a consequence, any existing variables whose current values would become invalid are instead set to their starting value.
* Invalid values for game variables can never be used, even if the values stored in a gamestate-tracking entity 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 Dice Roller if N is greater than one million.

===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 [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (e.g. 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 (e.g. “two days after this Proposal enacts, Designer 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 (e.g. “04/10/09”), it shall be assumed that the date is in a day/month/year format.
* A Designer may not take more than one dynastic game action at the same time (excluding any actions which have been ongoing for more than three hours).

===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.
* The terms “Player” and “Designer” are synonyms.
* Designers 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”.

===Names===
* Within the Ruleset, a word only refers to the name of a Designer if it is explicitly stated that it refers to a Designer’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 any valid representation of a tag or tags. i.e. a Proposal named “Changes [Core]” could instead be referred to by the name “Changes”.
* When referring to a Rule, the name used in reference to a specific Rule may be simplified by not including any valid representation of a tag or tags, and, in the case of Special Case Rules, any asterisks, as long as such a reference would be unambiguous.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any other 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 Special Case Rule has equal precedence as a Dynastic Rule, unless that Special Case Rule explicitly says it can’t be overruled by a Dynastic Rule;
# If two contradicting parts have equal precedence, the part with more limited scope applies (e.g. if the rules “Designers may Kick each other” and “Designers may not Kick each other on Tuesdays” exist, and it is Tuesday, Designers may not Kick each other);
# If two contradicting parts have the same scope, the negative rule applies (e.g. with “Designers may Punch a Spaceman on Friday” and “Designers may not Punch Spacemen on Friday”, then Designers may not Punch Spacemen on Friday).

==Mentors==

Whenever a new Designer joins the game, the Lead Developer should select an active Designer who has indicated their willingness to act as a mentor and ask them to take that new Designer on as a mentee. The Lead Developer should wherever possible take care to consider game balance when selecting a potential mentor. The approached prospective mentor may decline to act as a mentor, in which case the Lead Developer should continue to approach other prospective mentors until one agrees or there are no available candidates who have not declined. If there are no available candidates then the Lead Developer may act as the new Designer’s mentor themselves, or the new Designer must go without a mentor.

A relationship between a mentor and a mentee is a Mentorship. Whenever a new Mentorship is established, the Lead Developer should announce it in a blog post.

===Things that a mentor must do===

A mentor must do the following:

*Make pro-active contact with their mentee when appointed, and explain the dynamics of the Mentorship system;
*Be available to answer any questions that their mentee may have about the game, including explaining the rules, common standards and etiquette of play, proofreading posts and clarifying game events;
*Introduce their mentee to the various platforms of the game, including the wiki, Slack, and end-of-dynasty notifications through the Facebook group or Twitter;
*If possible, give their mentee a nudge if it appears that they are at risk of becoming Idle;
*If they themselves go idle, communicate with their mentee to either continue to support them as an idle Designer or arrange a handover to another mentor if requested.

===Things that a mentor should do===
The following sets out suggested best practice for Mentorship relationships:

*The Mentorship should last for at least four weeks or until the next Ascension Address, whichever occurs latest. It can continue for longer but after this threshold the mentor is no longer bound by any of the conditions set out in the parent rule to this rule, or any of its subrules.
*The mentor can and should advise the mentee on how to proceed in the mentee’s own best interests. This can include making connections with other Designers.
*The mentor should consider copying the mentee in on private, game-related communications, where it does not unfairly prejudice their own interests. The mentee should keep this information private without explicit consent from the mentor.
*The mentor and mentee may work together to achieve victory. If a mentor achieves victory with support of their mentee then they should, if the mentee wishes it, pass the baton to the mentee.

===Things that a mentor should not do===
The following sets out a list of things that a mentor should not do in their relationship with their mentee. All of these are considered to be Fair Play rules, as per the rule Fair Play.

*The mentor should not sock-puppet, bully, coerce or otherwise manipulate the mentee into performing any game actions.
*The mentor should not seek to dissuade the mentee from pursuing other alliances.
*A former mentor should not seek to use the fact of a prior Mentorship to influence the former mentee on an ongoing basis.

</div>

Second Switch bugs

2020-07-26T16:02:18Z

Tantusar: A joke, and a more serious note.

* Between two column mode and one column mode, there's an unnecessary three column mode. The width range occupied by this mode would be better served by two column mode. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 04:54, 22 June 2020 (UTC)
* The wiki signup password should only appear for logged-in users. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 04:54, 22 June 2020 (UTC)
* Post titles do not link to the relevant post from pages where multiple posts are displayed. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 04:54, 22 June 2020 (UTC)
* "Proposal:" prefixes aren't displayed on the individual post pages (eg. https://wp.blognomic.com/2020/06/14/queueing/) --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 10:07, 22 June 2020 (UTC)

* <s>If a post title wraps onto a second line, the voting icon expands to match the height... Clashing with the text to its right.</s> [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 04:54, 22 June 2020 (UTC)
** <s>Not fixed in previous wave.</s> [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 13:12, 22 June 2020 (UTC)
* Admins appear to have no access to make necessary adjustments to users' profiles (setting Active/Idle springs to mind). [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 14:10, 22 June 2020 (UTC)
* It is unclear how Admins can promote other Users to Admins as allowed by Proposals. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 14:10, 22 June 2020 (UTC)
* Error in the Quick Draft dialog: Notice: Undefined index: post_status_ in /home/blognomic/wp.blognomic.com/wp-content/plugins/extended-post-status/admin/class-extended-post-status-admin.php on line 684. [[User:Publius Scribonius Scholasticus|Publius Scribonius Scholasticus]] ([[User talk:Publius Scribonius Scholasticus|talk]]) 15:02, 22 June 2020 (UTC)
* <s>Wordpress-generated links to any part of member profiles are suffixed with <code>/profile</code>, which breaks all of them. There exist some links which should end <code>/profile</code> in this way, but not all.</s> [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 13:31, 22 June 2020 (UTC)
** <s>Not fixed in previous wave.</s> [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 03:04, 23 June 2020 (UTC)
* <s>Red colouration of posts in pending section has no relation to staleness of said posts?</s> [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 05:52, 23 June 2020 (UTC)
* Frequently I arrive on the site and it refuses to acknowledge that I've logged in until I have clicked on an individual post. A hard-refresh does not resolve the issue. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 12:40, 23 June 2020 (UTC)
** This is almost certainly because you're logged in on https://, but are currently visiting on http://. It's been bothering me too. I will start forcing https:// shortly. [[User:75th Trombone|75th Trombone]] ([[User talk:75th Trombone|talk]]) 03:19, 24 June 2020 (UTC)
* Pagination isn't paginating. The post limit is clearly set to 10, but there are also clearly more than 10 posts to a page. There are, in fact, currently all the posts to a page. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 17:50, 23 June 2020 (UTC)
** The limit you are seeing is a ''page'' limit, not a post limit. The post limit per page is I believe 20, and Elementor is honoring the WordPress global setting for this. And of course, there aren't even 20 posts on the new blog yet. The pagination will page up to 10 pages of 20 posts each; beyond that, you just have to rely on monthly archives. Though it raises the question of whether you can see more than 200 posts on a monthly archive. Will keep an eye on this. [[User:75th Trombone|75th Trombone]] ([[User talk:75th Trombone|talk]]) 03:19, 24 June 2020 (UTC)
* Closed (Enacted/Failed) votable matters (IMO) should display a link to the comments and a comment count instead of removing it once comments are closed. [[User:Pokes|Pokes]] ([[User talk:Pokes|talk]]) 13:24, 25 June 2020 (UTC)
** Seconded: the extremes of comment counts are both worth knowing about (that there was a huge discussion, or that a proposal was maybe scammed through with minimal voting), when catching up on the blog. --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 14:21, 26 June 2020 (UTC)
* <s>"pokes' test CfJ" is marked as "Adminned at 25 Jun 2020 01:21:47 UTC", but it was adminned at 13:21:47 UTC.</s> [[User:Pokes|Pokes]] ([[User talk:Pokes|talk]]) 13:26, 25 June 2020 (UTC)
** Lowercase H vs uppercase H: The age-old debate... Uppercase H is always correct. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 17:15, 25 June 2020 (UTC)
Everything above this line should be fixed. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 11:59, 2 July 2020 (UTC)
-----

* No username at top of member pages? [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 03:09, 23 June 2020 (UTC)
** Yep, aware of this, fix to come [[User:75th Trombone|75th Trombone]] ([[User talk:75th Trombone|talk]]) 03:19, 24 June 2020 (UTC)
* Posts and comments on Home tab of member pages have no relation to the member's activity? [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 03:09, 23 June 2020 (UTC)
** Not aware of this until now, will look into it [[User:75th Trombone|75th Trombone]] ([[User talk:75th Trombone|talk]]) 03:19, 24 June 2020 (UTC)
* <span style='color:red'>'''!!!'''</span> Method of styling site (primary fonts and colours, <s>switching between image-based and text-based header</s>) unclear. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 12:18, 25 June 2020 (UTC)
** Would it be helpful to have a settings page in the WordPress backend for common requirements? Could that settings page include a dropdown list of players for the current emperor? [[User:Tantusar|Tant* usar]] ([[User talk:Tantusar|talk]]) 12:49, 25 June 2020 (UTC)
** Image vs text header resolved as soon as tagline is enabled for editing. Customize > Site Identity. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 18:52, 27 June 2020 (UTC)
* The favicon isn't. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 19:59, 25 June 2020 (UTC)
* More feature request than bug, but myself and Clucky are both interested in non-Gravatar avatars. - Pokes
** And a minor nit, the comment avatars being circular mismatch the square sidebar ones. [[User:Pokes|Pokes]] ([[User talk:Pokes|talk]]) 00:37, 26 June 2020 (UTC)
* Sticky posts are unstyled. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 07:55, 27 June 2020 (UTC)
** Stopgap implemented until better solution found. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 15:25, 27 June 2020 (UTC)
* Unclear how to get email notifications related to posts and comments. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 08:04, 27 June 2020 (UTC)
* 75th mentioned a signup Captcha on the /register page to prevent spammers, but I'm not seeing one (even after clicking submit when making a test account). --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 14:21, 28 June 2020 (UTC)
** Recent innovations in Captcha technology result in the majority of human submissions not requiring a human test in order to be accepted as valid. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 15:44, 28 June 2020 (UTC)
* <span style='color:red'>'''!!!'''</span> Becoming a player is unintuitive, requiring re-saving your profile, likely with no actual changes to its content. It may be better to require admin intervention in a similar way to EE.BN. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 11:59, 2 July 2020 (UTC)
* The RSS comments feed (https://wp.blognomic.com/comments/feed/) doesn't contain all comments; as of this writing the most recent is the comment on PSS' template by PSS on June 30. [[User:Pokes|Pokes]] ([[User talk:Pokes|talk]]) 12:02, 2 July 2020 (UTC)
** This may be related to the specific messing around with statuses we're doing. (Published is removed from the list on Proposals, among other things.) Interestingly, the status' archive pages (for example https://wp.blognomic.com/status/enacted ) are also failing to dredge anything up. This may also be related. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 12:09, 2 July 2020 (UTC)
* Where a post is closed with no comments, the "No Comments" text is hidden. It's not hidden when there were one or more comments. (This is currently the case for the "Add To Cart" proposal on the front page.) --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 09:18, 6 July 2020 (UTC)
* I'm sometimes getting a four-second load time on the site, before anything appears at all - I think this tends to happen if I've not looked at it for a while, so it could be about loading in all that uncached Javascript in the head tag (including a google.com/recaptcha script which it loads even if I'm logged in?). It's also felt like longer sometimes. --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 10:34, 6 July 2020 (UTC)
* <span style='color:red'>'''!!!'''</span> I can see other peoples' PMs, for example, at https://wp.blognomic.com/members/75th-trombone/messages/ . [[User:Pokes|Pokes]] ([[User talk:Pokes|talk]]) 13:16, 7 July 2020 (UTC)
* Dates are appearing at the top of every post on the front and monthly archive pages, even when there are multiple posts in a day. (EE skips dates where they would repeat.) If Wordpress can't do this, we may as well drop it entirely rather than try and fail to mimic the look of the old site. --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 11:55, 8 July 2020 (UTC)
** To truly mimic EE, it would need to only work properly half the time. /s [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 16:02, 26 July 2020 (UTC)
* Comments have no datestamps. Is that an oversight, or something we've decided we can live without for the sake of a cleaner design? It may become an issue in dynasties where eg. a daily action takes place in comments. If to keep the design simple, we could bury it in some hover text. --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 16:02, 24 July 2020 (UTC)
* I can edit my comments with no obvious sign to other users that I've done so. Are we okay with that, or (at least) okay adding with a Fair Play rule of "don't edit your comments after others have replied to them"? --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 16:02, 24 July 2020 (UTC)
* On another comment editing note, players appear to be able to edit any comments on posts they have made. [[User:Tantusar|Tantusar]] ([[User talk:Tantusar|talk]]) 16:02, 26 July 2020 (UTC)

[[Category:The Second Switch]]

Second Switch Ruleset

2020-07-24T17:57:10Z

Tantusar: /* Designers */ "Adminship Part 2"

{{TOCRight}}

<div style="padding:8px;background:#ddd;">

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for the BlogNomic WordPress test; all Designers shall obey it. Henceforth in this document, "BlogNomic" refers to the BlogNomic WordPress test at https://wp.blognomic.com, ''not'' the main BlogNomic game at https://blognomic.com, unless otherwise specified.

It comprises four Sections: 1) the “core rules” of BlogNomic, covering the essential elements of gameplay; 2) the rules of the current Dynasty; 3) rules which apply in special cases; and 4) the appendix, which complements and clarifies the Ruleset.

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

If the Ruleset does not properly reflect all legal changes that have been made to it, any Designer may update it to do so.

== Designers ==
Any active Designer of the main BlogNomic game at https://blognomic.com may sign up for a BlogNomic WordPress test account, using the same name and email address they use at the main BlogNomic game, at https://wp.blognomic.com/register. When they have saved their profile fields with “Player status” set to “Active” and appear as an active player in the sidebar, they become a Designer.

A Designer may only change their name as a result of a Proposal approving the change.

Some Designers are '''Admins''', responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Admins at the main BlogNomic game shall become Admins of the BlogNomic WordPress test when they become a Designer of the BlogNomic WordPress test, unless they request otherwise, and any Admin at the main BlogNomic game may become an Admin of the WordPress Test game at any time by posting a notice to that effect. Upon the posting of such a notice, any other Admin should make the necessary profile changes at their earliest opportunity and comment to the Notice to confirm that they are complete. Designers of the main BlogNomic game who are not Admins there may not become Admins of the BlogNomic WordPress test.

===Idle Designers===

If a Designer is Idle, this is tracked by their "Designer status" profile field being set to "Idle", thus removing their name from the list of currently active Designers in the Sidebar. For the purposes of all Gamestate and the Ruleset, excluding Rules “Ruleset and Gamestate”, “Designers”, “Dynasties”, “Fair Play” and any of those Rules’ subrules, Idle Designers are not counted as Designers.

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

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

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

Admins who are unidling themselves should, in their first vote following each unidling, highlight their changed idle status and any changes to Quorum to have come about as a result of it.

Idle Admins can enact and fail Votable Matters.

== Dynasties ==
BlogNomic is divided into a number of '''Dynasties'''. Each Dynasty may be headed by a single Designer, known as the Lead Developer. If there is no Lead Developer, the Dynasty is a Metadynasty.

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

===Votes===
Each Designer may cast one Vote on a Votable Matter by making a top-level 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 Designer’s Vote on a Votable Matter is the last valid voting icon that they have used in any top-level comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a top-level comment to the post, then the author’s Vote is FOR. A non-Designer never has a Vote, even if they were a Designer previously and had cast a valid Vote.

If a Designer other than the Lead Developer casts a vote of DEFERENTIAL, then the Vote of DEFERENTIAL is an indication of confidence in the Lead Developer. When the Lead Developer 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 Lead Developer’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 Designers who are not voting AGAINST it is less than Quorum.
* It has been open for voting for at least 48 hours and it is not Popular.

=== Enacting and Failing ===

Votable Matters can either be Pending, Enacted, or Failed. When a Votable Matter is first put forward, it is considered Pending.

Whenever an Admin Resolves a Votable Matter, they should mark their name, and are highly encouraged to report the final tally of Votes (or the fact that it was self-killed or vetoed). Comments cannot be made on Enacted or Failed Votable Matters.

This rule cannot be overruled by Dynastic Rules in its application to Calls for Judgement or Declarations of Victory.

===Tags===
Votable Matters must have the tag/s “Core”, “Special Case” and/or “Appendix” to amend the Core Rules, the Special Case Rules and/or the Appendix, respectively.

Votable Matters other than [[#Victory and Ascension|DoVs]] require the tag “Victory” in order to grant victory to a Designer.

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

=== Special Proposal Voting ===

When a Designer 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 Lead Developer may use VETO as a voting icon to cast a Vote on a Proposal; when the Lead Developer casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Lead Developer later changes their Vote.

=== 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 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 Designers actively disagree as to the interpretation of the Ruleset, or if a Designer feels that an aspect of the game needs urgent attention, then any Designer 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 true:

* 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 any gamestate-tracking entities, as specified in the CfJ.

This Rule may not be overruled by Dynastic Rules.

== Victory and Ascension ==

If a Designer (other than the Lead Developer) believes that they have achieved victory in the current Dynasty, they may make a '''Declaration of Victory''' (abbreviated “DoV”) detailing this, by posting an entry in the “Declaration of Victory” category.

Every Designer may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty. If there is at least one pending DoV, BlogNomic is [[#hiatus|on Hiatus]].

A Pending DoV may be Enacted by any Admin if any of the following are true:

* It is Popular, it has been open for at least 12 hours, and either the Lead Developer 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.

If a DoV is Failed and it had at least one AGAINST vote, the Designer who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was Failed.

When a DoV is Enacted, all other pending DoVs are Failed, and a new Dynasty begins in which the Designer who made the DoV becomes the Lead Developer.

The new Lead Developer will make an '''Ascension Address''' by posting an entry in the “Ascension Address” category. This should specify the Lead Developer’s chosen theme for the new Dynasty, and it may optionally specify that the terms “Designer” and “Lead Developer” will be replaced with theme-specific terms throughout the entire Ruleset (where the replacement terms are different, and neither includes any words in a form in which they already appear in the non-dynastic Ruleset), and/or list a number of dynastic rules to keep. When such an Ascension Address is posted, the Ruleset is updated to reflect any changed terms, and any dynastic rules which were not listed to be kept are repealed. Between the enactment of the DoV and the posting of the Ascension Address, no new DoV may be made and BlogNomic is on Hiatus.

Before an Ascension Address has been posted for a new Dynasty, the Lead Developer may pass the role of Lead Developer to another Designer by making a post to that effect.

This rule cannot be overruled by Dynastic Rules as it relates to Declarations of Victory, but it 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 Designer’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. Designers should vote against any DoV that relies on having broken a fair play rule.

* A single person should not control more than one non-Idle Designer within BlogNomic, and should announce publicly if they control both a non-Idle Designer and any Idle Designers.
* A Designer 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 Designer should not deliberately exploit bugs or unexpected behaviours in the software running the game (WordPress, MediaWiki or other blognomic.com scripts).
* A Designer should not edit their own blog comments once posted, nor those of any other Designer.
* A Designer should not edit the “Entry Date” field of a blog post.
* A Designer should not make a DoV primarily to delay the game by putting it into Hiatus.
* A Designer 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 Designer should not roll dice 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 Designer must use their own name in the Dice Roller, when rolling dice.
* A Designer should not deliberately and unreasonably prolong the performance of a game action once they have started it.
* A Designer should not use a core, special case or appendix rules scam to directly or indirectly achieve victory.
</div>

= Dynastic Rules =

== Elementor Basics ==

When any of the following terms is used in reference to the contents of a page on https://wp.blognomic.com, they refer to their meaning in the Elementor page builder and [[https://docs.elementor.com/ its documentation]]:

* Section
* Column
* Widget
* Template

Any of the above terms may be preceded by the word “Elementor” for clarity.

When referring to the contents of a page on https://wiki.blognomic.com, including the Ruleset itself, these terms do not refer to their meaning in Elementor unless specified otherwise.

== The Second Switch Page ==

The page at [https://wp.blognomic.com/second-switch-page https://wp.blognomic.com/second-switch-page], if it exists, is known as the Second Switch Page or SSP, and is Gamestate. Its WordPress title shall be “Second Switch Page”.

The SSP shall consist of one or more Elementor Sections and their contents.

No SSP Sections may contain any Columns not authorized by the Ruleset. No SSP Columns may contain any Widgets not authorized by the Ruleset. No Designer, even Admins, may change the settings of SSP Sections or Columns from their default settings, except as explicitly permitted by the Ruleset.

The topmost Section on the SSP shall contain one Column, and that Column shall contain one “Page Title” Widget, set to display the page’s title. The settings of this widget may be changed at the discretion of the Lead Developer, provided that the settings do not break any rules.

All other SSP Sections shall collectively be known as the Canvas, and individually known as Canvas Sections.

=== The Canvas ===

Only Admins may edit the Canvas, and Admins may only edit it as the Ruleset allows.

All Canvas Sections shall contain between 2 and 4 Columns. All the columns within a Canvas Section must be equally wide, and all together must be the full width of the Section.

All of a Canvas Section’s Columns must contain at least one Widget.

New Widgets being added into empty Columns must follow the following algorithm (depicted [[:File:Second Switch Page Canvas algorithm.gif|here]]), unless otherwise permitted in the Ruleset:

# No Widget may be added to an empty Canvas until 2 Widgets are ready to be populated at the same time. (This is implied by the requirements that Canvas Sections must have at least 2 Columns, and that all Columns must have at least one Widget.)
# The order of Widgets will always be preserved left-to-right then top-to-bottom, in the order that their addition was required or requested.
# When 2 Widgets are ready to be added, the Admin editing the Canvas will create the first Canvas Section with a two-column layout, then add them.
# When the 3rd Widget is ready to be added, the Section will have 3 columns.
# When the 4th Widget is ready, the Section will have 4 columns.
# When the 5th Widget is ready, the Section will have 3 columns, and a new Section below it will have 2.
# When the 6th Widget is ready, the older Section and newer Section will both have 3 Columns.
# When the 7th Widget is ready, the older Section will have 4 Columns and the newer one 3.
# When the 8th Widget is ready, both older and newer Sections will have 4.
# When the 9th Widget is ready, the algorithm repeats the pattern started in step 6 above, with the “newer” Section now considered the “older” one, and another new Section created below it.

=== Designer Templates ===

All Designers may create one regular Elementor Template (not a Theme Builder or Popup Template), named “[Playername]’s Template”, where [Playername] is replaced by the Designer’s BlogNomic name. Such Templates are known as “Designer Templates”.

After creating their Designer Template, a Designer may make a blog post requesting an Admin to populate it into the Canvas, or, if they are an Admin, announcing that they will do so themselves. No Designer Template may be populated into the Canvas without such a post being made. The Admin should confirm that the Template abides by the Ruleset before populating it, and if it is found not to abide by the Ruleset, the Admin must decline to populate it and comment on the request explaining which rule they think it breaks and why. The creator of the Designer Template must then make a new post requesting that it be populated into the Canvas.

Designer Templates are populated into the Canvas by adding an Elementor “Template” Widget to an empty Column, then choosing the Template.

A Designer Template shall have only one Section, containing only one Column, and shall have no Widgets not permitted by the Ruleset. However, the Designer may change any of their Template’s Sections' settings, Columns' settings, and/or Widgets’ settings — except for Custom CSS, which must remain empty unless otherwise permitted — in any way not forbidden by the Ruleset.

No part of a Designer Template may ever exceed the bounds of its Column on the Canvas by any method, including but not limited to overly large fonts or relative/absolute positioning. This includes all browser widths; therefore, Designers should test their Templates at all browser widths and make width-specific adjustments as supported by Elementor if need be.

A Designer may edit their Designer Template as often as they wish if it is not yet populated into the Canvas. If it is populated into the Canvas, the Designer may edit it in any permissible way as a Daily Action. If a Designer Template on the Canvas is found to break a rule, the Designer may edit it at any time to make it conform to the rules, even if the rules regarding Daily Actions would prohibit it; however, such an edit still counts as a Daily Action for the purposes of determining whether a future edit to this template is legal. Such an edit must be announced in a blog post before being made, and may not make any changes not related to making the Designer Template conform to the rules.

Any Designer may challenge the legality of any other Designer’s Designer Template by making a post to the Votable Matter category tagged with “SSP”, and whose text explains the illegality and proposes a change to the Template to make it conform to the rules. If the post is Enacted, the proposed change shall be made by the enacting Admin. Such a Votable Matter is not required, however; if a Designer can be convinced in any informal way that their Template breaks the rules, they may simply announce their change and make it, as described above.

=== Permitted Widgets ===

A Designer Template shall have, as its topmost Widget, an Elementor “Heading” Widget, whose text must always be the same as the Designer Template’s name. The font size of this heading must be less than or equal to 24 pixels or 1.5 rems.

==== Icon Box or Image Box ====

A Designer Template may have one of the following: (1) up to two “Icon Box” Widgets, (2) up to two “Image Box” Widgets, or (3) an “Icon Box” Widget and an “Image Box” Widget. No image or icon within the chosen Widget may appear taller than 200 CSS pixels at any browser width. No text within it may have a font size greater than 24 pixels or 1.5 rems. Designers may create or upload any image to which they have distribution rights for use in an Image Box widget, so long as it does not violate any other rules.

==== Inventory ====

A Designer Template may have a single "Icon List" widget, with exactly three list items which unambiguously state the number of Products, Ideas, and Clients (collectively called Resources) owned by that Template's Designer. The icons of these three items shall be "Box", "Lightbulb", and "User" respectively. No text within this Widget may have a font size greater than 24 pixels or 1.5 rems.

== Income ==

When updating their Template, a Designer may increase the amount of a Resource they own by at most X, where X is the number of days since their last edit to the Template. This may only be done if the Template (prior to editing) contains an "Image Box" Widget or an "Icon Box" Widget matching that Resource.

An "Image Box" Widget is considered to match:

* Clients, if it contains an image which shows a person.
* Products, if it does not match Clients and contains an image which shows a man-made object.
* Ideas, if it does not match any other Resource.

An "Icon Box" Widget is considered to match a Resource if it contains the icon used to represent that Resource, as defined under "Inventory" in the "Permitted Widgets" subrule.

<br/>
<div style="padding:8px;background:#bbb;">

= Special Case =
'''Special Case Rules''' can be Active or Inactive. A Special Case Rule should be tagged with its status. Otherwise, its status is its Default Status.

Special Case Rules have a '''Default Status''', which can be Active or Inactive. If the title of a Special Case Rule includes an asterisk, (*) its Default Status is Inactive, otherwise, its Default Status is Active.

When a new Dynasty is started, the Ascension Address may list any number of existing Special Case Rules to be set to a status other than their respective Default Status. All other Special Case Rules are set to their respective Default Status.

The text of a Special Case Rule that is Inactive is flavour text.

==Seasonal Downtime [Active]==
On the 24th, 25th and 26th of December, BlogNomic is [[#hiatus|on Hiatus]]. In addition, game actions defined by the rules titled “Designers” and “Victory and Ascension” (with the exception of Voting in DoVs) may not be taken.

==Dormancy [Inactive]==
If there are fewer than five Designers, BlogNomic is [[#hiatus|on Hiatus]].

==Imperial Deferentials [Active]==
If the Lead Developer has voted DEFERENTIAL on a Proposal, that vote is instead considered to be valid and either FOR (if more Designers have voted FOR the Proposal than have voted AGAINST it) or AGAINST (in all other cases).

==Dynastic Distance [Active]==
For the purposes of dynastic rules which do not deal with voting, the Lead Developer is not a Designer.

==The Traitor [Active]==
The Traitor for a particular Dynasty may be a Designer (including an idle one), or may be nobody, and it defaults to being nobody. The Traitor’s identity in the current Dynasty is tracked privately by the Lead Developer, and the Lead Developer should not share this information with Designers other than the Traitor.

If there is no Traitor for the current Dynasty, and BlogNomic is not on Hiatus, the Lead Developer may secretly randomly select a Designer (other than the Lead Developer) and privately inform them that they are the Traitor for the current Dynasty.

A Traitor is under no obligation to honour any informal promises they have made with other Designers, nor to tell the truth to them, and is encouraged to betray other Designers in order to achieve victory.

</div>
<div style="padding:8px;background:#ddd;">

= 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. (e.g. 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 WordPress weblog at [https://wp.blognomic.com wp.blognomic.com]. A top-level comment is a comment which is not a reply to another comment.

;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 Designers.

;Daily Action
:If a game action is a Daily Action, each Designer 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 Designer 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 “DICEX” or “YDICEX” refer to X-sided dice and Y amount of X-sided dice, rolled using the Dice Roller.

;Dynastic Action
:An action that is defined in the Dynastic rules.

;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 Designer’s Effective Vote Comment with respect to a given Votable Matter is that Designer’s Comment to that Votable Matter, if any, that contains that Designer’s Vote on that Votable Matter.

;Commentary
:When posting a blog entry, a Designer 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.

;Flavour Text
:If a part of the ruleset is defined as being “flavour text”, it is gamestate and remains part of the ruleset document, but is not considered to have any meaning beyond being a string of characters. Designers are not required to obey flavour text and may not perform any action defined by it, and any statements that flavour text makes about gamestate are ignored.

;Gamestate
:Any information which the Ruleset regulates the alteration of. All wiki pages that the Dynastic Rules explicitly mention (except for dynastic histories and discussion pages) and any images or Templates contained within those Wiki Pages are assumed to be Gamestate.

;<span id="hiatus">Hiatus</span>
:If BlogNomic is on Hiatus, Dynastic Actions may not be taken, and Proposals may not be submitted or Resolved. If multiple rules require BlogNomic to be on Hiatus at any given time, BlogNomic will continue to be on Hiatus until no rules require it.

;Introduction: The introduction of a rule is the part of that rule’s text before any subrules.

;Post
:A blog post published to the BlogNomic WordPress weblog at [http://wp.blognomic.com wp.blognomic.com]

;Private Message
:A message sent via BlogNomic’s Private Messages system at wp.blognomic.com.

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

;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 subrules 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. Designers 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 (e.g. #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.

;Tag: A Post may have any number of tags applied to it using the WordPress interface. A Rule may have any number of tags applied to it. Rule tags are represented by appending to their title a comma-separated list of such tags, enclosed in square brackets.

;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 https://wp.blognomic.com/wp-content/uploads/icons/for.svg shall represent a Vote FOR, an X https://wp.blognomic.com/wp-content/uploads/icons/against.svg shall represent a Vote AGAINST, a DEF https://wp.blognomic.com/wp-content/uploads/icons/imperial.svg shall represent a Vote of DEFERENTIAL, and a crossed-out circle https://wp.blognomic.com/wp-content/uploads/icons/veto.svg shall represent a vote to 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 Designer 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 Designer per week.

;Wiki
:The BlogNomic Wiki at http://wiki.blognomic.com

== Gamestate Tracking ==

===Official Posts===

Votable Matters and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at [https://wp.blognomic.com https://wp.blognomic.com]. Any Designer may [https://wp.blognomic.com/wp-admin/post-new.php 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.

An official post may only be removed as allowed by the Ruleset.
An official post may be altered by its author if it is less than two hours old and either no Designer has commented on it or (if it is a Votable Matter) if all comments on it contain no voting icons; otherwise this can only be done as allowed by the Ruleset. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post’s Status must be changed to reflect its status. An official blog post that has the status of Enacted or Failed cannot change categories. An official blog post’s status may never be altered except in accordance with the rules that define that official post.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following two exceptions: Firstly, whilst a non-official post has been posted for less than fifteen minutes and has no comments, the author may change the categories as they wish. Secondly, if a post by a New Designer is not in any category but follows the wording of a Proposal, in that it has written changes the gamestate and or Ruleset, and if it has been posted for less than six hours, then any Admin may change it to be in the Proposal category. A New Designer is defined as a Designer who has been a Designer for fewer than seven days or a Designer that has unidled in the past seven days after being idle for at least 3 months.

Any post that is or is made illegal as a result of an infraction against any of the prohibitions set out in this rule continues to be an Official Post but may no longer have any effect on the ruleset or the gamestate. If it is a Votable Matter then it is Unpopular, regardless of any other performance against criteria set out in the core rules. When it is resolved it may be marked as Illegal by the resolving admin. A post that is illegal in this manner cannot subsequently be made legal by any means.

===Representations of the Gamestate===

For gamestate which is tracked in a specific place (such as a wiki page), any alteration of that gamestate as a result of a Designer’s action is (and can only be) applied by editing that data in that place. One 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 wiki merely represents the Gamestate tracked there, and is not the same thing. In the event that the Gamestate and its representations are different, any Designer may correct the representations to comply with the Gamestate.

If a Designer feels that a representation of the gamestate (such as a wiki page) 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 alteration, Designers are encouraged to raise a Call for Judgement instead.

The historical fact of the occurrence of a defined game action is itself considered to be gamestate, tracked in the history of whatever resource is used to track the gamestate modified by that action, where possible, or in the wiki page [[Gamestate Modifications]] if this is not possible.

===Orphan Variables===

An Orphan Variable is a dynastic gamestate variable which has neither a location in which it’s tracked, nor a reasonable manner in which it can be determined from other gamestate variables, specified in the Ruleset.

A Designer may not take any dynastic actions that are contingent on the specific value of an Orphan Variable.

=== Random Generators ===
The Dice Roller at https://blognomic.com/dice/roll.php can be used to generate random results.

* The DICE''N'' command can be used to generate a random number between 1 and ''N''.
* The FRUIT command will return a random result from the following options: Lemon, Orange, Kiwi, Grape, Cherry, Tangelo.
* The COLOUR (or COLOR) command will return a random result from the following: White, Red, Green, Silver, Yellow, Turquoise, Magenta, Orange, Purple, Black.
* The CARD command will return a card with a random suit (either Hearts, Diamonds, Spades or Clubs) and a random value (either Ace, 2, 3, 4, 5, 6, 7, 8, 9, 10, Jack, Queen, King). A card with a value that is either Jack, Queen or King is a face card.

Any changes to the potential outcomes of the Dice Roller’s random result commands must be made by Proposal.

If a Proposal proposes a change to this rule that would require server-level access to the BlogNomic site to fully enact its effects, that Proposal must name a Designer with such access. Only a Designer with such access may Enact that Proposal. If that Proposal does not name a Designer with such access, that Proposal is Illegal.

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 Dice Roller, unless otherwise specified. If a selection is explicitly specified as being “secretly” random, the Designer making this determination may do so using a private method of their choosing, instead of the Dice Roller.

==Atomic Actions==

An Atomic Action combines otherwise separate game actions into a single action.

* All steps of an Atomic Action are considered one action, including the steps of an Atomic Action that is itself a step of a parent Atomic Action.
* When a Designer performs an Atomic Action, they must complete all its steps; they must complete them in order; and they may not take any other dynastic action, or achieve victory, until all the steps are complete.
* An Atomic Action may direct the Designer performing it to skip some of its steps, which the Designer must do and in which case the skipped steps are considered completed for this rule.
* If a Designer arrives at a step in an Atomic Action and they cannot perform that step, they undo all the steps they have performed of that Action and are considered never to have performed that Action.
* If one or more steps of an Atomic Action were done incorrectly, the Designer must redo the Atomic Action; for that purpose, the Designer uses any legal steps that have already been completed in the illegal Atomic Action and only redoes the illegal ones. (For example, if an Atomic Action consists of rolling a dice and then doing steps based upon its result, the Designer would have to reroll the dice only if they rolled the wrong one in the first place, and would then have to repeat any steps that depended upon the result of that dice; however, if they rolled the dice correctly but took an illegal step later on, the result of the original dice roll would still be used in the redone step.)
* 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.

==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, a Designer can spend only their own values, and a rule that allows Designers to transfer a numeric value only allows them to transfer that value from themselves to another Designer (of their choice unless otherwise stated).
* A Designer 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 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 a default value but no defined starting value, then its default value should also be considered a starting value. If a game variable has neither a default value nor a starting value, then both may be considered to be 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 the rules that define a game variable are amended, and some previously valid values become invalid as a consequence, any existing variables whose current values would become invalid are instead set to their starting value.
* Invalid values for game variables can never be used, even if the values stored in a gamestate-tracking entity 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 Dice Roller if N is greater than one million.

===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 [[#Proposals|Proposal]] would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (e.g. 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 (e.g. “two days after this Proposal enacts, Designer 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 (e.g. “04/10/09”), it shall be assumed that the date is in a day/month/year format.
* A Designer may not take more than one dynastic game action at the same time (excluding any actions which have been ongoing for more than three hours).

===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.
* The terms “Player” and “Designer” are synonyms.
* Designers 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”.

===Names===
* Within the Ruleset, a word only refers to the name of a Designer if it is explicitly stated that it refers to a Designer’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 any valid representation of a tag or tags. i.e. a Proposal named “Changes [Core]” could instead be referred to by the name “Changes”.
* When referring to a Rule, the name used in reference to a specific Rule may be simplified by not including any valid representation of a tag or tags, and, in the case of Special Case Rules, any asterisks, as long as such a reference would be unambiguous.

===Prioritisation===
* If two parts of the Ruleset contradict each other, precedence shall be construed in the following order:
# The Appendix has precedence over any other 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 Special Case Rule has equal precedence as a Dynastic Rule, unless that Special Case Rule explicitly says it can’t be overruled by a Dynastic Rule;
# If two contradicting parts have equal precedence, the part with more limited scope applies (e.g. if the rules “Designers may Kick each other” and “Designers may not Kick each other on Tuesdays” exist, and it is Tuesday, Designers may not Kick each other);
# If two contradicting parts have the same scope, the negative rule applies (e.g. with “Designers may Punch a Spaceman on Friday” and “Designers may not Punch Spacemen on Friday”, then Designers may not Punch Spacemen on Friday).

==Mentors==

Whenever a new Designer joins the game, the Lead Developer should select an active Designer who has indicated their willingness to act as a mentor and ask them to take that new Designer on as a mentee. The Lead Developer should wherever possible take care to consider game balance when selecting a potential mentor. The approached prospective mentor may decline to act as a mentor, in which case the Lead Developer should continue to approach other prospective mentors until one agrees or there are no available candidates who have not declined. If there are no available candidates then the Lead Developer may act as the new Designer’s mentor themselves, or the new Designer must go without a mentor.

A relationship between a mentor and a mentee is a Mentorship. Whenever a new Mentorship is established, the Lead Developer should announce it in a blog post.

===Things that a mentor must do===

A mentor must do the following:

*Make pro-active contact with their mentee when appointed, and explain the dynamics of the Mentorship system;
*Be available to answer any questions that their mentee may have about the game, including explaining the rules, common standards and etiquette of play, proofreading posts and clarifying game events;
*Introduce their mentee to the various platforms of the game, including the wiki, Slack, and end-of-dynasty notifications through the Facebook group or Twitter;
*If possible, give their mentee a nudge if it appears that they are at risk of becoming Idle;
*If they themselves go idle, communicate with their mentee to either continue to support them as an idle Designer or arrange a handover to another mentor if requested.

===Things that a mentor should do===
The following sets out suggested best practice for Mentorship relationships:

*The Mentorship should last for at least four weeks or until the next Ascension Address, whichever occurs latest. It can continue for longer but after this threshold the mentor is no longer bound by any of the conditions set out in the parent rule to this rule, or any of its subrules.
*The mentor can and should advise the mentee on how to proceed in the mentee’s own best interests. This can include making connections with other Designers.
*The mentor should consider copying the mentee in on private, game-related communications, where it does not unfairly prejudice their own interests. The mentee should keep this information private without explicit consent from the mentor.
*The mentor and mentee may work together to achieve victory. If a mentor achieves victory with support of their mentee then they should, if the mentee wishes it, pass the baton to the mentee.

===Things that a mentor should not do===
The following sets out a list of things that a mentor should not do in their relationship with their mentee. All of these are considered to be Fair Play rules, as per the rule Fair Play.

*The mentor should not sock-puppet, bully, coerce or otherwise manipulate the mentee into performing any game actions.
*The mentor should not seek to dissuade the mentee from pursuing other alliances.
*A former mentor should not seek to use the fact of a prior Mentorship to influence the former mentee on an ongoing basis.

</div>

Second Switch bugs

2020-07-11T11:53:57Z

Tantusar: