Building Blocks
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 Guild is a Associate.
Malign Emperors
If “Mantle Passing” is active, the Guild may be recipient of the Mantle as if they were a Associate. The Guild 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 Guild 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 Associate may remove this rule from the ruleset.
No Private Communication
Associates 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 Associate 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 Associates (or people who are not yet Associates) also face the same restrictions if they intend to become an active Associate 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 the mentor and the mentee should not pursue strategies that is based on the private information of the other party.
The restrictions on communication due to the Rule No Private Communication do not apply during an Interregnum.
If information which was not allowed to be discussed is still privately discussed, the Associates who were part of the conversation should make a post to the blog disclosing what information was discussed at their earliest convenience.
Mantle Passing
During an Interregnum, the new Guild may Pass the Mantle by making a post naming a Associate who was not the last dynasty’s Guild; the passing Associate then ceases to be the Guild and the Associate so named becomes the Guild.
Declared Alliances
Each Associate may have an Alliance, which is publicly tracked, and consists of the distinct names of no more than two other Associates; a Associate's Alliance defaults to an empty set. A Associate may change their Alliance as a daily action.
If “Mantle Passing” is not active, and if a Associate 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 Associate may pass the Mantle to a Associate (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 Associates who each have the other’s names in their Alliance.
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 Guild 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 Guild 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 Associate (other than the Guild) 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 Associate 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 Guild is privately tracking any information about them then they should do likewise at their first opportunity. If a Associate has Reinitialised during the current dynasty, then, for the purposes of determining the validity of limited actions, they are considered to have undertaken no actions in this dynasty prior to their most recent Reinitialisation.
Virtual Actions
A Virtual Action is a type of action that the Guild performs on behalf of a Associate. A Associate may initiate a virtual action by privately communicating to the Guild their request to do so, along with any additional information needed to carry it out. The Guild 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 Associate, and indicate to the Associate that their action has succeeded.
If a Virtual Action fails, the Guild should tell the Associate 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 Guild to do something they cannot do.
- Any other reason specified by the action itself.
Except where otherwise stated by the ruleset, the Guild 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 Associate may cancel a pending Virtual Action by privately communicating to the Guild their request to do so.
When the performance of a Virtual Action causes the modification of publicly tracked gamestate, the Guild should publicly track the historical fact of the occurrence of that Virtual Action on behalf of the Associate who initiated that Virtual Action, using the Guild’s own name in that public tracking, and privately track the historical fact of the occurrence of that Virtual Action using the name of the Associate who initiated that Virtual Action.
No Cooperation
In this dynasty, Associates are expected to avoid co-operating to effect Victory, except through the use of co-operative mechanisms defined in the Dynastic rules, general strategic advice that does not involve planning coordinated actions and resources between two or more Associates, 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 Associates are considered to be Associates for the purposes of this rule.
If a Associate feels that another Associate has gone against this expectation in some way during the current dynasty, then they are encouraged to vote against all DoVs from that Associate during that dynasty. If a Associate feels that a DoV has come about as a result of one or more other Associates 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 and Ascension”.
Precondition Unidling
A Proposal that would (if adopted) amend the dynastic ruleset or dynastic gamestate, and that was submitted by an idle Associate, is known as Precondition Call.
Idle Associates may submit Precondition Calls as if they were not idle. The author of a Precondition Call is not considered to have a vote on that Proposal while they remain idle, and Recusants may not vote on Precondition Calls
If a Precondition Call enacts, the enacting admin must unidle its author immediately after enacting that Proposal (unless such an unidling would be impossible, perhaps because the author was already unidled)
Protected Edit Window
An official post may be altered by its author if it is less than 4 hours old. This rule supersedes the rule “Edit Window”, if it exists.