Difference between revisions of "Building Blocks"
(→Mantle Limiations: typo fix) |
(New synonyms) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
==Everyone’s Playing== | ==Everyone’s Playing== | ||
| − | For the purposes of all dynastic and Building Blocks rules, the | + | For the purposes of all dynastic and Building Blocks rules, the Head Researcher is a Genetic Engineer. |
==Malign Emperors== | ==Malign Emperors== | ||
| − | + | If “Mantle Passing” is active, the Head Researcher may be recipient of the Mantle as if they were a Genetic Engineer. The Head Researcher may not cast a vote of VETO on any Proposal whose effect is limited to the dynastic rules or gamestate; any such vote is disregarded for the purposes of proposal resolution. The Head Researcher may not use the rule “Official Posts” to move posts into the proposal category. | |
| − | If there is a Building Block rule called No Private Communication then any | + | If there is a Building Block rule called No Private Communication then any Genetic Engineer may remove this rule from the ruleset. |
==No Private Communication== | ==No Private Communication== | ||
| − | + | Genetic Engineers may not privately communicate with each other about dynastic gameplay or votable matters that affect the dynastic ruleset or gamestate. Private communications are considered to be anything that any other Genetic Engineer could not reasonably be privy to, perceive, or understand. Discussion conducted in plain English on the BlogNomic wiki and blog, and the #current-dynasty, #blognomic-general and #new-player-questions-and-mentorships Discord channels, are not considered to be private communication. Idle Genetic Engineers (or people who are not yet Genetic Engineers) also face the same restrictions if they intend to become an active Genetic Engineer during the course of the dynasty. The use of creative strategies to circumvent this rule may be considered to be a scam for the purposes of determining whether an infraction of Fair Play has taken place. | |
A mentor and mentee may still privately converse with each other, but should keep their conversations away from discussing specific gameplay strategy. This rule’s restrictions on communication do not apply during an Interregnum. The restrictions in this rule on communication in non-blognomic-related media shall not be construed as to cause those media to be gamestate. | A mentor and mentee may still privately converse with each other, but should keep their conversations away from discussing specific gameplay strategy. This rule’s restrictions on communication do not apply during an Interregnum. The restrictions in this rule on communication in non-blognomic-related media shall not be construed as to cause those media to be gamestate. | ||
| − | If information which was not allowed to be discussed is still privately discussed, the | + | If information which was not allowed to be discussed is still privately discussed, the Genetic Engineers who were part of the conversation should make a post to the blog disclosing what information was discussed as their earliest convenience. |
| − | ==Mantle | + | ==Mantle Passing== |
| − | + | During an Interregnum, the new Head Researcher may Pass the Mantle by making a post naming an Genetic Engineer who was not the last dynasty’s Head Researcher; the passing Genetic Engineer then ceases to be the Head Researcher and the Genetic Engineer so named becomes the Head Researcher. | |
==Declared Alliances== | ==Declared Alliances== | ||
| − | Each | + | Each Genetic Engineer may have an Alliance, which is publicly tracked, and consists of the distinct names of no more than two other Genetic Engineers; a Genetic Engineer's Alliance defaults to an empty set. A Genetic Engineer may change their Alliance as a daily action. |
| − | If | + | If “Mantle Passing” is not active, and if a Genetic Engineer has achieved victory in this dynasty, has posted a Declaration of Victory which has been enacted, and did not change their Alliance for at least the 48 hours immediately prior to the posting time of their Declaration of Victory: then that Genetic Engineer may pass the Mantle to a Genetic Engineer (as if “Mantle Passing” were active) who was named in their Alliance at the posting time of their Declaration of Victory. |
| − | If “No Private Communication” is active, it does not apply to communications between | + | If “No Private Communication” is active, it does not apply to communications between Genetic Engineers who each have the other’s names in their Alliance. |
==Event Types== | ==Event Types== | ||
| Line 36: | Line 36: | ||
* Creation Condition(s). Unless they are met, an Event of that type may not be posted. They may include a format for the body of the post. | * Creation Condition(s). Unless they are met, an Event of that type may not be posted. They may include a format for the body of the post. | ||
* Ending Condition(s). Unless they are met, an Open Event of that type may not be Ended. | * Ending Condition(s). Unless they are met, an Open Event of that type may not be Ended. | ||
| − | * Ending Action(s). | + | * Ending Action(s). A Genetic Engineer (or the Head Researcher) must do these when they End an Open Event of that type. |
| − | An Event is either Open or Ended, defaulting to Open. Except as otherwise specified, any | + | An Event is either Open or Ended, defaulting to Open. Except as otherwise specified, any Genetic Engineer (or the Head Researcher) may post or may End an Event. To End an Event is to make it Ended by submitting a comment on that post saying it is Ended or is being Ended, and then immediately taking its Ending Action(s), if any. Once an Event has been Ended, it may not become Open again, nor may it be Ended again. |
==Bounties== | ==Bounties== | ||
A Bounty Notice is a post in the Story Posts - Votable Matter category which broadly requests a single mechanical or ruleset change. Despite its category, it is not a votable matter and any votes on it are ignored. A Bounty Notice may be Open or Closed being Open by default and being Closed when set to the ‘Enacted’ or ‘Failed’ status in the post backend. The Enacted Status should be used for successfully completed Bounty Notices, while Failed should be used for ones that were closed for any other reason | A Bounty Notice is a post in the Story Posts - Votable Matter category which broadly requests a single mechanical or ruleset change. Despite its category, it is not a votable matter and any votes on it are ignored. A Bounty Notice may be Open or Closed being Open by default and being Closed when set to the ‘Enacted’ or ‘Failed’ status in the post backend. The Enacted Status should be used for successfully completed Bounty Notices, while Failed should be used for ones that were closed for any other reason | ||
| − | The | + | The Head Researcher may post a Bounty Notice, or close an open Bounty Notice, at any time. |
If a Bounty Payout action is not defined in the dynastic rules, then the Bounty Payout action is that nothing happens. | If a Bounty Payout action is not defined in the dynastic rules, then the Bounty Payout action is that nothing happens. | ||
| − | If the | + | If the Head Researcher believes that one or more enacted votable matters satisfy the demand of an open Bounty Notice, then they may apply the Bounty Payout action to each Genetic Engineer (other than the Head Researcher) who authored at least one of those votable matters and set that Bounty Notice to closed. |
==Reinitialisation== | ==Reinitialisation== | ||
| − | If they have not already done so in the current dynasty, | + | If they have not already done so in the current dynasty, A Genetic Engineer may make a post to the blog announcing that they are Reinitialising; if they do so then they must immediately set all of their gamestate tracked values to their defaults for new players, and if the Head Researcher is privately tracking any information about them then they should do likewise at their first opportunity. When a Genetic Engineer has Reinitialised, they are considered to have undertaken no actions in this dynasty for the purposes of determining the validity of limited actions taken after the Reinitialisation, except for the action of Reinitialising itself. |
==Virtual Actions== | ==Virtual Actions== | ||
| − | A Virtual Action is a type of action that the | + | A Virtual Action is a type of action that the Head Researcher performs on behalf of a Genetic Engineer. A Genetic Engineer may initiate a virtual action by privately communicating to the Head Researcher their request to do so, along with any additional information needed to carry it out. The Head Researcher shall resolve the Virtual Action by performing the following Atomic Action: |
# Determine whether the Virtual Action fails (if it does not fail, it is successful). | # Determine whether the Virtual Action fails (if it does not fail, it is successful). | ||
| − | # If the action is successful, apply any specified effects on the gamestate and/or perform any specified actions on behalf of the | + | # If the action is successful, apply any specified effects on the gamestate and/or perform any specified actions on behalf of the Genetic Engineer. |
| − | If a Virtual Action fails, the | + | If a Virtual Action fails, the Head Researcher should tell the Genetic Engineer why. A virtual action may fail for any of these reasons: |
* Some requirements/prerequisites to perform the action are not met. | * Some requirements/prerequisites to perform the action are not met. | ||
* The request does not contain all the information needed to resolve the action. | * The request does not contain all the information needed to resolve the action. | ||
* The request is unintelligible, or too vague to interpret unambiguously. | * The request is unintelligible, or too vague to interpret unambiguously. | ||
| − | * It would require the | + | * It would require the Head Researcher to do something they cannot do. |
* Any other reason specified by the action itself. | * Any other reason specified by the action itself. | ||
| − | Except where otherwise stated by the ruleset, the | + | Except where otherwise stated by the ruleset, the Head Researcher must resolve all virtual actions in the order that they are received. A virtual action is considered to have occurred at the time it was resolved. |
| − | Until a virtual action is resolved, it is pending. | + | Until a virtual action is resolved, it is pending. A Genetic Engineer may cancel a pending Virtual Action by privately communicating to the Head Researcher their request to do so. |
==No Cooperation== | ==No Cooperation== | ||
| − | In this dynasty, | + | In this dynasty, Genetic Engineers are expected to avoid co-operating to effect Victory, except through the use of co-operative mechanisms defined in the Dynastic rules, any activities carried out as part of a Mentorship, and the posting of votable matters and casting of votes. The Mentor clause that a Mentor and mentee “may work together to achieve victory” does not apply in this dynasty. |
| − | Idle | + | Idle Genetic Engineers are considered to be Genetic Engineers for the purposes of this rule. |
| − | If a | + | If a Genetic Engineer feels that another Genetic Engineer has gone against this expectation in some way during the current dynasty, then they are encouraged to vote against all DoVs from that Genetic Engineer during that dynasty. If a Genetic Engineer feels that a DoV has come about as a result of one or more other Genetic Engineers making a sincere attempt to ‘kingmake’ for the Declarant, even if the author of the DoV was not a party to that cooperation, then they are encouraged to vote against it. This overrules the encouragement to vote according to the perception of a victory in the rule “Victory in Ascension”. |
Latest revision as of 21:12, 19 October 2024
Contents
Building Blocks
Low-Player Mode
The Core Rule Dormancy is flavour text.
Everyone’s Playing
For the purposes of all dynastic and Building Blocks rules, the Head Researcher is a Genetic Engineer.
Malign Emperors
If “Mantle Passing” is active, the Head Researcher may be recipient of the Mantle as if they were a Genetic Engineer. The Head Researcher may not cast a vote of VETO on any Proposal whose effect is limited to the dynastic rules or gamestate; any such vote is disregarded for the purposes of proposal resolution. The Head Researcher may not use the rule “Official Posts” to move posts into the proposal category.
If there is a Building Block rule called No Private Communication then any Genetic Engineer may remove this rule from the ruleset.
No Private Communication
Genetic Engineers may not privately communicate with each other about dynastic gameplay or votable matters that affect the dynastic ruleset or gamestate. Private communications are considered to be anything that any other Genetic Engineer could not reasonably be privy to, perceive, or understand. Discussion conducted in plain English on the BlogNomic wiki and blog, and the #current-dynasty, #blognomic-general and #new-player-questions-and-mentorships Discord channels, are not considered to be private communication. Idle Genetic Engineers (or people who are not yet Genetic Engineers) also face the same restrictions if they intend to become an active Genetic Engineer during the course of the dynasty. The use of creative strategies to circumvent this rule may be considered to be a scam for the purposes of determining whether an infraction of Fair Play has taken place.
A mentor and mentee may still privately converse with each other, but should keep their conversations away from discussing specific gameplay strategy. This rule’s restrictions on communication do not apply during an Interregnum. The restrictions in this rule on communication in non-blognomic-related media shall not be construed as to cause those media to be gamestate.
If information which was not allowed to be discussed is still privately discussed, the Genetic Engineers who were part of the conversation should make a post to the blog disclosing what information was discussed as their earliest convenience.
Mantle Passing
During an Interregnum, the new Head Researcher may Pass the Mantle by making a post naming an Genetic Engineer who was not the last dynasty’s Head Researcher; the passing Genetic Engineer then ceases to be the Head Researcher and the Genetic Engineer so named becomes the Head Researcher.
Declared Alliances
Each Genetic Engineer may have an Alliance, which is publicly tracked, and consists of the distinct names of no more than two other Genetic Engineers; a Genetic Engineer's Alliance defaults to an empty set. A Genetic Engineer may change their Alliance as a daily action.
If “Mantle Passing” is not active, and if a Genetic Engineer has achieved victory in this dynasty, has posted a Declaration of Victory which has been enacted, and did not change their Alliance for at least the 48 hours immediately prior to the posting time of their Declaration of Victory: then that Genetic Engineer may pass the Mantle to a Genetic Engineer (as if “Mantle Passing” were active) who was named in their Alliance at the posting time of their Declaration of Victory.
If “No Private Communication” is active, it does not apply to communications between Genetic Engineers who each have the other’s names in their Alliance.
Event Types
An Event is an official post that meets a type definition in the dynastic rules, if and only if that type definition is specified as defining a type of Event; the type definition must include the following:
- A type name, such as “Auction” or “Quest”. A post with the Event type’s name as a tag is an Event of that type, provided it was (legally) posted while the type had a complete definition.
- A Response Format, the format by which a comment on that type of Event is classified as a Response for that Event. While other comments are allowed on an Event, only those comments which conform to its type’s Response Format are officially considered Responses. Whether or not a comment is currently considered a Response may change according to circumstances, but comments submitted on an Event while it is Ended can never be considered Responses.
An Event type definition may also optionally stipulate:
- Creation Condition(s). Unless they are met, an Event of that type may not be posted. They may include a format for the body of the post.
- Ending Condition(s). Unless they are met, an Open Event of that type may not be Ended.
- Ending Action(s). A Genetic Engineer (or the Head Researcher) must do these when they End an Open Event of that type.
An Event is either Open or Ended, defaulting to Open. Except as otherwise specified, any Genetic Engineer (or the Head Researcher) may post or may End an Event. To End an Event is to make it Ended by submitting a comment on that post saying it is Ended or is being Ended, and then immediately taking its Ending Action(s), if any. Once an Event has been Ended, it may not become Open again, nor may it be Ended again.
Bounties
A Bounty Notice is a post in the Story Posts - Votable Matter category which broadly requests a single mechanical or ruleset change. Despite its category, it is not a votable matter and any votes on it are ignored. A Bounty Notice may be Open or Closed being Open by default and being Closed when set to the ‘Enacted’ or ‘Failed’ status in the post backend. The Enacted Status should be used for successfully completed Bounty Notices, while Failed should be used for ones that were closed for any other reason
The Head Researcher may post a Bounty Notice, or close an open Bounty Notice, at any time.
If a Bounty Payout action is not defined in the dynastic rules, then the Bounty Payout action is that nothing happens.
If the Head Researcher believes that one or more enacted votable matters satisfy the demand of an open Bounty Notice, then they may apply the Bounty Payout action to each Genetic Engineer (other than the Head Researcher) who authored at least one of those votable matters and set that Bounty Notice to closed.
Reinitialisation
If they have not already done so in the current dynasty, A Genetic Engineer may make a post to the blog announcing that they are Reinitialising; if they do so then they must immediately set all of their gamestate tracked values to their defaults for new players, and if the Head Researcher is privately tracking any information about them then they should do likewise at their first opportunity. When a Genetic Engineer has Reinitialised, they are considered to have undertaken no actions in this dynasty for the purposes of determining the validity of limited actions taken after the Reinitialisation, except for the action of Reinitialising itself.
Virtual Actions
A Virtual Action is a type of action that the Head Researcher performs on behalf of a Genetic Engineer. A Genetic Engineer may initiate a virtual action by privately communicating to the Head Researcher their request to do so, along with any additional information needed to carry it out. The Head Researcher shall resolve the Virtual Action by performing the following Atomic Action:
- Determine whether the Virtual Action fails (if it does not fail, it is successful).
- If the action is successful, apply any specified effects on the gamestate and/or perform any specified actions on behalf of the Genetic Engineer.
If a Virtual Action fails, the Head Researcher should tell the Genetic Engineer why. A virtual action may fail for any of these reasons:
- Some requirements/prerequisites to perform the action are not met.
- The request does not contain all the information needed to resolve the action.
- The request is unintelligible, or too vague to interpret unambiguously.
- It would require the Head Researcher to do something they cannot do.
- Any other reason specified by the action itself.
Except where otherwise stated by the ruleset, the Head Researcher must resolve all virtual actions in the order that they are received. A virtual action is considered to have occurred at the time it was resolved.
Until a virtual action is resolved, it is pending. A Genetic Engineer may cancel a pending Virtual Action by privately communicating to the Head Researcher their request to do so.
No Cooperation
In this dynasty, Genetic Engineers are expected to avoid co-operating to effect Victory, except through the use of co-operative mechanisms defined in the Dynastic rules, any activities carried out as part of a Mentorship, and the posting of votable matters and casting of votes. The Mentor clause that a Mentor and mentee “may work together to achieve victory” does not apply in this dynasty.
Idle Genetic Engineers are considered to be Genetic Engineers for the purposes of this rule.
If a Genetic Engineer feels that another Genetic Engineer has gone against this expectation in some way during the current dynasty, then they are encouraged to vote against all DoVs from that Genetic Engineer during that dynasty. If a Genetic Engineer feels that a DoV has come about as a result of one or more other Genetic Engineers making a sincere attempt to ‘kingmake’ for the Declarant, even if the author of the DoV was not a party to that cooperation, then they are encouraged to vote against it. This overrules the encouragement to vote according to the perception of a victory in the rule “Victory in Ascension”.
