BlogNomic Wiki - User contributions [en]

The Eighth Metadynasty

2026-06-12T20:12:54Z

Whirlingstars:

[[File:Blognomic8th.gif|right]]
'''October 5, 2017 — November 4, 2017'''

== Ascension Address ==

Welcome to the Eighth Metadynasty of Blognomic. This is the longest blognomic has gone without entering meta-dynasty. 39 dynasties have passed since Sept 4, 2013, when purplebeard ended the Seventh Metadynasty.

All dynastic rules have been reset. Cuddlebeam is no longer a King. Princes remain Princes, which is suitably generic if not particularly themed. The Imperial vote mechanism will do nothing until we have a king or until a function is assigned it.

While it is customary to have a hiatus between dynasties, no declaration of victory has been made, and no ascension address can be made. And we only have 25 days to Halloween. So I invite all of you to start making rules immediately.

As indicated in the initiating proposal, this dynasty is Halloween themed. Will it end in a trick of rules? or in the treat of involved and clever gameplay?

-- Derrick

==Players==
The following players were active at the end of the Dynasty: Axemabaro, card*, Cuddlebeam, Darknight*, derrick*, Trigon

<nowiki>*</nowiki>: denotes admins 

==Final Ruleset==
[[Ruleset 152]]

==Gamestate==

* [[Pumpkin Boulevard]]

==Posts of Interest==

* [https://blognomic.com/archive/recolor_appendix_core Recolor] - Specified the actual theme of the dynasty more than "Halloween"
* [https://blognomic.com/archive/trick_or_treat Trick or Treat] - Established the Trick and Treat values that would soon become crucial to the gameplay
* [https://blognomic.com/archive/costume_selection Costumes] - Created Costumes that Trick-or-Treaters could wear
* [https://blognomic.com/archive/pumpkin_boulevard Pumpkin Boulevard] - Created the neighborhood
* [https://blognomic.com/archive/walking Walking] - Defined how one could move around Pumpkin Boulevard
* [https://blognomic.com/archive/the_big_night Time] - Divided the game up into separate time periods
* [https://blognomic.com/archive/give_me_something_good_to_eat Give Me Something Good to Eat] - Defined the act of trick-or-treating
* [https://blognomic.com/archive/candy_counting Candy Counting] - Defined a scoring mechanism

==Ascension==

After tabulating the scores, Axemabaro had 46 points compared to Trigon's 23 and card's 10. Therefore, Axemabaro won.

==Commentary==

This dynasty had a long list of mechanics, some of which were never used. For the most part, however, player engagement was high. Unfortunately, only three people actually ended up trick-or-treating at the end.
This dynasty also had the opportunity to be open mostly during OCTOber while being the eighth metadynasty.

I didn't pay much attention during this dynasty lol. I regret that though, since the finale was basically "Whoever pulls off the best finishing combo wins" and HNNNNGGG that shit is just my favorite.--[[User:Cuddlebeam|Cuddlebeam]] ([[User talk:Cuddlebeam|talk]]) 10:56, 23 November 2017 (UTC)

{{Dynastic Histories}}

Pumpkin Boulevard

2026-06-12T20:11:40Z

Whirlingstars:

{{gamestate|The Eighth Metadynasty}}

=Values=
Time: The Big Night

=Locations=
{|class="wikitable"
!Valid Locations
!Connections
|-
|Main Street
|Cauldron Avenue, Pumpkin Boulevard, Nightmare Way, Hardware Store, Police Station
|-
|Cauldron Avenue
|Main Street, Gated Fence, Cemetery
|-
|Pumpkin Boulevard
|Main Street, Sidewalk
|-
|Nightmare Way
|Main Street, Beach
|-
|Addams
|Sidewalk
|-
|Scarecrows
|Sidewalk
|-
|Misers
|Sidewalk
|-
|Tuckers
|Sidewalk
|-
|Joneses
|Sidewalk
|-
|Greenbergs
|Sidewalk
|-
|Sidewalk
|Addams, Scarecrows, Misers, Tuckers, Greenbergs, Joneses, Pumpkin Boulevard
|-
|Hardware Store
|Main Street
|-
|Police Station
|Main Street
|-
|Cemetery
|Cauldron Avenue, Spooky Woods
|-
|Spooky Woods
|Cemetery
|-
|Gated Fence
|Cauldron Avenue, Ominous Castle
|-
|Ominous Castle
|Gated Fence
|-
|Beach
|Nightmare Way, Shipwreck
|-
|Shipwreck
|Beach
|}

=Houses=
==Adams==
Costume Type Preference: spooky 
Candy Type: Licorice 
Gullibility: 4 
Trick Value: 0 

==Scarecrows==
Costume Type Preference: sneaky 
Candy Type: Corn 
Gullibility: 3 
Trick Value: 5 
Dropped items: 4 gummy bears 

==Misers==
Candy Type: Gummy Bears 
Candy Quantity: 15 
Trick Value: 0 

==Tuckers==
Costume Type Preference: spooky 
Candy Type: Suckers 
Gullibility: 5 
Trick Value: 0 

==Greenbergs==
Costume Type Preference: ecologically responsible 
Candy Type: Apples 
Gullibility: 6 
Trick Value: 0 

==Joneses==
Costume Type Preference: expensive 
Candy Type: King Size Snickers 
Gullibility: 7 
Trick Value: 6

Doomsday Device

2026-06-12T20:08:11Z

Whirlingstars: this is from Ruleset 54

{{gamestate|The First Dynasty of Purplebeard}}

#The idol that houses John DeFoe's soul.
#A fresh corpse, which will fall onto the idol and be possessed by John DeFoe when a rope is cut.
#Stewie Griffin cutting the rope to drop the corpse while yelling "Victory is mine".
#A solar panel providing power to the speaker and blade-spring of the cardboard Griffin cutout.
#A Friken Laser; device that emits a beam of light to pinpoint a target with a glowing red dot.
#A prisoner, tied up to fall in a certain direction when killed by John DeFoe.
#A ravenous shark, to which the Friken Laser is attached with nylon cord.
#A big red button, which the dead prisoner will fall on to.
#A huge box suspended in the air, filled with explosive ping pong balls, that has a trapdoor in the bottom that opens when the big red button is pressed.
#A giant pirahna, who is blown up by the ping pong balls.
#A fairskinned damsel, who shrieks at the sight of giant toothy fish.
#A skittish hamster, who begins running in his wheel when awoken by shrieking.
#A shoelace tied to the hamster wheel, which would be wound up when spun.
#A table cloth tied to the shoelace.
#A goldfish bowl on the table cloth, inching toward the edge of the table.
#The bulldog from Tom & Jerry asleep on his pillow beside the table.
#A weather control device, which maintains heavy cloud cover over the device, preventing the sunlight from reaching the solar panel.
#Super Happy Fun Ball (carefull it's dangerous).
#A string tied to the bulldog.
#Tied to the business end of the string, the RELEASE switch on a dump truck full of Mentos backed over an Olympic-sized swimming pool filled with Diet Coke, which erupts and destroys the moon.
#A spaceman on the moon unaware that the moon is about to be destroyed.
#An ejecting mechanism on the spaceman's helmet which sends it into orbit around the Earth.
#A family of gremlins, who lived inside the helmet, who leap out in despair.
#A group of children, clapping in glee at the fireworks display of gremlins burning up on reentry to the atmosphere.
#A wall lamp activated by the sound of clapping.
#A solar panel, which turns the light of the wall lamp into electricity, which powers a huge animatronic dinosaur.

Ruleset

2026-06-12T20:01:57Z

Whirlingstars: /* Insolvency */ Spelling correction

{{TOCRight}}

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

= Core Rules =

== Ruleset and Gamestate ==
This is the '''Ruleset''' for BlogNomic; all Associates shall obey it.

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 set metagame parameters for the current dynasty; 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 text of the Ruleset document does not reflect all legal changes that have been authorised to be made to it, any Associate may update it to do so.

The gamestate tracking page for this dynasty is the [[Guild Business]] page of the wiki. Unless otherwise stated, all publicly tracked gamestate information is tracked on it.

== Associates ==
A human with access to the blog who is not already an Associate may make a blog post making clear their wish to be an Associate (plural form Associates); in response, an Admin shall add them to the roster in the sidebar, at which moment they become an Associate. (See the FAQ for guidance on how to apply for access to the BlogNomic blog.)

Some Associates are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Associates who wish to become Admins should submit a Proposal or CfJ to that effect. An Admin may make a blog post clearly stating their wish to resign under this rule. In response, any Admin may remove them from their post as Admin.

An Associate may cease to be an Associate at any time by posting an entry to the BlogNomic weblog requesting such an action. A human who has ceased to be an Associate in this way may not become an Associate again within the following two weeks.

===Idle Associates ===
An Associate may be either Active or Idle. An Associate is only Active if their name is on the list of currently active Associates in the Sidebar; otherwise they are Idle.

An Associate may request to become Idle at any time by making a post or comment to that effect. An Admin may render an Associate Idle if that Associate has asked to become Idle in an entry or comment from the past 96 hours (4 Days), or if that Associate has not posted an entry or comment in the past 168 Hours (7 days). Admins may render themselves Idle at any time, but should announce it in a post or comment when they do so.

For the purposes of all Gamestate and the Ruleset, excluding the core and appendix Rules “Ruleset and Gamestate”, “Associates”, “Dynasties”, “Fair Play”, “Imperial Tracking”, “Mentors” and any of those Rules’ subrules, Idle Associates are not counted as Associates. The combined term “Idle Associates” can be used to refer to Associates who are Idle even in Proposals or rules that do not treat them as Associates, and any Votable Matter that specifically refers to a named Idle Associate can affect them as if they were Active. Idle admins may act as Admins as if they were Active.

An Admin may make an Associate Active if that Associate is Idle and has asked to become Unidle in an entry or comment from the past 96 hours (4 Days), and Idle Admins may make themselves Active at any time, unless the Associate who would become Active has become Idle within the past 48 hours (2 days), and within the current Dynasty. Admins who are making any Associate Active should highlight the changed status of the relevant Associate and any changes to Quorum to have come about as a result of it as a comment to the entry requesting the change, or as part of their next vote comment if making themselves Active.

When an Associate is made Active, 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 Associate Idled in a different Dynasty), the Associate is given the default value for new Associates, if such a value exists.

When an Associate becomes idle due to inactivity, the Admin must announce the idling in a blog post, and the 168 Hour idle timeout is considered to be reduced to 96 hours for that Associate during the current and subsequent dynasty.

===Dormancy===
If there are fewer than four Active Associates (not including the Guild), then BlogNomic is on Hiatus.

===Recusants===
An Idle Associate may post or vote on a Proposal or CfJ provided that it does not, even conditionally, create, repeal, change, or amend dynastic rules or gamestate defined by dynastic rules (apart from idling or unidling Associates), or uphold, revert, or reject Dynastic Actions. An Idle Associate who makes or votes upon such a Proposal or CfJ is, for the purposes of that Proposal or CfJ, a Recusant. When resolving a Proposal or CfJ, all Idle Associates who are Recusants on that matter are considered to be Active solely for the purposes of determining whether it was legally posted, and for determining Quorum on that matter; and all otherwise valid votes cast by Recusants are considered to be valid votes cast by Active Associates.

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

An Interregnum is the period between dynasties, after a DoV has been enacted and before a Dynastic Reset has been performed. During an Interregnum the game is in hiatus; additionally, no DoVs may be made, and no Associate may achieve Victory. However, dynastic actions that are specifically permitted to be carried out during an Interregnum may be carried out.

If the game is in an Interregnum and the Guild has posted an Ascension Address during this Interregnum, then Proposals may be submitted as if the game was not in Hiatus.
If the game is in an Interregnum, Proposals may be submitted and resolved as if the game was not in Hiatus provided they do not change the Dynastic Rules or Gamestate defined by Dynastic Rules.

Unless otherwise stated by a dynastic or Building Blocks rule, then for the purposes of dynastic and Building Blocks rules, the Guild is not an Associate.

Each Dynasty is tracked by a number. The current Dynasty Number is 249.

The following Associate is the Guild: "Lawnomos".

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

===Votes===
Each Associate may cast one Vote on a Votable Matter by making a comment to the Official Post that comprises that Votable Matter using a voting icon of FOR, AGAINST, or DEFERENTIAL. Additional voting icons may be permitted in some cases by other rules. A valid Vote is, except when otherwise specified, a Vote of FOR or AGAINST. An Associate‘s Vote on a Votable Matter is the last valid voting icon that they have used in any comment on that Votable Matter. Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR. A non-Associate never has a Vote, even if they were an Associate previously and had cast a valid Vote.

If an Associate other than the Guild casts a vote of DEFERENTIAL, then the Vote of DEFERENTIAL is an indication of confidence in the Guild. When the Guild 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 Guild’s Vote for the purposes of other rules unless otherwise specified. When the Guild themselves casts a vote of DEFERENTIAL, it indicates an indication of confidence in the votes of the other players; please see the Rules and Votable Matters section of the Appendix for more information on how this is resolved.

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

This rule cannot be overruled by dynastic or Building Blocks rules in its application to Calls for Judgement or Declarations of Victory.

=== Enacting and Failing ===

Votable Matters have a status, which can either be Pending, Enacted, Failed, or Illegal. When a Votable Matter is first put forward it is considered Pending (which is tracked as having no status in the current blog software), and it remains Pending until it is Resolved.

A Votable Matter is resolved by an admin setting its status through use of the “status” field in the blog post editing form. When 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 withdrawn or vetoed). Comments cannot be made on resolved Votable Matters.

A Votable Matter may not be resolved except as directed by the ruleset, and the status of a resolved Votable Matter, once resolved, is determined by the votes cast upon it, as assessed by the rules that govern the specific kind of Votable Matter (as well as any other considerations regarding the legality of the Votable Matter, such as the stipulations put forward in the Appendix rule Official Posts). When a Failed proposal has been Vetoed it may optionally have the Vetoed status upon resolution, which is considered to be the same as Failed for the purposes of all other rules.

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

===Tags===
Votable Matters have zero or more tags. Tags are represented in the title of a Votable Matter with the format “[X]” (e.g. “[Core] Wording Fix”, where “[Core]” is the tag).

Votable Matters making changes to the Core Rules, the Building Blocks Rules or the Appendix Rules require any of the following to be true for each such change in order to make that specific modification to the ruleset:
* The Votable Matter has the appropriate Tag or Tags for that change: [Core] for Core Rules changes, [Building Blocks] for Building Blocks Rules changes and [Appendix] for Appendix Rules changes.
* The modification is preceded or followed immediately by an unambiguous statement of which section of the ruleset it takes place.
* The modification specifically states a rule using its number or the name of the stated rule only occurs once in the ruleset.

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

=== Special Proposal Voting ===

When an Associate casts a vote AGAINST their own Proposal (which is not in the form of a DEFERENTIAL vote), this renders the Proposal '''Withdrawn''', even if the author later changes their Vote. The Guild may use VETO as a voting icon to cast a Vote on a Proposal; when the Guild casts a vote of VETO on a Proposal, this renders the Proposal Vetoed, even if the Guild later changes their Vote.

=== Resolution of Proposals ===

The oldest Pending [[#Proposals|Proposal]] may be '''Enacted''' by any Admin if all of the following are true:

* It is Popular.
* It has been open for voting for at least 24 hours.
* It has not been Vetoed or Withdrawn.

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

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.

When a Proposal is Enacted, its stated effects are applied by treating the text in the Proposal as a series of steps starting from the beginning of that Proposal’s text and performing each step until reaching the end of that Proposal’s text, except that if the Admin Enacting it reaches a step which cannot be applied immediately (e.g. “two days after this Votable Matter enacts, Associate A gains 1 point”) or at all (e.g. applying to a rule which does not exist), that step is ignored for the purposes of Enactment; the Admin Enacting the Proposal shall update the Gamestate and Ruleset, and correct any gamestate-tracking entities, as specified in each step that was performed.

== Calls for Judgement ==
Any Associate or idle Associate may raise a Call for Judgement (abbreviated “CfJ”) by posting an entry in the “Call for Judgement” category. Calls for Judgement are intended to be used only to resolve disagreements about the interpretation of the Ruleset, to address aspects of the game that need urgent attention, or to address mistakes in gamestate tracking. If a CfJ is used for other purposes, this does not cause the CfJ to become invalid, but Associates are encouraged (but not required) to vote AGAINST such CfJs.

A vote of DEFERENTIAL on a CfJ is never considered a valid vote.

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 does not specify changes to the gamestate nor ruleset, does not specify that any attempt to perform an action should be upheld or rejected, and does not specify 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 an Associate (other than the Guild) 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.

An Associate’s vote on a DoV is encouraged to reflect whether or not they agree with the proposition that the poster has achieved victory in the current Dynasty. A vote of DEFERENTIAL on a DoV is never considered a valid vote. If there is at least one pending DoV, BlogNomic is [[#hiatus|on Hiatus]], no Idle Associate may be made unidle, and no new player joining requests may be administered.

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

* It has a FOR Vote from every Associate.
* It has been open for at least 24 hours and it has a number of FOR Votes that exceed or equal Quorum.

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.
* It is more than 48 hours old and cannot be Enacted

When a DoV is Enacted, all other pending DoVs are Failed, the Associate who posted the DoV becomes Guild, and the game enters an Interregnum. The player who Enacted it updates the rule “Dynasties” as specified in “Imperial Tracking”. When a DoV is enacted then all game actions that led up to it are considered to be upheld.

If the game is in an Interregnum then the new Guild must make an Ascension Address by posting an entry in the “Ascension Address” category. The Ascension Address may be altered by its author if it is less than 4 hours old and the Dynastic Reset action has not yet been performed since the initial posting of that Ascension Address. The Ascension Address should specify the Guild’s chosen theme for the new Dynasty, and it may optionally specifiy one or more of the following:
* New dynasty-specific terms as outline in the rule “Synonyms”
* A number of dynastic rules to keep (if none are specifed then the entire Dynastic Ruleset is repealed)
* Any number of Building Blocks rules to remove or insert, as per the instructions in the Building Blocks section
* The name of the gamestate tracking page referred to in the rule “Ruleset and Gamestate” to a different page that does not exist and does not start with the word “Ruleset”
* The Guild’s Imperial Style, which if specified is a set of nonbinding guidelines that the Guild is encouraged to follow, using the terms defined on the wiki page [[Imperial Styles]].

If it has not been done since the most recent posting of an Ascension Address, the Guild or any Associate (if it’s the latter, they must wait until at least 4 hours after that Ascension Address has been posted) may perform a Dynastic Reset, which is an atomic action with the following steps:
* Create a wiki page called “Ruleset X” where X is the current Dynasty Number, and replace that page’s contents with a copy of the current ruleset (replacing its contents if it already exists).
* Increase the current Dynasty Number by 1
* Update the Ruleset to reflect any changed terms as outlined in the most recent Ascension Address.
* Repeal any dynastic rules which were not listed to be kept in the most recent Ascension Address.
* Update the gamestate tracking page referred to in the rule “Ruleset and Gamestate” with the name specified in the most recent Ascension Address, if any. If no name is specified, set the gamestate tracking page to be “Gamestate Tracking X” where X is the current dynasty number
* Update the Building Blocks page to reflect any changes to the terms outlined in the rule Synonyms.
* Make any specified or automatic changes to the Building Blocks section of the ruleset as described in the most recent Ascension Address.

Once this Atomic Action has been completed the Interregnum ends and the new dynasty begins.

== Fair Play ==
The following are BlogNomic’s rules of '''fair play'''. If any of these rules are found to have been broken, or if an Associate’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. Associates 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 Associate within BlogNomic, and should announce publicly if they control both a non-Idle Associate and any Idle Associates. This extends to exerting full control over the actions of another Associate, defined here as the controlled Associate’s game behavior being functionally indistinguishable from if the controlling Associate was logged into their account and playing through it, over a period of more than a day.
* An Associate should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
* An Associate should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or other blognomic.com scripts).
* An Associate should not edit their own blog comments once posted, nor those of any other Associate.
* An Associate should not edit the “Entry Date” field of a blog post, except as permitted by the rule Date and Time Tracking in the Appendix.
* An Associate should not make a DoV primarily to delay the game by putting it into Hiatus.
* An Associate should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an Ascension Address).
* An Associate 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. an Associate must use their own name in the Dice Roller, when rolling dice.
* An Associate should not deliberately and unreasonably prolong the performance of a game action once they have started it.
* An Associate should not use a Core, Building Blocks, or Appendix rules scam to directly or indirectly cause an Associate to achieve victory. For the purposes of this bullet point, such a scam is one in which rules from one or more of these sections of the ruleset are used to achieve victory in a manner that does not have a dependency on a specific set of dynastic rules.
* An Associate should not trade actions in BlogNomic for favors or compensation outside of BlogNomic, nor trade actions in any other game for favors within BlogNomic, nor trade actions or favours in one Dynasty of Blognomic for actions or favours in another Dynasty of Blognomic.
*A person with administrative, moderation, or other heightened access to the software running or supporting BlogNomic should not take any action using such heightened access for the purpose of causing any Associate or Associates to gain, receive, maintain, or preserve gameplay advantage unless any of the following is true:
**Such action is required or explicitly permitted by the rules or required to implement an action required or explicitly permitted by the rules.
**A reasonable, impartial, and prudent external observer would deem such action necessary or reasonable for the purpose of supporting, moderating, or administering BlogNomic or such software.

All Associates and idle Associates should be aware of the BlogNomic [[Community Guidelines]]. The contents of this page are not ruletext and are nonbinding as pertains to the ruleset, but Associates are encouraged to commit to upholding them to whatever extent is possible.

</div>

= Dynastic Rules =

==The Presidency==

The President is publicly tracked, and is either an Associate, idle Associate, or empty.

Each Associate has a publicly tracked Ballot, which may be either blank (the default) or any Associate with a share, and an Associate may change their own Ballot anytime. If this rule has not been amended in the past 24 hours, if Associates owning Quorum of all Shares have set their Ballot to the same Associate (the Candidate), and this has been true for all of the past 24 hours, anyone may appoint the Candidate as President (unless the Candidate is already President).

If an Associate’s shares are ever set to 0, any Ballots which match that Associate are also set to the default value for a Ballot

===Shares===

Each Associate has a publicly tracked number of Shares, which defaults to the mean of all Player’s Shares, rounded down. The Share Price is publicly tracked and defaults to 5. Any Associate may Buy a Share as a Virtual Action by paying the Share Price in Credits. The Guild may (and should), once a Day, perform the Accounting action. When they do so, they, as an atomic action:
* Resolve all Buy a Share virtual actions
* Increase the Share Price by 1 for all Buy a Share virtual actions successfully resolved during this atomic action, and decrease Debt by that same number (to a minimum of 0)
* If the Share Price did not increase in the prior step, reduce the Share Price by 1 to a minimum of 3

The Guild may not otherwise resolve Buy a Share actions.

If an Action is a Timed Action, a given Associate may not perform it if they have already performed that same action since the last time the Accounting Action was performed. If an Action is a Timed Communal Action, it may not be performed if anyone has performed the same action since the last time the Accounting Action was performed. The time that the last Accounting Action was performed is publicly tracked.

As a Timed Action known as Discount Purchase, if an Associate’s Shares are equal to or less than the Median of all Shares, they may immediately perform Buy a Share as if the Share Price is one less than the actual Share Price.

==Systems and Directors==

The Guild operates in publicly tracked Systems, each identified by a unique flavour text name. Every System has a publicly tracked Director, which is an Associate, a Faction, or vacant (it’s default). If a System’s Director is vacant, the President may choose another Associate who controls a Vessel in that System and who is not already Director of a System to be that System’s Director. If a System is vacant and there are no Associates (other than the President) who are not already a Director of a System, any Associate or the Guild may set that System’s Director to the Faction whose Zone of Control contains that System and whose Zone of Control has more Systems than any other Faction whose Zone of Control contains that System, publicly randomly choosing among ties. If there are less than Quorum Systems, the Guild may create a new System, choosing a name from the [[List of Stars]] that does not start with the same letter as an existing System.

Each System has a publicly tracked Tax Rate, a number defaulting to 1. To Pay Taxes to a System, an Associate transfers a number of credits equal to that System’s Tax Rate to that System. As a Timed action, the Director of a System can change its Tax Rate to a number in the range 0 to 99 inclusive.

===Influence===

Each System has a publicly tracked ordered list of Associates known as its Influence List. If an Associate goes idle, they are removed from all Influence Lists they are on. If an Associate has a Vessel in a system, or they are the Director of that System, they may Influence that System by performing the following atomic action:

* Transfer 3 credits from themselves to the system (the rule Corruption may not be used for this transfer)
* Add themselves to the top of that System’s Influence List
* If that System’s Influence List has more than 10 total entries (including duplicates), remove the entry in the bottom of the list

A System’s Influence Scope is equal to the number of entries in its Influence List.

As a Timed Action, the Director of a System may decrease the System’s Credits by its Influence Scope, then increase each Associates Credit’s by the number of times they appear in that System’s Influence List

==Vessels==

Vessels are a type of object tracked by the game, and can only be created when allowed by the rules. If two Vessels have the same publicly tracked variables as each other, they are interchangeable for the purpose of the rules. Each Vessel is stationed in a particular System (publicly tracked), and has a publicly tracked Owner (an Associate, idle Associate, or the Guild). Each Vessel has a publicly tracked list of Produce, which is a possibly empty list of distinct Systems (i.e. duplicates are not allowed in the list), defaulting to empty. Produce represents the set of Systems from which that Vessel is carrying goods with which to trade.

At any time, the owner of a Vessel may add the System in which it is stationed to its Produce, unless it is already there (this is known as Exporting). Up to 3 times each week (but no more than once every 42 hours), an Associate may change the System in which one of their Vessels is stationed by Paying Taxes to both the System it was previously stationed at and the System it will be newly stationed at (unless the Class of the Vessel is Scout, in which case they must only perform Paying Taxes to the System it was previously stationed at and not the new System). As a weekly action, an Associate may remove any number of Systems from the Produce of a Vessel they own in order to gain a number of Credits equal to the square of the number of Systems removed (this is known as Importing), except that the System at which the Vessel is currently stationed cannot be removed from its Produce this way.

Each Vessel has a Class, which can be Transport, Frigate, Fighter, Scout, or Unclassified and is by default Unclassified.

Each Class of ship other than Unclassified has a Max Cargo Size, Attack, and Defense as follows

;Transport: Max Cargo Size 10, Attack 0, Defense 3
;Frigate: Max Cargo Size 4, Attack 1, Defense 5
;Fighter: Max Cargo Size 2, Attack 3, Defense 2
;Scout: Max Cargo Size 3, Attack 1, Defense 1

As an act known as Reclassification, an Associate may change the class of any of their Unclassified Vessels. No other dynastic actions may be taken using Unclassified Vessels, other than creating them.

If a Vessel is not Unclassified, the length of their list of Produce may not exceed the Max Cargo Size for its Class.

==Credits==

The low-median of a set of values is always a member of that set of values. When the number of values in a set is odd, the middle value in that set is the low-median. When the number of values in a set is even, the smaller of the two middle values in that set is the low-median.

The Guild, every System, and every Associate each have a publicly tracked number of Credits, defaulting for each Associate to the low-median of every Associate’s Credits, and for each System and the Guild to 0. The Guild also has a publicly tracked Debt. If the ruleset specifically state that a Director of a System spends Credits (as opposed to simply saying an associate spends credits), those Credits come from that System, not from the Associate personally.

As a Timed Action, the President may increase the Debt by 1 to give the Guild Credits equal to the current Share Price plus Quorum minus Debt. The President may also transfer the Guild’s Credits to Systems anytime, with the restriction that no system being given credits in this way can have more than three times the credits of any other system at the time of the credits being granted.

Each Associate has a publicly tracked amount of Crypto, defaulting to the low-median of every Associate’s Crypto. An Associate may transfer any of their Credits to any other Associate’s Crypto. As a Communal Timed Action, anyone may transfer X or 1 (whichever is higher) from each Associate’s Crypto (or if there is not enough Crypto, as much as possible) to that Associate’s Credits, where X is the low-median of each Associate’s Crypto.

When the Guild performs a Bounty Payout, the targeted Associate gains up to 8 Credits. The Guild chooses the exact amount and should publish and follow guidelines for this payout in their Bounty Notice.

===Corruption===

Each Associate has a integer Corruption which is publicly tracked and defaults to 0. When an Associate would spent Credits (and they are the one performing the action to cause them to spend credits) they may instead spend those Credits from a System they are the Director of. Upon doing so, they gain a number of Corruption equal to the number of Credits spent.

Each System has a publicly tracked number named Inefficiency which defaults to 0. Whenever a System would gain an amount of Credits, if that System’s Inefficiency is less than the Corruption of the Associate that is that System’s Director, that System gains that amount of Inefficiency instead.

As a Timed Communal Action, any Associate or the Guild may perform Corruption Decay, which is an atomic action with the following steps:
* Subtract 1 from every Associate’s Corruption, to a minimum of 0 Corruption.
* Set every System’s Inefficiency to 0.

==Factions==

There exists some number of Factions. Each Faction has a name, which is flavour text, and a Zone of Control which is a list of up to three system names, defaulting to blank.

When an action is listed as a Faction Action, an Associate must either have a vessel in one of the systems in the target Faction’s Zone of Control, or must have no vessels.

Whenever there are fewer than quorum factions, the Guild or any Associate may create a Faction, following these steps:
* Set its name to a string consisting of a random colour (via rolling COLOUR in the dice roller) and a random animal from the [[List of animals]] wiki page, pluralised. (e.g. Magenta Caimans).
* Roll DICE3 to get the number of Systems to place in the Faction’s Zone of Control.
* Select the system in the fewest Zones of Control, rolling randomly between the systems in the fewest in the case of a tie. Place it within the Faction’s Zone of control.
* Repeat the preceding step as many times as necessary until the Faction has the rolled number of systems in its Zone of Control.

===Faction Control===

As a Communal Timed Action, any Associate or the Guild may perform Faction Control, which is an atomic action with the following steps:
* For each Faction that is the Director of one or more Systems, publicly roll {-2,-1,-1,0,0,0,0,1,1,2} and add the result to the Tax Rate of every System in which that Faction is the Director, to a minimum Tax Rate of 0.

==Insolvency==

If the Guild ever has more than or equal to twice Quorum Debt, the Guild is said to be Insolvent. If the Guild has been Insolvent for all of the past 96 hours, the Guild may perform Liquidation, and no other Dynastic Actions can be taken. To perform Liquidation, the Guild creates a new rule named “Collateral” with the following text (the following text is flavour text until it becomes a Rule):

<code>The Game is in Interregnum Hiatus. Anyone may perform Dynastic Reset, using the below Ascension Address. When they finish doing so, "for the next Dynasty" changes to "for this Dynasty", the third sentence of the rule Imperial Tracking takes effect, and this sentence and everything before it in this rule is repealed.
The following text is flavour text and is considered to be an Ascension Address for the next Dynasty:
The Theme of this Metadynasty is Paying Back the Debt. Repeal all Dynastic rules except Collateral. Remove the Building Blocks "Bounties" and "Virtual Actions". "Associate" becomes "Debtor". "Guild" becomes "Creditor". Gamestate shall be tracked on the page "Bankrupt". This Dynasty is a Metadynasty.</code>

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

= Building Blocks =
Building Blocks are rules that can be substituted in and out of the ruleset as needed, usually as a result of an Ascension Address. All rules in the Building Blocks section are ruletext.

Potential Building Blocks rules can be found at the [[Building Blocks]] page of the wiki. That page’s contents are not rulestext. When the contents of the Building Blocks page are referred to as ‘rules’ by the ruleset or by a Votable Matter, it should be assumed that said contents are being referred to as potential rules rather than actual rules.

When a Guild specifies the Building Blocks rules in use for a new dynasty in an Ascension Address, they should specify (by name) the rules from the Building Blocks page that they would like to be included in this section of the ruleset. When a Dynastic Reset is performed, the Building Blocks rules selected in the most recent Ascension Address (if any) must be transcribed faithfully to this section of the ruleset, and any Building Blocks rules not so named in that Ascension Address must be removed from the Building Blocks section.

Whenever the text of a Building Block rule is changed in the ruleset, or a new Building Block rule is added to the ruleset, those changes are also made to the [[Building Blocks]] page of the wiki.

==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)

==Virtual Actions==
A Virtual Action is a type of action that the Guild performs on behalf of an Associate. An 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. An 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 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.
==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.
</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.)

===Imperatives===
;Can: “is able to”
;Shall: “is required to”
;Should: “is recommended that”

===Time===
;Daily Action: If a game action is a Daily Action, each Associate 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 Associate per day. A Daily Communal Action may still not be performed if another Associate has performed that action within the last ten hours.
;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.
;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 Associate 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 Associate per week. A Weekly Communal Action may still not be performed if another Associate has performed that action within the last twenty-four hours.

===Other===
;Comment: A blog comment published to the BlogNomic weblog at [http://blognomic.com blognomic.com]
;Core Proposal: A Proposal which mandates changes that, even if conditionally, are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of Admin status from one or more Associates.
;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 only 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.
;Dynastic Variable: A gamestate variable that exists only due to a dynastic rule and is not mentioned in a non-dynastic rule. (In particular, the identity of the Guild is not a dynastic variable.)
;Effective Vote Comment (EVC): An Associate's Effective Vote Comment with respect to a given Votable Matter is that Associate's Comment to that Votable Matter, if any, that contains that Associate's Vote on that Votable Matter.
;Commentary: When posting a blog entry, an Associate 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.
;Discord: The BlogNomic Discord can be accessed at https://discord.gg/J7kP9KuHQK and is also linked to on the sidebar. Associates , as well as people who are not Associates but are interested in learning more about BlogNomic, may join the Discord by clicking the button in the sidebar.
;Discord Channel: A Discord Channel is any channel on the BlogNomic Discord in the BlogNomic Discussion category. All Associates who are in the Discord should have the ability to access all of these channels. To reference a Discord Channel, use a hash (#) followed by the name of that channel (e.g. #random).
;Flavour Text: If a part of the ruleset or gamestate is defined as being “flavour text”, it retains its context, but is not considered to have any meaning beyond being a string of characters. Associates 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. An Associate cannot achieve victory if achieving that victory relies on matching the contents of any flavour text gamestate that Associate has with the criteria for achieving victory.
;Gamestate: Any information which the Ruleset regulates the alteration of. All wiki pages that the rules and Building Blocks explicitly mention (except for the FAQ, the dynastic histories and discussion pages) and any images or Templates contained within (or indirectly invoked by Templates contained within) those Wiki Pages are assumed to be Gamestate.
;Hiatus: If BlogNomic is on Hiatus, Dynastic Actions may not be taken (except where the rule defining the action explicitly requires it to be taken during Hiatus), and Proposals may not be submitted or Resolved unless a core rule permits doing so for that type of Hiatus. 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.
;Indirect Action: An action performed by an Associate or the Guild where the performance of the action is defined using the phrase “on behalf of” another Associate. When such an action is performed, any gamestate changes are applied as if the latter Associate had performed that action directly, with the exception that the person performing the action may make any decisions necessary to perform that action without regard to the benefit of the latter Associate, unless otherwise specified by the rules for that action.
;Post: A blog post published to the BlogNomic weblog at [http://blognomic.com blognomic.com]
;Quorum: Quorum of a subset of Associates is half the number of Associates in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Associates it is referring to, it is referring to a Quorum of all Associates.
;Reject: To reject an attempt to take an action is to retroactively declare the attempt to have been unsuccessful, and to declare that all attempted game actions taken after that attempt were attempted as though the rejected attempt had been unsuccessful. An attempt to take an action can be rejected even if it were originally legal. The opposite of rejecting an attempt to take an action is upholding it.
;Resolve/Resolution: If used in a context of a Votable Matter, the word “Resolve” means to perform the act, as an Admin, of enacting, failing, or marking illegal 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. The resolution of a Votable Matter is tracked by reference to its status in the blog post edit form. If otherwise legally applied, the application of any status through the blog post editing form is sufficient to consider that Votable Matter to have been correctly resolved, but a resolved Votable Matter should have the correct status wherever possible; if any admin believes that a resolved Votable Matter has an incorrect status then they may correct it.
;Revert: To Revert an action or change is both to fully reverse the effects of that change having occurred, and also to consider that change to have not occurred at all. To Revert a document or piece of tracked gamestate to a specific prior state means to return that item to that state, considering the actions that may have changed it since the time of that state to have not occurred. Reverting the gamestate to a specific state does not imply upholding that state.
;Rule: Each individually numbered and titled block of text (using the wikimedia section heading formatting) of the Ruleset is a rule, including rules that are subrules of other rules; with the exception that the top-level headings defined as ‘sections’ in the rule “Ruleset and Gamestate” are considered sections but not rules themselves.
;Sticky Post: A blog post where the “Make Entry Sticky” option has been enabled. Changing the state of this option is not considering altering or modifying the post with regards to the rules on Official Posts. The sticky status of posts should generally be left to the discretion of the Guild.
;Story Post: A Story Post is a post (that is not a Proposal, Call for Judgement, or Declaration of Victory) that follows a format specified by a dynastic rule, and is either in the “Story Post” category, (if it is a Votable Matter) the “Story Post—Votable Matter” category, or in no category. As an exception to the rule against changing the categories of posts in “Official Posts”, if a Story Post is ever in no category, it may be edited into 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.
;Seasonal Downtime: On the 24th, 25th and 26th of December, BlogNomic is [[#hiatus|on Hiatus]]. In addition, game actions defined by the core rules titled “Associates” and “Victory and Ascension” (with the exception of Voting in DoVs) may not be taken.
;Subrule: A subrule is a type of rule that is hierarchically ordered beneath another rule. Rules and proposals that refer to a rule do not also refer to its subrules, unless otherwise specified.
;Table of Contents: The directory of section headings that is generated by the MediaWiki software for most pages in the wiki.
;Title: The title of a post is never considered to include, for the purposes of any rule, any text that was automatically generated by the blog software as a result of the author putting it into the appropriate category.
;Uphold: To uphold an attempt to take an action is to retroactively declare the attempt to have been successful, and to declare that all attempted game actions taken after that attempt were attempted as though the upheld attempt had been successful. An attempt to take an action can be upheld even if it were originally illegal (in which case the retroactive change is made by pretending, for the purpose of calculating the results of that change, that the action was legal). The opposite of upholding an attempt to take an action is rejecting it.
;Vote: The word “Vote”, used as a noun, means a Vote that is cast in accordance with the rule “Votable Matters” and its subrules. The word “Vote”, used as a verb, means the act of casting such a Vote. The definition of the word Vote in either noun or verb form cannot be redefined by a dynastic rule.
;Voting Icons: For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, a DEF http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and a crossed-out circle http://blognomic.com/images/vote/seal.gif shall represent a vote to VETO.
;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 [http://blognomic.com http://blognomic.com]. Any Associate may [http://blognomic.com/update/index.php?C=publish post] to the blog at any time, but may only make official posts to the blog when the [[#Ruleset and Gamestate|Ruleset]] allows it. Posts following the format specified by a rule are considered official posts. Any single official post cannot be of two different types of official post unless a rule explicitly states otherwise. Dynastic rules cannot define posts in the “Call for Judgement” category to be a type of official post other than a Call for Judgement, and this restriction cannot be overridden by dynastic rules.

An official post may only be removed as allowed by the Ruleset. An official post may only be altered by its author 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, except that a Votable Matter’s illegal resolution may be overturned. An official blog post’s status may never be altered except in accordance with the rules that define that official post.

An official post may be altered by its author if it is less than 30 minutes old and either no Associate has commented on it or (if it is a Votable Matter) if all comments on it contain no voting icon; this provision may be overruled by dynastic or Building Blocks rules.

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 voting icons in any of its comments, the author may change the categories as they wish. Secondly, if a post is less than six hours old and appears to the Guild to have been intended as a Proposal, and if its author does not already have two Proposals pending, then the Guild may move it into the Proposal category, causing it to be considered to have been open for voting since the time that the post was first posted.

Any post that is or is made illegal as a result of an infraction against any of the prohibitions set out in this rule, except for a Votable Matter’s illegal resolution that has been overturned, 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, except for the legal enactment of a CfJ. An illegal CfJ cannot cause itself to become legal.

An Official Post is considered to consist only of text or other content clearly visible while looking at the blog’s output of that Official Post’s underlying code, and links clearly marked as links by the blog.

====Date and Time Tracking====

The Entry Date field of an Official Post may be modified by its author, an Admin, or the Guild, only under the following conditions and only in the following ways:
* If an Official Post is older than 7 days but needs to remain Sticky on the front page of the Blog then its Entry Date may be edited to the time of the edit, to within a minute, with the original date and time at which it was posted added to the Commentary or flavour text field of that post, in which case the original time of posting remains the time at which it was posted.
* If an Official Post has been made visible on the blog within the preceding 6 hours, then the Entry Date field may be amended to match the timestamp for the first revision of the post (i.e. the timestamp for the initially posted version).

===Representations of the Gamestate===
If authorised by the rules as a result of an Associate’s action, changes to gamestate which is tracked in a specific place (such as a wiki page) do not take effect until the representation of that gamestate has been updated to match the authorised change. 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. Likewise, when performing a sequence of actions in quick succession that would otherwise require multiple comments to be posted in a row to the same blog post, the Associate performing them may combine those comments into a single comment (as long as it is clear which actions were performed), performing any wiki page updates that would otherwise have been performed between the comments immediately after posting the combined comment. 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 Associate may correct the representations to comply with the Gamestate.

If an Associate feels that a representation of the gamestate (such as a wiki page) does not match the gamestate, they may either:

* Undo the effects of any alteration that led to it, if that alteration did not follow the rules at the time it was made.
* Alter the representation to match what they believe to be the correct application of an incorrectly-applied alteration. This may include completing incomplete actions on behalf of the original Associate, if doing so would not require the correcting Associate to make any decisions on behalf of the original Associate.

Instead of repeatedly reverting and re-reverting a disputed alteration, however, Associates are encouraged to raise a Call for Judgement.

The historical fact of the occurrence of a defined game action is itself considered to be gamestate. Unless the rule defining the action specifies otherwise, this occurrence is 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.

A week (168 hours) after each attempt by an Associate to perform an action, the values to which that attempt changed publicly tracked dynastic variables on their public trackers are automatically upheld, unless the attempt is challenged. (If an attempt does not change the value of a particular variable on the tracker, this does not cause the value of that unchanged variable to be upheld.) An attempt can be challenged in a blog post or comment (e.g. by stating that the attempt may not have succeeded or that the value of the variable is wrong), by making a CFJ that would uphold, reject or revert the attempt, or by making an edit to the tracker that purports to correct the effects of that attempt on publicly tracked dynastic variables (including by reverting its changes on the purported basis that attempted action was illegal).

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

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

===Imperial Tracking===

The identity of the current dynasty’s Guild is tracked in the last sentence of the Core Rule “Dynasties”. Whenever an Associate becomes the Guild, that sentence changes to “The following Associate is the Guild: ” followed by that Associate’s name in quotes. Whenever a Metadynasty starts, that sentence changes to “There is no Guild this Dynasty.”.

All names after the colon in the last sentence of “Dynasties” are considered to be references to Associates, and are flavour text for all purposes other than referencing Associates. If the Guild changes their name by proposal, the sentence in question is updated to reflect the new name of the Guild.

The identity of the Guild is considered to be a gamestate variable that belongs to the game of BlogNomic as a whole, rather than belonging to the Guild personally.

=== 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.
* A list of comma-separated values in curly brackets (eg {x,y}) will return one of the values at random.

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

If a Votable Matter proposes a change to this rule that would require server-level access to the BlogNomic site to fully enact its effects, that Votable Matter must name an Associate with such access. Only an Associate with such access may Enact that Votable Matter. If that Votable Matter does not name an Associate with such access, that Votable Matter 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 roll in the Dice Roller, unless otherwise specified, and which value the roll result corresponds to must be reasonably inferable from the nature of the roll and any comments supplied by the Associate making the roll before or while making the roll. The Dice Roller is considered to fulfill the uniform probability distribution requirements to meet the purposes of the game. Additionally, when using a private random generation method, it is enough that the Associate performing the selection holds a genuine belief that their random selection method is uniform. If a selection is explicitly specified as being “secretly” random, the Associate 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 an Associate 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 except when required as part of the steps of that Atomic Action, or achieve victory, until all the steps are complete or 72 hours have passed.
* If a rule allows the Associate performing an Atomic Action to skip some of its steps, the skipped steps are considered to have been completed.
* If an Associate 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 the step required posting a blog post, it is undone by editing the blog post to explain that its creation was undone (rather than by deleting the post). If the step required posting a comment, it is undone by adding another comment to the same post, explaining that the comment was undone (rather than by deleting the comment). A post or comment that is undone this way as part of correcting an Atomic Action no longer has any effect on the ruleset or gamestate.
* If one or more steps of an Atomic Action were done incorrectly, the Associate must redo the Atomic Action; for that purpose, the Associate 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 Associate 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,” “pay” 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” or “pay” 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, paid, lost, gained, or transferred, an Associate can spend or pay from only their own values, and a rule that allows Associates to transfer or pay a numeric value to another Associate only allows them to transfer that value from themselves to that other Associate (of their choice unless otherwise stated).
* If a Dynastic Action is defined as having a cost X of numeric value V, or defines a requirement to spend, pay, or lose X of numeric value V to accomplish an effect or multiple effects, then the arithmetic effects of spending or payment and the act of carrying out those effects are considered to be subsequent steps in an Atomic Action, with the spending or payment step taking place before the effects step unless stated otherwise.
* An Associate 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), false (for variables or states that may only be either true or false), 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”). For the purposes of this bullet point, the names of Associates are not considered to be legal values for game variables, nor for list items within game variables.
* 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.
* If a piece of information is described as being tracked secretly or privately by the Guild (including secretly random selections), then that information may only be revealed by the Guild when the ruleset allows it. If an Associate should already know such a piece of information (in that the Guild has already told them it, or vice versa, and there is no way that the information could have been changed since then), the Guild may repeat it to them. Additionally; if a piece of private information is described as being Sealed; the Associate or Guild who tracked that information may reveal it during an Interregnum or during any later dynasty.
* A range of numerical values stated to be “between” one value and another value is treated as an inclusive range unless otherwise explicitly stated.
* If a game variable is defined to hold a singular Associate or the singular name of an Associate and that Associate (or the Associate with the matching name) goes idle, that variable is set to its default value. If a game variable is defined to hold a list of Associates, or the list of names of Associates, and that Associate (or the Associate with the matching name) goes idle, it is removed from the list (if this would cause the list to become invalid, the list is instead set to its default value

===Rules and Votable Matters===
* If a new rule is created by a Votable Matter and its location is not noted in that Votable Matter, that new rule is to be placed in the Dynastic Rules.
* If a wiki page (or image or Template) becomes gamestate as a result of a Votable Matter enacting, that content shall – unless otherwise specified – be reverted to whatever state it was in at the time of that Votable Matter’s submission (and if the new gamestate did not exist at that time, it shall be blanked).
* Where a [[#Votable Matters|Votable Matter]] would amend the effects of Votable Matter Enactment, this does not apply to its own enactment unless explicitly stated (e.g. a Votable Matter proposing that enacted Votable Matters 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 a dynastic rule has no text and no subrules, any Associate may delete it from the ruleset.
* A rule may be accompanied by one or more illustrations, and an illustration may have a caption. In all situations, unless otherwise explicitly stated, an illustration may not be treated as containing ruletext, and may not be considered to possess any meaning other than that given to it by ruletext, and a caption to an illustration must be treated as flavour text.
* When the ruleset calls for the use of a specific tool (such as the dice roller, or an off-domain website, or a specific piece of downloadable software), Associates may not deliberately interfere with the function of that tool except in ways explicitly permitted by the ruleset.
* If the Guild has voted DEFERENTIAL on a Proposal, they (and any other Associates who have voted DEFERENTIAL on it) are not considered to be an Associate for the purposes of totaling quorum on that Proposal.

===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.
* An Associate 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 and formatting===
* 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.
* Associates may correct obvious spelling, punctuation, typographical, and/or formatting mistakes in the Ruleset, the Building Blocks page, and their own Pending Votable Matters at any time, including replacing Spivak and gender-specific pronouns that refer to Associates with the corresponding forms of the singular ‘they’.
* An Associate may reformat a list of items in the dynastic ruleset to have bullet points or other appropriate list markup, if doing so would not change the order of that list, nor how any rules interpreted its content.
* An Associate may change the layout or design of a gamestate wiki page if doing so would not change how any rules interpreted its content.

===Names===
* Within the Ruleset, a word only refers to the name of an Associate if it is explicitly stated that it refers to an Associate's name.
* If a rule would ever have no name, it is instead given the name of the Votable Matter that created it, or (if this is not possible) the name “Unnamed Rule”.
* The names of rules and wiki pages (other than the Ruleset) are flavour text.
* 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 Votable Matter, the name used in reference to a specific Votable Matter may be simplified by not including braces and any text between the opening and closing braces. i.e. a Votable Matter 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 braces and any text between a pair of opening and closing braces, as long as such a reference would be unambiguous.
* Where a Votable Matter refers to a second Votable Matter by name, it is assumed to refer to the most recently posted Votable Matter of that name which pre-dates the first Votable Matter.
* When changing their name or joining the game for the first time, an Associate's (or prospective Associate's ) new name must be between 3 and 30 characters in length, and may only include the 26 letters of the Latin alphabet, numbers, underscores, hyphens, full stops and apostrophes. An Associate’s name may only be changed as a result of a Proposal approving the change.

==Prioritisation==
* The Ruleset may impose no limitation on the ability of a CfJ to alter the Gamestate or Ruleset. If an enacted CfJ calls for a change that the Ruleset prohibits or considers impossible then the CfJ has priority (with the exception of the prohibition on votable matters making changes that apply to its own enactment). An enacted Proposal has priority over the Dynastic rules or Building Blocks, but may not make changes that are prohibited or contradicted by the Appendix or Core Rules.
* 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;
# If a Core Rule explicitly says it cannot be overruled by a Dynastic Rule, that Core Rule has precedence over a Dynastic Rule, otherwise a Dynastic Rule has precedence over that Core Rule;
# If a Building Blocks Rule explicitly says that it cannot be overruled by a Dynastic Rule, that Building Blocks Rule has precedence over a Dynastic Rule, otherwise a Dynastic Rule has equal precedence as that Building Blocks Rule;
# If two contradicting parts have equal precedence, the part with more limited scope applies (e.g. if the rules “Associates may Kick each other” and “Associates may not Kick each other on Tuesdays” exist, and it is Tuesday, Associates may not Kick each other);
# If two contradicting parts have the same scope, or have scopes that only overlap where they contradict each other, the negative rule applies (e.g. with “Associates may Punch a Spaceman on Friday” and “Associates may not Punch Spacemen on Friday”, then Associates may not Punch Spacemen on Friday).
* This document is considered to be, in effect, the only Ruleset for BlogNomic, so long as it is located at at the URL https://wiki.blognomic.com/index.php?title=Ruleset.

==Mentors==

An Associate may have another Associate as a Mentor. Associates who are willing to act as a Mentor, and who meet the criteria set out in the Tenured Players section of the aftermentioned page, are listed on the [[Mentorships]] wiki page, and are said to be “Tenured”. An Admin may add or remove their own name, or the name of an Associate who has requested a change on their own behalf, or may remove the name of any Tenured Player who no longer meets the criteria set out in the Tenured Players section of the Mentorships page, from this list at any time. The Mentorships page is also used to list the names of players who are prohibited from becoming Tenured; this list may only be amended by the effect of a Votable Matter.

If an unmentored Associate requests a Mentor, or a new Associate has joined the game and has no Mentor, the Guild should select a Tenured Associate and ask them to take that Associate on as a Mentee; if they accept, then such a Mentorship is established. The members and starting dates of all active Mentorships are tracked on the Mentorships wiki page, and whenever a new Mentorship is established, the Guild should announce it in a blog post. The Guild should take care to consider game balance when selecting a potential mentor.

A relationship between a mentor and a mentee is a Mentorship. An Associate may dissolve a Mentorship they are part of at any time, by announcing this in a blog post.

If there is no Guild, any Associate who has been active in at least three previous dynasties may act as Guild for the purposes of this rule.

===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 and Dice Roller, and optionally the game’s Discord and social media feeds
*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 Associate 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 lasts for four weeks or until the next Ascension Address, whichever occurs latest. It can continue informally 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 Associates .
*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.

== Synonyms ==

A dynasty may provide extra theming by using alternative terms for words like “Associate” and “Guild”.

Each term in this list is synonymous with the term in parentheses

* Associate (Player)
* Guild (Emperor)

When a new Dynasty is started, the Ascension Address may specify new terms for each entry in the above list, provided the newly chosen term does not appear anywhere in the Building Blocks page or the ruleset outside of this rule (though if it only appears in rules which are being removed as part of the Ascension Address, it is fine), and that doing so would not cause two terms in the above list to become synonymous with each other. Doing so causes the old corresponding value (including regional spelling variations) to be replaced by the new value everywhere in the ruleset except in any of the parentheses in the above list.

</div>

Guild Business

2026-06-12T19:58:47Z

Whirlingstars: Taking JonathanDark's advice. I think 5 is reasonable

{{pill|President|SingularByte|gold}} {{pill|Share Price|9|lightblue}} {{pill|Guild Credits|4|lightgreen}} {{pill|Guild Debt|3|orangered}}

{| class="wikitable"
|-
! Guild Insolvency
| style="width: 100px;" | {{progress bar|3|12|color=orange}}
|}

{| class="wikitable sortable"
|+ Associates
|-
! Associate !! Shares !! Credits !! Crypto !! Corruption !! Ballot !! Votes for President
|-
| ais523 || 2 || 13 || 0 || 3 || Chiiika || {{Progress bar|0|13}}
|-
| ayesdeeef || 3 || 2 || 0 || 0 || Chiiika || {{Progress bar|0|13}}
|-
| Chiiika || 3 || 0 || 0 || 0 || Chiiika || {{Progress bar|8|13}}
|-
| Clucky || 1 || 5 || 0 || 0 || SingularByte || {{Progress bar|0|13}}
|-
| Goob || 3 || 2 || 0 || 0 || Chiiika || {{Progress bar|0|13}}
|-
| JonathanDark || 5 || 0 || 0 || 21 || SingularByte || {{Progress bar|0|13}}
|- style="background-color: #f8f8a0; font-weight: bold;"
| SingularByte || 5 || 8 || 0 || 0 || SingularByte || {{Progress bar|14|13}}
|-
| whirlingstars || 2 || 24 || 0 || 0 || SingularByte || {{Progress bar|0|13}}
|}

{| class="wikitable sortable"
|+ Systems
|-
! System !! Director !! Credits !! Tax Rate !! Inefficiency !! Vessels !! Influence
|-
| {{ZavijavaShort}}avijava || ais523 || 0 || 0 || 0 ||

{{Vessel|ais523|Z}}
{{Vessel|Clucky (Scout)|H}}
{{Vessel|ais523 (Transport)|MRHTZ}}
{{Vessel|SingularByte (Frigate)|ATMZ}}
{{Vessel|Darknight|-}}
{{Vessel|Josh|-}}

||
|-
| {{RigelShort}}igel || Clucky || 14 || 3 || 0 ||

{{Vessel|Josh|-}}

||
Clucky
|-
| {{ThubanShort}}huban || Chiiika || 11 || 10 || 0 ||

{{Vessel|JonathanDark|T}}
{{Vessel|SingularByte (Frigate)|T}}
{{Vessel|redtara|-}}

|-
| {{MiraShort}}ira || Yellow Iguanas || 16 || 1 || 0 ||

{{Vessel|Chiiika|M}}
{{Vessel|whirlingstars|M}}
{{Vessel|Clucky|HA}}
{{Vessel|whirlingstars (Transport)|AHM}}

||
|-
| {{AtlasShort}}tlas || whirlingstars || 13 || 5 || 0 ||

{{Vessel|Chiiika (Transport)|ZRMAT}}
{{Vessel|JonathanDark (Transport)|AHMRZ}}
{{Vessel|redtara|-}}

||
|-
| {{HamalShort}}amal || JonathanDark || 2 || 30 || 0 ||

{{Vessel|Darknight|-}}

||
Clucky
|}
''Key:{{pill|Vessel Owner (Type)|Produce}}Produce is referenced by the first letter of the System, for example:{{letter|A|aquamarine}}{{letter|T|turquoise}}''

{| class="wikitable"
|+ Factions
|-
! Name !! Zone of Control
|-
| Purple Wombats || Thuban
|-
| Yellow Iguanas || Mira, Hamal
|-
| Turquoise Macaws || Zavijava, Rigel, Atlas
|-
| Black Meerkats || Hamal, Rigel, Thuban
|-
| Magenta Quolls || Atlas, Mira
|-
| Silver Oysters || Zavijava
|}

Guild Business

2026-06-11T20:52:48Z

Whirlingstars: classify, move, produce

{{pill|President|SingularByte|gold}} {{pill|Share Price|7|lightblue}} {{pill|Guild Credits|4|lightgreen}} {{pill|Guild Debt|6|orangered}}

{| class="wikitable"
|-
! Guild Insolvency
| style="width: 100px;" | {{progress bar|6|10|color=orange}}
|}

{| class="wikitable sortable"
|+ Associates
|-
! Associate !! Shares !! Credits !! Crypto !! Corruption !! Ballot !! Votes for President
|-
| ais523 || 2 || 14 || 0 || 4 || Chiiika || {{Progress bar|0|12}}
|-
| Chiiika || 3 || 2 || 0 || 0 || Chiiika || {{Progress bar|5|12}}
|-
| Clucky || 1 || 2 || 0 || 0 || SingularByte || {{Progress bar|0|12}}
|-
| Darknight || 2 || 28 || 0 || 0 || SingularByte || {{Progress bar|0|12}}
|-
| JonathanDark || 6 || 0 || 0 || 20 || SingularByte || {{Progress bar|0|12}}
|- style="background-color: #f8f8a0; font-weight: bold;"
| SingularByte || 5 || 8 || 0 || 0 || SingularByte || {{Progress bar|17|12}}
|-
| whirlingstars || 2 || 24 || 0 || 0 || SingularByte || {{Progress bar|0|12}}
|}

{| class="wikitable sortable"
|+ Systems
|-
! System !! Director !! Credits !! Tax Rate !! Inefficiency !! Vessels !! Influence
|-
| {{ZavijavaShort}}avijava || ais523 || 0 || 0 || 0 ||

{{Vessel|ais523|Z}}
{{Vessel|Darknight|}}
{{Vessel|SingularByte|ATMZ}}
{{Vessel|Clucky (Scout)|H}}

||
|-
| {{RigelShort}}igel || Clucky || 14 || 3 || 0 ||


||
Clucky
|-
| {{ThubanShort}}huban || Chiiika || 9 || 1 || 0 ||

{{Vessel|JonathanDark|T}}
{{Vessel|SingularByte|T}}
{{Vessel|ais523 (Transport)|MRHT}}
{{Vessel|Chiiika (Transport)|ZRMT}}
||

|-
| {{MiraShort}}ira || Yellow Iguanas || 15 || 1 || 0 ||

{{Vessel|Chiiika|M}}
{{Vessel|whirlingstars|M}}
{{Vessel|Clucky|HA}}
{{Vessel|JonathanDark (Transport)|HMRZ}}
{{Vessel|whirlingstars (Transport)|AHM}}

||
|-
| {{AtlasShort}}tlas || whirlingstars || 11 || 1 || 0 ||


||
|-
| {{HamalShort}}amal || JonathanDark || 2 || 1 || 5 ||

{{Vessel|Darknight|}}

||
Clucky
|}
''Key:{{pill|Vessel Owner (Type)|Produce}}Produce is referenced by the first letter of the System, for example:{{letter|A|aquamarine}}{{letter|T|turquoise}}''

{| class="wikitable"
|+ Factions
|-
! Name !! Zone of Control
|-
| Purple Wombats || Thuban
|-
| Yellow Iguanas || Mira, Hamal
|-
| Turquoise Macaws || Zavijava, Rigel, Atlas
|-
| Black Meerkats || Hamal, Rigel, Thuban
|-
| Magenta Quolls || Atlas, Mira
|-
| Silver Oysters || Zavijava
|}

Guild Business

2026-06-08T19:28:17Z

Whirlingstars: Going places and immediately Exporting

{{pill|President|SingularByte|gold}} {{pill|Share Price|8|lightblue}} {{pill|Guild Credits|4|lightgreen}} {{pill|Guild Debt|7|orangered}}
{| class="wikitable sortable"
|+ Associates
|-
! Associate !! Shares !! Credits !! Crypto !! Corruption !! Ballot !! Votes for President
|-
| ais523 || 1 || 16 || 0 || 0 || Chiiika || {{Progress bar|0|8}}
|-
| Chiiika || 3 || 2 || 0 || 0 || Chiiika || {{Progress bar|4|8}}
|-
| Clucky || 1 || 16 || 0 || 0 || SingularByte || {{Progress bar|0|8}}
|-
| Darknight || 2 || 28 || 0 || 0 || SingularByte || {{Progress bar|0|8}}
|-
| JonathanDark || 1 || 20 || 0 || 0 || - || {{Progress bar|0|8}}
|- style="background-color: #f8f8a0; font-weight: bold;"
| SingularByte || 5 || 9 || 0 || 0 || SingularByte || {{Progress bar|10|8}}
|-
| whirlingstars || 2 || 26 || 0 || 0 || SingularByte || {{Progress bar|0|8}}
|}

{| class="wikitable sortable"
|+ Systems
|-
! System !! Director !! Credits !! Tax Rate !! Corruption !! Vessels
|-
| {{ZavijavaShort}}avijava || ais523 || 7 || 0 || 0 ||

{{Vessel|ais523|Z}}
{{Vessel|Darknight|}}
{{Vessel|JonathanDark|HR}}

|-
| {{RigelShort}}igel || Clucky || 11 || 1 || 0 ||


|-
| {{ThubanShort}}huban || Chiiika || 9 || 1 || 0 ||

{{Vessel|JonathanDark|T}}
{{Vessel|SingularByte|T}}

|-
| {{MiraShort}}ira || - || 11 || 1 || 0 ||

{{Vessel|Chiiika|M}}
{{Vessel|Chiiika|RM}}
{{Vessel|whirlingstars|M}}
{{Vessel|SingularByte|ATM}}
{{Vessel|Clucky|HA}}

|-
| {{AtlasShort}}tlas || whirlingstars || 11 || 1 || 0 ||


|-
| {{HamalShort}}amal || JonathanDark || 22 || 1 || 0 ||

{{Vessel|Clucky|H}}
{{Vessel|Darknight|}}
{{Vessel|ais523|MRH}}
{{Vessel|whirlingstars|AH}}

|}
''Key:{{pill|Vessel Owner|Produce}}Produce is referenced by the first letter of the System, for example:{{letter|A|aquamarine}}{{letter|T|turquoise}}''

{| class="wikitable"
|+ Factions
|-
! Name !! Zone of Control
|-
| Purple Wombats || Thuban
|-
| Yellow Iguanas || Mira, Hamal
|-
| Turquoise Macaws || Zavijava, Rigel, Atlas
|-
| Black Meerkats || Hamal, Rigel, Thuban
|-
| Magenta Quolls || Atlas, Mira
|-
| Silver Oysters || Zavijava
|}

Guild Business

2026-06-08T19:26:43Z

Whirlingstars: Exporting

{{pill|President|SingularByte|gold}} {{pill|Share Price|8|lightblue}} {{pill|Guild Credits|4|lightgreen}} {{pill|Guild Debt|7|orangered}}
{| class="wikitable sortable"
|+ Associates
|-
! Associate !! Shares !! Credits !! Crypto !! Corruption !! Ballot !! Votes for President
|-
| ais523 || 1 || 16 || 0 || 0 || Chiiika || {{Progress bar|0|8}}
|-
| Chiiika || 3 || 2 || 0 || 0 || Chiiika || {{Progress bar|4|8}}
|-
| Clucky || 1 || 16 || 0 || 0 || SingularByte || {{Progress bar|0|8}}
|-
| Darknight || 2 || 28 || 0 || 0 || SingularByte || {{Progress bar|0|8}}
|-
| JonathanDark || 1 || 20 || 0 || 0 || - || {{Progress bar|0|8}}
|- style="background-color: #f8f8a0; font-weight: bold;"
| SingularByte || 5 || 9 || 0 || 0 || SingularByte || {{Progress bar|10|8}}
|-
| whirlingstars || 2 || 28 || 0 || 0 || SingularByte || {{Progress bar|0|8}}
|}

{| class="wikitable sortable"
|+ Systems
|-
! System !! Director !! Credits !! Tax Rate !! Corruption !! Vessels
|-
| {{ZavijavaShort}}avijava || ais523 || 7 || 0 || 0 ||

{{Vessel|ais523|Z}}
{{Vessel|Darknight|}}
{{Vessel|JonathanDark|HR}}

|-
| {{RigelShort}}igel || Clucky || 11 || 1 || 0 ||


|-
| {{ThubanShort}}huban || Chiiika || 9 || 1 || 0 ||

{{Vessel|JonathanDark|T}}
{{Vessel|SingularByte|T}}

|-
| {{MiraShort}}ira || - || 11 || 1 || 0 ||

{{Vessel|Chiiika|M}}
{{Vessel|Chiiika|RM}}
{{Vessel|whirlingstars|M}}
{{Vessel|SingularByte|ATM}}
{{Vessel|Clucky|HA}}

|-
| {{AtlasShort}}tlas || whirlingstars || 10 || 1 || 0 ||

{{Vessel|whirlingstars|A}}

|-
| {{HamalShort}}amal || JonathanDark || 21 || 1 || 0 ||

{{Vessel|Clucky|H}}
{{Vessel|Darknight|}}
{{Vessel|ais523|MRH}}

|}
''Key:{{pill|Vessel Owner|Produce}}Produce is referenced by the first letter of the System, for example:{{letter|A|aquamarine}}{{letter|T|turquoise}}''

{| class="wikitable"
|+ Factions
|-
! Name !! Zone of Control
|-
| Purple Wombats || Thuban
|-
| Yellow Iguanas || Mira, Hamal
|-
| Turquoise Macaws || Zavijava, Rigel, Atlas
|-
| Black Meerkats || Hamal, Rigel, Thuban
|-
| Magenta Quolls || Atlas, Mira
|-
| Silver Oysters || Zavijava
|}

Guild Business

2026-06-04T19:09:22Z

Whirlingstars: A bit too hasty

{{pill|President|-|gold}} {{pill|Share Price|9|lightblue}} {{pill|Guild Credits|0|lightgreen}} {{pill|Guild Debt|5|orangered}}
{| class="wikitable sortable"
|+ Associates
|-
! Associate !! Shares !! Credits !! Crypto !! Ballot !! Votes for President
|-
| ais523 || 1 || 20 || 0 || - || 0/9
|-
| Chiiika || 1 || 20 || 0 || - || 0/9
|-
| Clucky || 1 || 20 || 0 || - || 0/9
|-
| Darknight || 2 || 28 || 0 || - || 0/9
|-
| JonathanDark || 1 || 20 || 0 || - || 0/9
|-
| Josh || 3 || 10 || 0 || SingularByte || 0/9
|-
| redtara || 1 || 20 || 0 || - || 0/9
|-
| SingularByte || 5 || 13 || 0 || SingularByte || 10/9
|-
| whirlingstars || 2 || 28 || 0 || SingularByte || 0/9
|}

{| class="wikitable sortable"
|+ Systems
|-
! System !! Director !! Credits !! Vessels
|-
| Acrux || ais523 || 0 || ais523, Darknight, Josh
|-
| Rigel || Clucky || 0 || Chiiika, JonathanDark, Josh
|-
| Thuban || Chiiika || 0 || JonathanDark, redtara, SingularByte
|-
| Mira || redtara || 0 || ais523, Chiiika, whirlingstars
|-
| Atlas || Josh || 0 || redtara, SingularByte, whirlingstars
|-
| Hamal || JonathanDark || 0 || Clucky, Clucky, Darknight
|}

{| class="wikitable"
|+ Factions
|-
! Name !! Zone of Control
|-
| Purple Wombats || Thuban
|-
| Yellow Iguanas || Mira, Hamal
|-
| Turquoise Macaws || Acrux, Rigel, Atlas
|-
| Black Meerkats || Hamal, Rigel, Thuban
|-
| Magenta Quolls || Atlas, Mira
|-
| Silver Oysters || Acrux
|}

Guild Business

2026-06-04T16:30:05Z

Whirlingstars: President SingularByte

{{pill|President|SingularByte|gold}} {{pill|Share Price|9|lightblue}} {{pill|Guild Credits|0|lightgreen}} {{pill|Guild Debt|5|orangered}}
{| class="wikitable sortable"
|+ Associates
|-
! Associate !! Shares !! Credits !! Crypto !! Ballot !! Votes for President
|-
| ais523 || 1 || 20 || 0 || - || 0/9
|-
| Chiiika || 1 || 20 || 0 || - || 0/9
|-
| Clucky || 1 || 20 || 0 || - || 0/9
|-
| Darknight || 2 || 28 || 0 || - || 0/9
|-
| JonathanDark || 1 || 20 || 0 || - || 0/9
|-
| Josh || 3 || 10 || 0 || SingularByte || 0/9
|-
| redtara || 1 || 20 || 0 || - || 0/9
|- style="background-color: #f8f8a0; font-weight: bold;"
| SingularByte || 5 || 13 || 0 || SingularByte || 10/9
|-
| whirlingstars || 2 || 28 || 0 || SingularByte || 0/9
|}

{| class="wikitable sortable"
|+ Systems
|-
! System !! Director !! Credits !! Vessels
|-
| Acrux || ais523 || 0 || ais523, Darknight, Josh
|-
| Rigel || Clucky || 0 || Chiiika, JonathanDark, Josh
|-
| Thuban || Chiiika || 0 || JonathanDark, redtara, SingularByte
|-
| Mira || redtara || 0 || ais523, Chiiika, whirlingstars
|-
| Atlas || Josh || 0 || redtara, SingularByte, whirlingstars
|-
| Hamal || JonathanDark || 0 || Clucky, Clucky, Darknight
|}

Guild Business

2026-06-04T16:16:20Z

Whirlingstars: This is democracy manifest

Defusal School

2026-05-03T23:24:13Z

Whirlingstars:

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}
{{pill|Lead Defuser| - |gold}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 17 || - || - || Ready
|-
| Desertfrog || 7 || Josh (1st) || {{box|Tracer|red}} || Ready
|-
| JonathanDark || 13 || Lawnomos (1st) || {{box|Ash|gray}} || Ready
|-
| Josh || 19 || whirlingstars || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - || {{box|Pulse Meter|yellow}} {{box|Solder|brown}} {{box|Tracer|red}} {{box|Ejector Seat|green}} || Ready
|-
| whirlingstars || 4 || Josh (2nd) || {{box|Ash|gray}} || Ready
|}

Defusal School

2026-05-02T19:43:29Z

Whirlingstars: revert

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}
{{pill|Lead Defuser| - |gold}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 13 || - || - || Ready
|-
| Desertfrog || 5 || - || {{box|Probe|blue}} || Ready
|-
| JonathanDark || 13 || Lawnomos (1st) || {{box|Ash|gray}} || Ready
|-
| Josh || 11 || Darknight || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}{{box|Ejector Seat|green}}|| Ready
|-
| whirlingstars || 2 || - || {{box|Ash|gray}} || Ready
|}

Defusal School

2026-05-02T19:42:22Z

Whirlingstars: claiming

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}
{{pill|Lead Defuser| - |gold}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 13 || - || - || Ready
|-
| Desertfrog || 5 || - || {{box|Probe|blue}} || Ready
|-
| JonathanDark || 13 || Lawnomos (1st) || {{box|Ash|gray}} || Ready
|-
| Josh || 11 || Darknight (1st) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}{{box|Ejector Seat|green}}|| Ready
|-
| whirlingstars || 2 || Darknight (2nd) || {{box|Ash|gray}} || Ready
|}

Defusal School

2026-04-29T02:38:31Z

Whirlingstars: oops

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}
{{pill|Lead Defuser| - |gold}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || ais523 || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 7 || whirlingstars || - || Ready
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || - || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}{{box|Ejector Seat|green}}|| Sneaking
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 32 || Darknight || {{box|Ash|gray}} || Sneaking
|}

Defusal School

2026-04-29T02:37:59Z

Whirlingstars: Reclaim Darknight's Design. It was not safely Defused, so it got reset, and so I can go again

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}
{{pill|Lead Defuser| - |gold}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || ais523 || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 7 || whirlingstars || - || Ready
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || - || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}{{box|Ejector Seat|green}}|| Sneaking
|-
| ServusCallidus || 7 || Darknight || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 32 || - || {{box|Ash|gray}} || Sneaking
|}

Defusal School

2026-04-29T02:35:02Z

Whirlingstars: remove myself from the design

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}
{{pill|Lead Defuser| - |gold}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || ais523 || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 7 || whirlingstars || - || Ready
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || - || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}{{box|Ejector Seat|green}}|| Sneaking
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 32 || - || {{box|Ash|gray}} || Sneaking
|}

Defusal School

2026-04-28T20:52:35Z

Whirlingstars: Should've read the fine print

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}
{{pill|Lead Defuser| - |gold}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || ais523 || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 7 || ServusCallidus || - || Ready
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || - || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}{{box|Ejector Seat|green}}|| Sneaking
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 30 || Darknight || {{box|Pulse Meter|yellow}} || Sneaking
|}

Defusal School

2026-04-28T19:43:50Z

Whirlingstars: I am not paying you $8

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || 0 || ais532 || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Ready
|-
| Darknight || 7 || ServusCallidus || - || Ready
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || - || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}{{box|Ejector Seat|green}}|| Sneaking
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 0 || Darknight || {{box|Pulse Meter|yellow}} || Sneaking
|}

Defusal School

2026-04-28T02:38:31Z

Whirlingstars: I did not succeed. Nor did Chiiika for that matter

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || -3 || - || {{box|Blindfold|black}} || Designing
|-
| Darknight || 7 || - || - || Designing
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || ServusCallidus || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}|| Designing
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 0 || - || {{box|Pulse Meter|yellow}} || Sneaking
|}

Defusal School

2026-04-27T23:00:15Z

Whirlingstars: surely *I* can succeed

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || -3 || ServusCallidus (1st) || {{box|Blindfold|black}} || Designing
|-
| Darknight || 7 || - || - || Designing
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || ServusCallidus (2nd) || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || Lawnomos (2nd) || {{box|Pulse Meter|yellow}} || Ready
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}|| Designing
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 0 || ais523 || {{box|Pulse Meter|yellow}} || Sneaking
|}

Defusal School

2026-04-27T20:21:17Z

Whirlingstars: beep. beep. beep

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || -3 || ServusCallidus || {{box|Blindfold|black}} || Designing
|-
| Darknight || 7 || ais523 || - || Designing
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || - || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || - || {{box|Pulse Meter|yellow}} || Designing
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}|| Sneaking
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 0 || - || {{box|Pulse Meter|yellow}} || Sneaking
|}

Defusal School

2026-04-27T20:11:27Z

Whirlingstars: Being a little sneaky 'round here

{{pill|Round|2|lightblue}}
{{pill|Max Cost|15|yellow}}
{{pill|Max Wires|5|green}}
{{pill|Lesson|Power|silver}}

{| class="wikitable sortable"
|-

! Defuser !! Expertise !! Claim !! Equipment !! Status
|-
| Chiiika || -3 || ServusCallidus || {{box|Blindfold|black}} || Designing
|-
| Darknight || 7 || ais523 || - || Designing
|-
| Desertfrog || 5 || Lawnomos (1st) || {{box|Pulse Meter|yellow}} || Designing
|-
| JonathanDark || 2 || - || {{box|Pulse Meter|yellow}}{{box|Tracer|red}} || Sneaking
|-
| Josh || 3 || - || {{box|Pulse Meter|yellow}} || Designing
|-
| Lawnomos || 3 || - ||{{box|Pulse Meter|yellow}}{{box|Solder|brown}}{{box|Tracer|red}}|| Sneaking
|-
| ServusCallidus || 7 || - || {{box|Blindfold|black}} || Sneaking
|-
| whirlingstars || 0 || - || - || Sneaking
|}