Sunday, March 31, 2024

Story Post: Upgrade Request for Snap 019

Timed out, 4-0. Processed by JonathanDark.

Adminned at 02 Apr 2024 15:32:52 UTC

I believe that Snap 019 meets the Upgrade Benchmark “A Snap which meets every Public Criteria”

Story Post: Snap 019: Waving From The Other Side of the Mountain

Story Post: Upgrade Request for Snap 018

Timed out, 4-0. Processed by JonathanDark.

Adminned at 01 Apr 2024 23:56:51 UTC

A Snap which includes a found instance of the BlogNomic username of another Seeker, where the found instance cannot be from a screen capture taken from, or a photo of, a computer monitor, laptop screen, phone, tablet, television, or smart watch

Story Post: Snap 018: Good Vintage?

Friday, March 29, 2024

Proposal: Into the light!

Timed out 4 votes to 0. Enacted by Kevan.

Adminned at 31 Mar 2024 17:26:02 UTC

In Criteria, replace “At any time a Seeker may change any of their Private Criteria while also resetting its satisfying and unsatisfying counts to zero.” with:

At any time a Seeker may change any of their Private Criteria, by first posting the hash and the secret text in a blog entry and then changing the hash and resetting its satisfying and unsatisfying counts to zero in the game state tracking page

 

“For nothing is hid, that shall not be made manifest; nor anything secret that shall not be known and come to the light”

It would allow some validation of secret criteria before the DoV and might kick up some conversation around what should go in Secret Criteria.

Thursday, March 28, 2024

Proposal: Square Eyes

Popular, 5-0. Enacted by JonathanDark.

Adminned at 30 Mar 2024 07:03:27 UTC

In “Shots”, replace “A Shot is confirmed as Authentic if it includes an appearance” with:-

A Shot is confirmed as Authentic if it was taken outside and includes an appearance

Remove “The Shot was taken in an outside location.” from the list of Public Criteria.

Let’s move on from photos of laptops.

Proposal: And the Best Picture Award goes to…...

Withdrawn. Failed by JonathanDark

Adminned at 30 Mar 2024 07:02:35 UTC

New Award:  Best Picture Award


Update Criteria to include:

An Authentic Shot’s Quality Score is equal to the total Satisfying Count of all satisfied criteria by all Seekers that respond and score a Snap.

Update Scoring to include:

When a Seeker posts an Authentic Shot, the Seeker may reduce the Quality Score of the publicly tracked Best Picture Award by 0.5 points.

After 48 hours of a Shot having been posted, any Seeker may at most once respond to it stating the Shot’s Quality Score by totaling all satisfied criteria from all Seekers that responded to score a Snap.


In the rule Awards replace the second paragraph with:

At any time, if a Seeker has met the Standard for a General Award then they may claim it by making a blog post announcing as such and then incrementing their Awards by 1. A Seeker may only claim each General Award once in the dynasty.

At any time, if a Seeker has met the Standard for a Singular Award then they may claim it by making a blog post announcing as such and then incrementing their Awards by 1, and decrementing the current Awards of the Seeker holding that award by 1. Only a single Seeker can hold a Singular Award in the dynasty.

Each Singular Awards ownership will be publicly tracked with its associated owner and any Award criteria.

Add a default Best Picture Award to the Photo Gallery with a default score of 0 and the date and time of this rules adoption.

Update the rule Awards, to rename Award table to General Award table and to include:

{| class="wikitable sortable"
|-
! Singular Award !! Standard
|-
| Best Picture || Post a Snap, after the last recorded date of the current Best Picture Award, that has a Quality Score greater than the Quality Score of the current Best Picture Award. Update the public tracked Best Picture Award to include the Seekers username, Snap Name, Snap Date and Time, and Quality Score.
}


This creates an award type that isn’t shared that only one person can hold. The decay in the Quality Score for Best Picture is to ensure that it isn’t just a simple high score but creates an award that can change hands.  There’s always something new coming…..

Proposal: Philosophical Opposites

Timed out, 3-0 with 1 DEF. Enacted by JonathanDark.

Adminned at 30 Mar 2024 07:00:51 UTC

In the rule “Awards”, add the following entry to the table:

|-
| Conceptual Balance || Have at least one Private Criteria with a Satisfying score of 4 and an Unsatisfying score of 4, where those scores were obtained from the 8 most recent contiguous Authentic Shots

The last part of the clause is to prevent someone from simply gaining the required Satisfying and Unsatisfying scores on specific Shots while ignoring others.

Wednesday, March 27, 2024

Outstanding Composition Award

I have met the standard for the Outstanding Composition Award, so am claiming it

Proposal: Don’t Just Google It

Reached quorum 4 votes to 0. Enacted by Kevan.

Adminned at 28 Mar 2024 16:11:17 UTC

In the rule “Upgrades”, after the text “A Snap which includes a found instance of the BlogNomic username of another Seeker”, add the following text:

, where the found instance cannot be from a screen capture taken from, or a photo of, a computer monitor, laptop screen, phone, tablet, television, or smart watch

Removing the ability to claim the upgrade simply from finding a username on blognomic.com, kevan.org, Google search, making a comment on a social media site, or finding someone’s profile in some other app

Story Post: Upgrade Request for Snap 17

Cannot be enacted with 4 against. Josh

Adminned at 28 Mar 2024 17:43:52 UTC

Snap 17 is taken in the same place (32 seconds in) in the song “So You Can Sleep Enter” by “Ned Navillus” as Snap 16 which was made by another seeker.

Therefore I think I have satisfied the clause “A Snap that was taken in the same place as another Snap taken by a different Seeker.” and so fulfill that Upgrade Benchmark

Story Post: Snap 17: Déjà vu

Story Post: GUESS: Clucky

I guess that one of Clucky’s Private Criteria is “Satisfies all of my other Private Criteria”.

Story Post: Upgrade Request: Snap 016

Cannot be enacted with 3 votes AGAINST. Josh

Adminned at 28 Mar 2024 18:20:14 UTC

Snap 016 contains a found instance of the BlogNomic name of another Seeker (Nadnavillus).

Your tidal cheque will be 0.01c heavier this month and that’s all down to me. Don’t allow it to affect your voting though, that would violate the rule No Cooperation

Story Post: Snap 016: Man, what is this, the invasion of privacy dynasty of something

Proposal: The Public Realm

Withdrawn. Failed by Kevan.

Adminned at 27 Mar 2024 19:54:03 UTC

Remove all but the first Public Criteria from the list in “Criteria”.

To the top of the list in “Scoring”, add a new bullet point:-

* If it is the responder’s own Snap, then for each Public Criteria that the Shot satisfies, the responder’s Score is increased by 3

In Upgrades, replace “A Snap which meets every Public Criteria” with:-

A Snap which includes a specific named entity that had its own Wikipedia page at Mon 18/03/24—09:00 UTC, in which at least one article of clothing worn by the posting Seeker at the time that the Snap was taken is visible, and which contains a message to the viewer

The concepts of Public and Private Criteria seem a bit disconnected. This makes Public into something that, like Private Criteria, you score - specifically, something you can score for each photo and are rewarded for following when composing it, rather than something you can entirely ignore once you’ve unlocked the everything-in-shot achievement.

This also cuts (for now) the list back down to just “photo taken outside”, as I’m not sure whether the group would want to see the entity/clothing/message aspects in every single photo that gets posted.

Tuesday, March 26, 2024

Proposal: The Dying of the Trite

Popular, 4-0 with 1 DEF and Observer voting FOR. Enacted by JonathanDark.

Adminned at 27 Mar 2024 16:24:16 UTC

Repeal the rule “Trite”.

In the rule “Scoring”, remove “and the Trite at the time that the post is made” and the bullet point beginning “For each Private Criteria in the response that contains any of the nouns listed in the Trite”.

This rule doesn’t really seem to have taken off.

Story Post: Upgrade Request for Snap 015

Reached quorum 4 votes to 0. Processed by Kevan.

Adminned at 27 Mar 2024 09:24:04 UTC

I believe Snap 015 meets every Public Criteria:

Taken outside.
Includes a specific named entity Plymouth Rock
Includes one article of seeker: blue glove
Includes a message: “It’s a rock!”

Story Post: Snap 015: A Rock

Trite: sky, pole

Story Post: Upgrade Request for Snap 014

Reached quorum 5 votes to 0. Processed by Kevan.

Adminned at 27 Mar 2024 09:22:39 UTC

I believe Snap 014 contains a found instance of the BlogNomic username of another Seeker, namely Josh.

Story Post: Snap 014: If Josh Wins

The Trite is currently “sky, pole”.

Monday, March 25, 2024

Mentorship announcement

I will be mentoring Nadnavillus.

Joining Blognomic

Hey Everyone, 

I would like to join the current Dynasty.  I understand that I’m probably far behind but I thought I could at least start to understand the game play process.

Sunday, March 24, 2024

Story Post: Upgrade Request for Snap 013

Timed out, 2-2. Failed by JonathanDark.

Adminned at 26 Mar 2024 19:34:54 UTC

I believe that Snap 013 meets the Upgrade Benchmark “A Snap which meets every Public Criteria”

Story Post: Snap 013: A Bit of Gardening

Friday, March 22, 2024

Proposal: What’s the point of Points?

Reached quorum 5 votes to 0. Enacted by Kevan.

Adminned at 24 Mar 2024 12:48:58 UTC

In the rule “Scoring”, replace the text “they gain a number of Points” with “they gain an amount of Score”.

In the rule “Awards”, replace the text “Have more than 200 Points” with “Have more than 200 Score”.

Correcting places where the term “Points” is used instead of “Score”.

If we keep doing this, I suppose we could add a clause that says that Points and Score are interchangeable terms. However, being a named tracked variable, I’d prefer just to keep it Score, or rename all of it to Points, rather than having two different terms referring to the same thing.

Snisgo

Snisbo idles out after seven days without a post or comment. Quorum drops to 3.

Story Post: Upgrade Request for Snap 012

Reached quorum 3 votes to 0, applied by Kevan.

Adminned at 23 Mar 2024 10:33:47 UTC

I believe Snap #12 meets the Upgrade Criteria of “A Snap which meets every Public Criteria”, and that it do so in the following manner:

  • It was taken in an outside location
  • It includes a specific named entity that has a Wikipedia page (it’s a park near where I live which has a name; I’d rather not publicly identify it, but can do so privately if required) (Sciurus carolinensis is perhaps also a “specific, named entity”)
  • It features a boot that I was wearing at the time
  • It conveys the message “Hello World” to the viewer (this is more clearly legible at full size)

Poked

Pokes is idled after seven days of inactivity. Quorum remains 4.

Story Post: Snap 012: Squirrel

The Trite is currently “sky, pole”.

Proposal: Hidden in Plain Sight

Timed out 1 vote to 2. Failed by Kevan.

Adminned at 24 Mar 2024 12:47:09 UTC

Add a new rule called “Tokens”

Each Seeker may have a Token, which is an concrete noun. Each Token is privately tracked by its seeker, and publicly tracked by its sha256 hash which includes the Token plus a salt of 10 characters or less. A Seeker may change their Token at any time.

As a weekly action, if a Seeker has posted three different Snaps since they last changed their Token, each of those Snaps contains an instance of their Token, and their Token (or any of its synonyms) is not in the trite list, they may make a post to the blog with links to those three Snaps.

Each other Seeker may make one response to the post mentioning the one noun which they think matches the Token of the Seeker who posted the Snap

After 48 hours of making such a post, if no Seeker has accurately guessed their Token (or guessed any of its synonyms) in reply to the post, the Seeker who made the post may claim the Mastery in Subtle Product Placement Award

Add an Award called “Mastery in Subtle Product Placement” with a Standard of “May only be claimed as allowed by the rule “Tokens”“

Wednesday, March 20, 2024

Proposal: Expecting the Unexpected [Building Blocks]

Reached quorum, 4-0. Enacted by JonathanDark.

Adminned at 21 Mar 2024 17:01:30 UTC

If the proposal “Co-op No-op” failed, then to the Building Block “No Cooperation” (both in the ruleset and the Building Blocks wiki page), add a paragraph:-

If a Seeker feels that another Seeker has gone against this expectation in some way during the current dynasty, then they are encouraged to vote against all DoVs from that Seeker during that dynasty. This overrules the encouragement to vote according to the perception of a victory in the rule “Victory in Ascension”.

Per Jonathan’s question on Co-op No-op about whether a DoV can be reasonably voted down for going against the “loose definition” of the spirit of the rule.

Under the current ruleset, if a team cooperates their way to victory, the rules say that a player’s vote on that DoV is “encouraged to reflect whether or not they agree with the proposition that the poster has achieved victory in the current Dynasty”. Although No Cooperation says that the victor was “expected” not to do that, the ruleset is still encouraging each voter to vote on the proposition rather than the expectation.

So let’s make clear that it’s fine to vote against a DoV if you feel that this expectation has not been met.

Call for Judgment: uh-oh; I had an oopsie

Timed out and enacted, 3-0. Josh

Adminned at 22 Mar 2024 16:09:36 UTC

Uphold the action where Chiiika set her Private Criteria to include 30daf7b3b83f87396258e7c30211f0a23367f33f57d1c3055b5f62949f6a46b3 and 3600b793e6c5f658028f482626b551e3c49c605f294e591fe2e3b2ffbc6c6b94 performed at 09:31, 15 March 2024 as legal.

When I was generating new criterias I found that two of my old criteria is over 50 characters (thought it was 50 words) but can be expressed under 50 characters, namely
- Secret Criteria: there is a kind of public transport stop in the picture, Hash: 30daf7b3b83f87396258e7c30211f0a23367f33f57d1c3055b5f62949f6a46b3, Salt: n983L, Created at: 2024-03-15 17:25:11 HKT
-> can be simplified to “there is a public transport stop in the picture”
- Secret Criteria: characters from two or more kinds of language exist in the picture, Hash: 3600b793e6c5f658028f482626b551e3c49c605f294e591fe2e3b2ffbc6c6b94, Salt: b0RFW, Created at: 2024-03-15 17:30:00 HKT
-> can be simplified to “two or more kinds of language exist in the picture”

Tuesday, March 19, 2024

Proposal: Story Post: Upgrade Request for Snap 011: Poking the Waters

Passes 5-0—Clucky

Adminned at 22 Mar 2024 06:34:33 UTC

https://blognomic.com/archive/snap_011_poking_the_waters

This Snap contains an instance of me finding the username of the Seeker known as Pokes. I submit it for an upgrade request.

Story Post: Snap 011: Poking the Waters

The trite is: sky, pole

Story Post: Upgrade Request: Snap 010

Reached quorum and enacted, 5-0. Josh

Adminned at 20 Mar 2024 09:47:36 UTC

Snap 010 has the following characteristics:

* It was taken outdoors
* It includes a specific named entity that has its own Wikipedia page (https://en.wikipedia.org/wiki/Leyton_Midland_Road_railway_station)
* My right shoe is visible
* It exhorts the viewer to vote a certain way on a named proposal

I believe it therefore satisfies the Upgrade Benchmark of being “a Snap which meets every Public Criteria” and I should therefore be allowed to Upgrade.

A public test of the limits of “should”.

Story Post: Snap 010: Street Scene

The trite is: sky, pole

Proposal: Once More Unto

Timed out, 1-2. Failed by JonathanDark.

Adminned at 21 Mar 2024 16:55:35 UTC

Add the following as a subrule to the Appendix rule Clarifications, called Imperatives:

An action is ‘’‘optional’‘’ when it may be performed at the Seeker’s discretion, although it may be subject to other restrctions around time and circumstance. A move is optional when it uses the terms ‘may’, ‘is permitted to’, ‘can’ etc.

An action is ‘’‘obligatory’‘’ when the Seeker is compelled to perform it. When a Seeker is required by the ruleset to take an obligatory move then they may not undertake any other action, dynastic or core, except for voting, carrying out admin duties like resolving votable matters or rendering players idle or unidle, or other obligatory actions, until they have carried out that obligatory move. Rules that define obligatory moves use langauge like “should” or “is required to”. If it is discovered that a Seeker took an obligatory move out of order (i.e. after an optional move that they should not have been able to take due to an obligatory move having been outstanding), but it is also found that the outcome would not have varied had the moves been taken in the correct order, then it may be considered that no infraction has taken place.

An ‘’‘obligatory restriction’‘’ is a rule that sets out something that a Seeker may not do. It uses language like “should not”, “may not”, “cannot” or “is not permitted”. It violates the rules to knowingly carry out any action that carries an obligatory restriction. An obligatory restriction takes precidence over an obligatory action (i.e. where an obligatory restriction makes an obligatory action impossible to perform, the obligatory action must not be performed and may be considered not to be obligatory for the purposes of restricting other actions from being performed).

An action is ‘’‘mandatory’‘’ when a Seeker is required to perform it ‘‘and the game, to some extent, cannot continue until they have done so’‘. A mandatory action uses terms like “must” or “shall”. A rule that defines a mandatory action should set out what happens when that action is not carried out, but as a baseline, if a mandatory action is required to occur then no subsequent action that is dependent on that mandatory action occurring (i.e. an action whose conduct or effect would vary based on the performance of the mandatory action) may be carried out.

Repeal the subrule Imperatives, from the Keywords rule in the Appendix.

I hate dumping this many words into the ruleset for something that should be intuitive, but we repeatedly see that it isn’t - that the term “should” in particular is frequently used to compel a player when what it actually means - both in common English usage and as defined by the BlogNomic glossary - is that it is an optional recommendation. This attempts to collapse that ambigity by codifying what I perceive as the natural use of the terms in the game context.

Proposal: Co-op No-op [Building Blocks]

Timed out, 1-3. Failed by JonathanDark.

Adminned at 21 Mar 2024 16:53:36 UTC

Reword the Building Block “No Cooperation” (in both the ruleset and the Building Blocks wiki page) from:

In this dynasty, Seekers are expected to avoid co-operating to achieve Victory, except through the use of co-operative mechanisms defined in the Dynastic rules.

to:

If the dynasty has any defined victory conditions, then a Seeker may not take a dynastic action that would directly cause another Seeker’s gamestate to move closer to having achieved any of those conditions. If an action is defined in the rules as being a Bountiful Action then the previous sentence does not apply to it.

Before the final paragraph of Guesses, add:-

Resolving the Guess is a Bountiful Action.

Per comments on Monomethyl-P, an attempt to clarify what the No Cooperation rule might actually mean, or at least prompt some discussion about what people think it should and shouldn’t include.

Proposal: Abstraction

Timed out, 4-0. Enacted by JonathanDark.

Adminned at 21 Mar 2024 16:39:46 UTC

Add a new rule to the dynastic ruleset, called Awards:

Each Seeker can have a number of Awards, which is publicly tracked and defaults to zero.

At any time, if a Seeker has met the Standard for an Award then they may claim it by making a blog post announcing as such and then incrementing their Awards by 1. A Seeker may only claim each individual Award once in the dynasty.

Any Seeker who has claimed 5 Awards has achieved Victory.

The possible Awards and their Standards are as follows:

{| class="wikitable sortable"
|-
! Award !! Standard
|-
| Fine Art Photographer of the Year || Have more than 200 Points
|-
| Excellence in War Photography || Have a Development Interval of 1
|-
| Outstanding Composition || Have five private Criteria, each of which has an Unsatisfying score of 0 and a Satisfying score of 5
|-
| Grand Prix in Advertising Photography || Successfully Guess (i.e. post a Guess and have the target respond with a FOR mark to that Guess)
|}

If Proposal: b-b-b-b-bonus was enacted, change the Standard for Excellence in War Photography to “Have a Development Bonus of at least 3”.

Only four at the moment, to prevent instant win scams and give room for future mechanics

Tuesday, March 19, 2024

Proposal: b-b-b-b-bonus

Timed out, 5-0. Enacted by JonathanDark.

Adminned at 21 Mar 2024 05:22:49 UTC

In “Scoring” after “Each Seeker has a Development Interval, which is a publicly tracked number that defaults to 5” add “which is at least 2”

Add the following to “Scoring”

Each Seeker has a Development Bonus which is publicly tracked and defaults to 0. Whenever a Seeker posts a Snap, they gain a number of Points equal to three times their Development Bonus.

In “Upgrades” replace “When an Upgrade Request is enacted, the Development Interval of its poster is reduced by 1, to a minimum of 1, unless the same Seeker has already had a Upgrade Request enacted for the same Upgrade Benchmark previously in the dynasty, in which case their development interval is not reduced” with

When an Upgrade Request is enacted, the Development Interval of its poster is reduced by 1 (if it is three or higher) or their Development Bonus is increased by one (if their Development Interval is already 2), unless the same Seeker has already had a Upgrade Request enacted for the same Upgrade Benchmark previously in the dynasty, in which case their development interval is not reduced and their development bonus is not increased

The game speeding up to being one post per day feels excessive. This rewards doing upgrades past the first three, while limiting the pace of the dynasty a bit.

Proposal: monomethyl-p-aminophenol hemisulfate

Reached Quorum, 5-0. Enacted by JonathanDark.

Adminned at 19 Mar 2024 04:43:33 UTC

Add the following as new Upgrade Benchmarks:

* A Snap on which, after 48 hours, every Private Criteria claimed by another Seeker was Unsatisfied
* A Snap which meets every Public Criteria
* A Snap which includes a found instance of the BlogNomic username of another Seeker

Add the following as Public Criteria in the rule Criteria:

* A Snap which includes a specific named entity that had its own Wikipedia page at Mon 18/03/24—09:00 UTC
* A Snap in which at least one article of clothing worn by the posting Seeker at the time that the Snap was taken is visible
* A Snap that contains a message to the viewer

Another try at this, as the 5 day limit is starting to chafe

Sunday, March 17, 2024

Story Post: Snap 009: Night at the Minibus Stop


Current Trite: sky, pole


Editing Disclaimer: This is a screen capture of a photo, because iPhone shenanigans

Story Post: Snap 008: Postbox

The Trite is currently “sky, pole”.

Wandered too close to the woods

Brendan idles after 7 days of inactivity. Quorum drops to 4.

Story Post: Snap 007 - Monsters in the Back Yard

Editing Disclaimer: I used the brightness, sharpness, and exposure tools on my phone on this photo to try to make the piece of paper with my username and word-of-the-day more clear. It also wound up producing some weird light squiggle artifacts. The result isn’t great, but should still be legible. I am definitely not a professional.

The Trite is: sky, pole

Saturday, March 16, 2024

Proposal: Risk It For the Biscuit

Timed out, 4-0. Enacted by JonathanDark.

Adminned at 18 Mar 2024 23:37:06 UTC

Add the following to “Criteria”

A Private Criteria’s Exposure is equal to its Unsatisfying Score plus its Satisfying Score

The date and time (to nearest minute) a given Private Criteria was last changed should be tracked on the Gamestate tracking page in a column called “last modified”

in “Guesses” replace

reduce their own Score by 3, and increase the score of the Guesser by 3

with

reduce their own Score by the Exposure of that private criteria, and increase the score of the Guesser by the same amount, and then remove that Private Criteria from the Target’s private criteria list (resetting its satisfying and unsatisfying counts to zero in the process)

The more examples you give of your private criteria in action, the more points you can get from it but also the easier it becomes for someone else to guess. So I like the idea of adding more risk to keeping the criteria for a long time.

Bubbling last modified time up to make it less annoying for people to isolate guesses

Friday, March 15, 2024

Proposal: Everybody Move In A Bit [Building Blocks]

Vetoed by the Observer. Failed by Kevan.

Adminned at 17 Mar 2024 17:47:35 UTC

Remove “Low-Player Mode” from the Building Blocks section of the ruleset.

To the “Everyone’s Playing” Building Block, in both the ruleset and the Building Blocks page, add:-

The Observer is not excluded from the count of Seekers in the Dormancy rule.

Turning off Low-Player Mode, with six active players. Seems like a Playing Observer should also be part of the head count for Dormancy.

Paralyzed by the beauty

I would like to idle

Proposal: Patron of the Arts

Timed out 2 votes to 2. Failed by Kevan.

Adminned at 17 Mar 2024 17:46:50 UTC

Add a new rule named “Commissions” with the following text:

Each Seeker has a publicly-tracked Commission, defaulting to empty, and which can be either empty or a combination of a Commission Criteria, which is a phrase of 1 to 10 English words, and a non-negative integer contained in () brackets named the Commission Price. If it has been more than 48 hours since a Seeker has changed any part of their Commission, or if their Commission is empty, that Seeker may spend any positive amount of Score, up to the amount of Score that they have, to perform a Recommission, which is one of the following actions:
* That Seeker may change their Commission from empty to a Commission Criteria and Commission Price, where the Commission Price must be the same as the amount of Score they spent.
* That Seeker may change their existing Commission Criteria to a different Commission Criteria, where the Commission Price must be the same as the amount of Score they spent.
* That Seeker, if they have a non-empty Commission, may increase their Commission Price by the amount of Score they spent as long as they don’t change their Commission Criteria.

Additionally, if it has been more than 48 hours since a Seeker has changed any part of their Commission, they may set their Commission to empty.

In the rule “Scoring”, at the end of the rule add the following text:

Additionally, within 48 hours of such a Shot having been posted, the poster of that Shot may at most once respond to it with the comment that they are claiming a Commission. Such a claim must include the name of the Seeker whose Commission is being claimed, that Seeker’s Commission Criteria, and that Seeker’s Commission Price. If that Shot meets the Commission Criteria mentioned in this claim, and the Seeker who owns that Commission is not the same Seeker as the poster of that Shot, then the poster of that Shot may increase their Score by the Commission Price mentioned in this claim.

 

This allows a Seeker to incentivize other Seekers to include or exclude certain things in their photos. The Seekers who do so gain Score, and the Seeker who posted the Commission can use this to increase their Satisfying or Unsatisfying counts, which could pay off in better scoring in the long run for the Seeker who posted the Commission.

Proposal: Catching up with the photos

Enacted 4-0 by Chiiika

Adminned at 17 Mar 2024 06:39:17 UTC

Enacts a new rule, “Catching Up with the Photos”, with the following text

While a Seeker has exactly 0 Score and has more than one Private Criteria having a non-null value, a Seeker may perform the following Atomic Action once per week:
- For the previous three Shots in chronological order, perform the following bullet points:
- - Respond to the Shot stating which of their own Private Criteria that Shot satisfies and does not satisfy.
- - For each Private Criteria in the response that the Shot satisfies, that Private Criteria’s satisfying count is incremented by one, and increment their Score by that Private Criteria’s unsatisfying count.
- - For each Private Criteria in the response that the Shot does not satisfies, that Private Criteria’s satisfying count is incremented by one, and increment their Score by that Private Criteria’s satisfying count.

Photographer Chiiika

This seems a noice dynasty. I unidle myself, Quorum stays at 5.

Proposal: Shot Diversification

Enacted by Chiiika, 5-0.

Adminned at 16 Mar 2024 11:25:58 UTC

In “Upgrades” after “When an Upgrade Request is enacted, the Development Interval of its poster is reduced by 1, to a minimum of 1”

, unless the same Seeker has already had a Upgrade Request enacted for the same Upgrade Benchmark previously in the dynasty, in which case their development interval is not reduced. (Which Upgrade Benchmarks have been enacted for which seekers should be tracked on the gamestate tracking page for easy reference)

 

Scoring the same benchmark multiple times feels boring

Proposal: Order Up!

Enacted 6-0 by Chiiika.

Adminned at 16 Mar 2024 11:24:13 UTC

In Scoring after “provided that none of their Private Criteria has been changed since that Shot was posted” add

and provided that there are no other Shots that were posted before the shot in question, within the last 48 hours, and which the Seeker in question has not already responded to in this manner

 

Waiting for other shots to be posted in order to try and optimize your satisfying/unsatisfying scores is currently an optimal strategy, especially if https://blognomic.com/archive/supersaturation passes, but it’s behavior I’d rather not encourage. Intent of this is to make you respond to all snaps in order.

Thursday, March 14, 2024

Proposal: Quite Trite

Enacted 5-0 by Chiiika.

Adminned at 16 Mar 2024 11:20:07 UTC

In the rule “Scoring”, in the bulleted list after the text “Upon doing so:”, add this as the first bullet point in that list:

* For each Private Criteria in the response that contains any of the nouns listed in the Trite mentioned in that Shot post, that Private Criteria cannot be used to increment any Seeker’s Score for that shot, and the remaining bullet points in this list must be ignored with regard to that Private Criteria.

I still think the Trite list has its place.

Proposal: Diptych

Timed out and failed by Chiiika, 2-3.

Adminned at 16 Mar 2024 11:16:54 UTC

Add the following as a third bullet point to the list in the rule Scoring:

* Increment the Score of the poster of the Shot being responded to by the amount the owner’s Score was incremented by as a result of this Action.

Rename the rule Editing Disclaimer to “Editing Rules” and rewrite it as follows:

Any Snap must include a description of any edits or changes made to the photograph prior to it being made a Shot, with a lack of such a description indicating that no editing was done. Major edits to a photo that substantially change its appearance, composition or content are not permitted, but minor adjustments to photos are acceptable. These include cropping, dodging and burning, conversion into grayscale, elimination of dust on camera sensors and scratches on scanned negatives or scanned prints and normal toning and color adjustments. These should be limited to those minimally necessary for clear and accurate reproduction and that accentuate the authentic nature of the photograph. Changes in density, contrast, color and saturation levels that substantially alter the original scene are not acceptable. Elements may not be added to a picture under any circumstances. The use of AI tools to modify a picture is prohibited.

Two unrelated changes. The first change restores sniping the criteria of other players. The second borrows from the AP guidelines on photojournalism, and may be a little too restrictive as a staring point but is intended to ensure that the photo itself retains primacy over any editing that may take place.

Story Post: Snap 006: Sleepless in Seattle

The current trike is sky

Wednesday, March 13, 2024

Proposal: Supersaturation

Reached quorum 6 votes to 0 with 1 unresolved Imperial DEF. Enacted by Kevan.

Adminned at 15 Mar 2024 11:55:28 UTC

If “A Private Criteria is considered Saturated if its satisfying count plus its unsatisfying count is greater than or equal to seven or the number of seekers, whichever is greater” exists in the ruleset, replace it with:-

A Private Criteria is considered Saturated if its satisfying count or its unsatisfying count is greater than or equal to five (or half the number of seekers, whichever is greater)

Might be more interesting to have Saturation happen at the extremes, rather than always at a neutral 7-photo timeout (the total of the two counts will always go up by 1 per photo scored).

Proposal: Delocalisation

Timed out 3 votes to 3. Failed by Kevan.

Adminned at 15 Mar 2024 11:54:14 UTC

In the rule Upgrades, add the following to the end of the first Upgrade Benchmark:

(other than the Observer)

Add the following as new Upgrade Benchmarks:

* A Snap that includes at least one building that appeared as a Wonder in the base game or officially released expansions to Civilization 6 (each Wonder may only be claimed as an Upgrade Benchmark once by each Seeker)
* A Snap which for which, after 48 hours, the poster has generated no Score
* A Snap in which includes two or more of the following geological features: a mountain, a waterfall, a glacier, a lake, a volcano, a canyon, gorge or ravine, a sand dune, or the sea

Removing the London advantage, and adding some new Upgrade mechanisms.

List of Civ 6 Wonders: https://civilization.fandom.com/wiki/List_of_wonders_in_Civ6

Proposal: Daily actions are not very fun

Quorum Reached. Passes 5-0—Clucky

Adminned at 15 Mar 2024 05:09:54 UTC

In “Scoring” replace “Within 24 hours” with “Within 48 hours”

Feel like we long ago established that actions that required daily activity weren’t great for the game

Wednesday, March 13, 2024

Proposal: Runaway games are no fun

Timed out. Passes 5-0—Clucky

Adminned at 15 Mar 2024 05:06:27 UTC

Add the following to Criteria

A Private Criteria is considered Saturated if its satisfying count plus its unsatisfying count is greater than or equal to seven or the number of seekers, whichever is greater

In Scoring, whenever it appears replace

For each Private Criteria

with

For each non-Saturated Private Criteria

The current rules seem rather poorly setup people joining late. Basically mean if you fall behind at all, you’re kinda screwed as the players who grind can easily get to the point where in a few rounds they are scoring 5+ points criteria round per post and you’re still always a few behind and fall further and further behind each post. Zaps any motivation out of actually participating in the dynasty because its simply rewarding whoever is the most active and so can build up the highest point totals. This still lets you score more points from having a mix of satisfying/unsatisfying claims but prevents the game from being a total runaway because eventually you have to restart

Story Post: Snap 005: The Angel of Islington

The trite is sky

Monday, March 11, 2024

Proposal: Criteria Cleanup

Timed out, 2-3. Failed by JonathanDark.

Adminned at 14 Mar 2024 05:44:32 UTC

In the rule Scoring, change “may at most once respond” to “should respond, no more than once,”.

For each Seeker whose EVC on this proposal contains exactly two different numbers between 1 and 5, remove the two of their Criteria (even if blank) associated with their stated numbers and condense the remainder into three Criteria. Then, in the rule Criteria, change “set of up to five Private Criteria” to “set of up to three Private Criteria”.

Lovely to have so many players but tracking up to 40 private criteria seems overwhelming. I’m on the fence about cutting it down to three or two; even three is potentially 24 different criteria we have to work out from potentially sparse evidence.

Also making it so scoring on other peoples’ snaps is encouraged, even when not optimal.

Story Post: Snap 004: The Alley

The current Trite is: sky

Proposal: Western Spiral Arm

Timed out, 2-2. Failed by JonathanDark.

Adminned at 14 Mar 2024 05:18:54 UTC

If the text “A Snap that was taken in the same place as another Snap taken by a different Seeker” exists in the ruleset, replace it with:-

A Snap that was taken within 100m of another Snap taken by a different Seeker

Story Post: Snap 003: A Path

The Trite is currently “sky”.

Proposal: Refocused Lens

Reached quorum 5 votes to 0. Enacted by Kevan.

Adminned at 13 Mar 2024 11:37:52 UTC

Add the following to Scoring after “which includes a single Authentic Shot and the Trite at the time that the post is made.”

Such a post is known as a Snap.

In “Criteria” replace every instance of “identical” with “equivalent”. In the same rule, after the text “publicly tracked by its sha256 hash” add:

which includes the Private Criteria plus a salt of 5 characters or less

and in the same rule, replace “Each Private Criteria is also tracked with a count” with:

Each Private Criteria also has a publicly-tracked count

In the rule “Scoring”, after the text “which of their own Private Criteria that Shot satisfies and does not satisfy” add the following text:

, provided that none of their Private Criteria has been changed since that Shot was posted

Some miscellaneous fixes from previous Proposals. I think that Satisfying Shots and Unsatisfying Shots should be publicly tracked, since they are directly related to Scoring. UPDATE: also closed the exploit that Kevan recently used.

Proposal: Paper Trail

Reached quorum 5 votes to 1. Enacted by Kevan.

Adminned at 13 Mar 2024 11:35:48 UTC

In the rule “Criteria”, add the following subrule named “Audit”:

As part of a Declaration of Victory, the Seeker posting the DoV must include a history of their Private Criteria and corresponding salt in the body of the DoV post. Any DoV which does not contain this information is not considered a valid DoV and should be marked as illegal.

Proposal: Hunter/Seeker

Timed out 3 votes to 2. Enacted by Kevan.

Adminned at 13 Mar 2024 11:34:52 UTC

Add a new dynastic rule, called Upgrades:

If a Seeker believes that a Shot that they have previously posted (but which has not previously been the subject of an Upgrade Request) meets an Upgrade Benchmark then they may make an Upgrade Request.

An Upgrade Request is a post in the Story Post - Votable Matter category which indicates a single Snap posted by the same author and a single Upgrade Benchmark that it purports to meet, and nothing else.

An Upgrade Request is voted on and resolved in the same manner as a Proposal, with the exceptions that it does not need to be resolved in chronological order (nor does it count as a proposal for the purposes of determining the oldest pending Proposal). Seekers should vote FOR on any Upgrade Request where they believe that the specified Snap does meet the specified Upgrade Benchmark. When an Upgrade Request is enacted, the Development Interval of its poster is reduced by 1, to a minimum of 1.

Upgrade Benchmarks are listed in this rule and are as follows:
* A Snap that was taken in the same place as another Snap taken by a different Seeker.

Story Post: Snap 002: Ok NOW it’s right

whoops x2.

Monday, March 11, 2024

The REAL Snap 002

whoops.

Snap 002: Dusk-Blue Street Sign

Took this while on my nightly walk - probably going to try varying my route to get some pics of different locations :)

Proposal: Spice of Life

Withdrawn. Failed by JonathanDark.

Adminned at 12 Mar 2024 15:57:15 UTC

Add the following to Scoring after “a Seeker may make a post in the story post category with the title of their choice which includes a single Authentic Shot”

and declares which (if any) non-expired Public Criteria the shot meets. Such a post is known as a Snap.

and after “the poster gains Score equal to the number of Criteria declared met in response to that post” add

plus the number of non-expired public criteria that met the shot (using the list of public criteria and their expiration status at the time the shot was posted )


Add the following the first Paragraph of “Criteria”

Each Public Criteria also has an Expiration Date which is tracked next to it in the list of Public Criteria. If it after the Expiration Date for a Public Criteria, it is considered to be Expired. Any Seeker may remove an Expired Public Criteria from the list of Public Criteria at any time.

Set the Expiration Date of every Public Criteria to be one week from the time this proposal is enacted.

Add the following subrule to “Criteria” called “New Public Criteria”

If at least three Snaps have been posted, then as a weekly action a Seeker may add a new Public Criteria of their choosing, provided none of three most recently posted Snaps contain Shots which meet it and provided it is not equivalent to any existing non-expired Public Criteria. The expiration date of this new public criteria is one week after the action is performed

In “Criteria” replace “identical” with “equivalent”

Proposal: Up the contrast slightly… and maybe shift the hue a bit more red

Popular, 3-0 with 2 DEFs and Observer voting FOR. Enacted by JonathanDark.

Adminned at 12 Mar 2024 15:52:58 UTC

Add the following to the second paragraph of the rule “Shots”:

A typographical error does not prevent the Shot from being Authentic, as long as it’s obvious what the intended word is.

Add a subrule to the rule “Scoring” named “Editing Disclaimer,” which reads:

Any new post that contains a Shot must include a description of any edits or changes made to the photograph prior to it being made a Shot, with a lack of such a description indicating that no editing was done. If a post is found to have broken this rule, the Seeker responsible or any Admin should replace the Shot in the offending post with this image, no scoring may be performed for that post (and any scoring already awarded to the poster should be reverted), and the responsible Seeker may create a new post as if they had not made the offending post.

Don’t want to ban editing, since I want to try my hand at it this Dynasty, but it should probably be tracked. Also, typos shouldn’t make posts invalid imo

Proposal: Half-Satisfied

Popular, 4-0 with 1 DEF and Observer voting FOR. Enacted by JonathanDark.

Adminned at 11 Mar 2024 17:19:06 UTC

Replace “Each Seeker has a set of up to five Private Criteria, which are a type of Criteria - defaulting to blank - which are privately tracked by themselves, and which are publicly tracked through the use of an sha256 hash which includes those criteria as well as a reasonable (no more than 5 character) salt. A Seeker may set or amend their Private Criteria as a weekly action.” with:

Each Seeker has a set of up to five Private Criteria, which are a type of Criteria - defaulting to blank. Each Private Criteria is privately tracked by its seeker, and publicly tracked by its sha256 hash. Each Private Criteria is also tracked with a count of satisfying Shots and unsatisfying Shots, both defaulting to 0. At any time a Seeker may change any of their Private Criteria while also resetting its satisfying and unsatisfying counts to zero.

In “Scoring”, replace the text after “Within 24 hours” to the end of the rule with:

Within 24 hours of such a Shot having been posted, each Seeker (including the poster) may at most once respond to it stating which of their own Private Criteria that Shot satisfies and does not satisfy. Upon doing so:
* For each Private Criteria in the response that the Shot satisfies, that Private Criteria’s satisfying count is incremented by one, and its owner’s Score is incremented by that Private Criteria’s unsatisfying count.
* For each Private Criteria in the response that the Shot does not satisfy, that Private Criteria’s unsatisfying count is incremented by one, and its owner’s Score is incremented by that Private Criteria’s satisfying count.

To avoid trite criteria (triteria?), this rewards keeping around long-standing private criteria with the goal of being satisfied by half the pictures: if they all satisfy, your satisfying count will be high, but you never get unsatisfying pictures that can capitalize that in your score, and vice-versa.

Rubbelt Gets Lost In The Woods

Rubbelt has been idled after over 7 days of inactivity. Quorum remains unchanged at 5.

Proposal: Reasonable Limits

Reached quorum 5 votes to 0, enacted by Kevan.

Adminned at 11 Mar 2024 12:47:13 UTC

Add the following as a sub-rule to the rule Criteria:

A Criteria must have the following characteristics:
* May be no longer than 50 characters in length
* Must be expressed in vernacular English

I don’t know yet whether it’s better for private criteria to be easily guessable or very obscure, so I’m a little reluctant to over-define the possibility space - but short and understandable feels like a smart restriction in pretty much all circumstances.

Story Post: Snap 001: A Rainy London Park

Proposal: Fixing It In Post

Reached quorum 6 votes to 0. Enacted by Kevan.

Adminned at 11 Mar 2024 12:42:28 UTC

In “Scoring”, replace “A seeker may not respond to a scoring post if they changed their private criteria after the scoring post was made” (if it exists) with:-

A seeker may not respond to a scoring post if they have changed any of their private criteria since that scoring post was made.

Patching Clucky’s proposal, also making it unambiguous that changing a single criterion is enough.

Proposal: It’s Impolite to be Trite

Reached quorum 5 votes to 0. Enacted by Kevan.

Adminned at 11 Mar 2024 12:41:08 UTC

In the rule “Criteria” add the following subrule named “Trite”:

There is a publicly-tracked list named Trite, defaulting to an empty list, that can either be empty or contain one or more single-word nouns that are unique from the other nouns in the list. The Trite can be no larger than 20 nouns.

As a weekly action, a Seeker may either add a unique noun to the Trite, as long as the Trite is not already at its maximum length, or replace an existing noun with a different one as long the replacement is still unique from the others in the Trite.

In the rule “Scoring” after the text “a Seeker may make a post in the story post category with the title of their choice which includes a single Authentic Shot” add the following text:

and the Trite at the time that the post is made

and in the same rule, after the text “may respond to it stating how many of their own Private Criteria that Shot meets” add the following text:

, but may not include any Private Criteria that contains any of the nouns listed in the Trite in the the post containing that Shot

Here’s a way we as a group can dynamically affect Private Criteria by adding common things in photos that people shouldn’t get Score for. It can also become a strategic place of activity if someone consistently keeps scoring on their own pictures with the same subject matter.

Sunday, March 10, 2024

I need to touch grass

And this dynasty is a good excuse. Unidle me please!

Proposal: Mise en Abyme

Popular, 4-1 with 2 DEFs and Observer voting FOR. Enacted by JonathanDark.

Adminned at 11 Mar 2024 04:18:48 UTC

Activate the Building Block “No Cooperation.”

No Private Communication seems too heavy-handed for this theme, but even a two-player cabal with an “I get five points and you get five points” criteria-matching mechanic would quickly outrun anyone who’s not buddied up.

Proposal: Keep It Secret, Keep It Safe

Quorum Reached. Passes 6-0—Clucky

Adminned at 11 Mar 2024 02:07:42 UTC

In Scoring replace “a Score, which is a publicly tracked number” with “a Score, which is a publicly tracked, possibly negative, number”

Add the following to “Criteria”

Two Criteria are considered to be identical if any shot which meets the first criteria also meets the second criteria, and any shot which does not meet the first criteria also does not meet the second criteria. None of a Seekers private criteria can be equivalent to another of that Seekers private criteria.


Add a new rule called “Guesses” with the following text

As a Weekly Action, a Seeker (the Guesser) with a score of at least 3 guess a private criteria of another Seeker (the Target) who is not currently Targeted by performing the following Atomic Action known as Initiating a Guess

* Reduce the score of the Guesser by 3
* Make a story post to the blog clearly declaring the name of the Targeted Seeker, and what the guesser thinks one of their Private Criteria are

The Target is now considered Targeted, and may not take any other dynastic action until they perform the following Atomic Action known as Resolving the Guess

* If the guess is equivalent to one of their private Criteria, respond to the post with a for, reduce their own Score by 3, and increase the score of the Guesser by 3
* If the guess is not equivalent to any of their private Criteria, respond to the post with a against

At this point, the target is no longer considered targeted

Proposal: Criteria Collection

Reached quorum 5 votes to 0. Enacted by Kevan.

Adminned at 10 Mar 2024 13:58:46 UTC

In “Scoring” add

A seeker may not respond to a scoring post if they changed their private criteria after the scoring post was made

Proposal: All Points East

Popular, 6-0. Enacted by JonathanDark.

Adminned at 10 Mar 2024 06:32:45 UTC

Add a new dynastic rule to the ruleset, called Scoring:

Each Seeker has a Development Interval, which is a publicly tracked number that defaults to 5, and a Score, which is a publicly tracked number defaulting to 0.

No more than once per number of days equal to their Development Interval, a Seeker may make a post in the story post category with the title of their choice which includes a single Authentic Shot.

Within 24 hours of such a Shot having been posted, each Seeker (including the poster) may respond to it stating how many of their own Private Criteria that Shot meets. After those 24 hours have elapsed, the poster gains Score equal to the number of Criteria declared met in response to that post, and each responder to that post gains Score equal to the number of their own Private Criteria that that Shot met.

Proposal: Snap Happy

Popular, 6-0. Enacted by JonathanDark.

Adminned at 10 Mar 2024 06:12:15 UTC

Add a new dynastic rule to the ruleset, called Shots:

Seekers may create Shots by taking photographs (or having photographs taken on their behalf) and hosting them through the image hosting functionality offered by the BlogNomic wiki.

A Shot is confirmed as Authentic if it includes an appearance of a hand-written note (as part of the Shot) which includes the name of an active Seeker and the Merriam Webster Word of the Day for the day on which the Shot was taken, or the preceding day (per http://www.merriam-webster.com/word-of-the-day).

Add a new dynastic rule to the ruleset, called Criteria:

There exist a number of Public Criteria, which are a type of Criteria, and which are listed in this rule. Each Seeker has a set of up to five Private Criteria, which are a type of Criteria - defaulting to blank - which are privately tracked by themselves, and which are publicly tracked through the use of an sha256 hash which includes those criteria as well as a reasonable (no more than 5 character) salt. A Seeker may set or amend their Private Criteria as a weekly action.

An Authentic Shot’s Criteria Score is equal to the number of Criteria it meets.

The following Public Criteria exist:
* The Shot was taken in an outside location.

Ascension Address: The Sequel

As any good sequel should, I’m going to stick to the formula that worked the last time: no narrative pre-amble, just an acknowledgement that Spring is here, in the Northern hemisphere at least, and so it’s a good time to go outside and take in the beauty of the world.

I’m very open to seeing what direction proposals take, but I’m especially interested in proposals that encourage real-world interactions with other players - including in person where players are geolocated.

Change the term Vassal to Seeker and Sovereign to Observer. Activate the Building Block Everyone’s Playing and Low-Player mode; deactivate all other Building Blocks. Change the Public Tracking page to “Photo Gallery”.

Starting in a similar place to Kevan XVIII and seeing where it goes.

Look Upon My Works

Post-dynastic washup.

I liked this ruleset in the end. Only thing it needed was a few more committed players.

Friday, March 08, 2024

Declaration of Victory: How Happy Those Whose Walls Already Rise

4-0, greater than 2/3 of the Vassals and the Sovereign voted FOR. Enacted by JonathanDark.

Adminned at 09 Mar 2024 07:33:02 UTC

As the only Vassal with less than 10 damage, I have achieved victory.

Story Post: Herald: March 8, 2024

  • Desertfrog assigned 4 Serfs to Dig and 1 Serf to Smelt, gained 2 Stone, and converted 1 Ore to 1 Iron.
  • Josh assigned 9 Serfs to Repair and removed 9 Damage.
  • naught assigned 2 Serfs to Chop, 4 Serfs to Dig, and 1 Serf to Smelt, and gained 2 Wood, 2 Stone, and converted 1 Ore to 1 Iron.
  • Rubbelt assigned 3 Serfs to Chop and 1 Serf to Smelt, gained 3 Wood, and converted 1 Ore to 1 Iron.
  • The following Wave of enemies attacked each Vassal’s castle:
    • 1 Drake (Large) (12 Strength each - Air)
    • 2 Tental (Medium) (5 Strength each - Sea)
  • A Lightning Curse caused the Structure (or Structures, if tied) with the highest sum of Defensive Values for each Vassal to be ignored during this attack.
  • The results of the attack were as follows:
    • Desertfrog’s Large Stone Wall was ignored due to the Lightning Curse. The Drake and 2 Tentals were not stopped by the Small Moat and Desertfrog took 22 Damage. Desertfrog lost 1 Reputation.
    • Josh’s Large Moat was ignored due to the Lightning Curse. The Medium Dam defended against the 2 Tentals, and the Large Wooden Wall slowed down the Drake, but it still got through, and Josh took 6 Damage. Josh lost 1 Reputation.
    • naught’s Medium Stone Wall was ignored due to the Lightning Curse. The Large Wooden Wall defended against 1 Tental, and slowed down the other Tental and the Drake, but they got through, and naught took 10 Damage.
    • Rubbelt’s Large Wooden Wall was ignored due to the Lightning Curse. The Medium Wooded Wall slowed down the 2 Tentals and the Drake, but all of them broke through, and Rubbelt took 14 Damage.
  • Desertfrog contributed 13 to the War Effort.
  • Josh contributed 40 to the War Effort.
  • naught contributed 29 to the War Effort.
  • Rubbelt contributed 25 to the War Effort.
  • The next Building Wave contains 47 total Strength of Enemies and Curses:
    • A Crawl Curse will cause Small Enemies to only be defended by Small Structures during the Charging of the Wave.
    • 1 Carpathian (Gargantuan) (25 Strength each - Land)
    • 12 Destrals (Small) (1 Strength each - Air)

Wednesday, March 06, 2024

Almost The Halfway Point

Just a heads-up that we’re almost to the halfway point for the Final Advance. I’m estimating that we’ll reach it in 2-3 Fortnights, or roughly March 15.

There’s a possibility that we’ll hit the Default Mode win condition sooner if folks aren’t careful.

Story Post: Herald: March 5, 2024

  • Desertfrog assigned 2 Serfs to Dig and 3 Serfs to Mine, and gained 1 Stone and 1 Ore.
  • Josh assigned 8 Serfs to Chop and gained 8 Wood.
  • naught assigned 4 Serfs to Dig and 3 Serfs to Mine, and gained 2 Stone and 1 Ore.
  • Rubbelt assigned 2 Serfs to Dig and 3 Serfs to Mine, and gained 1 Stone and 1 Ore.
  • The following Wave of enemies attacked each Vassal’s castle:
    • 1 Razorspine (Large) (11 Strength each - Sea)
    • 2 Flingers (Medium) (5 Strength each - Air)
    • 7 Destrals (Small) (1 Strength each - Air)
  • The results of the attack were as follows:
    • Desertfrog’s Large Stone Wall defended against 2 Flingers and a Razorspine, while the Folly rendered all 7 Destrals harmless, and Desertfrog took no damage. Desertfrog gained 1 Reputation and 28 bonus War Contribution.
    • Josh’s Large Wooden Wall defended against 1 Flinger, and the Small Stone Wall and Small Stone Tower defended against 7 Destrals, but 1 Flinger and 1 Razorspine got through the Large Wooden Wall, and Josh took 9 Damage. Josh lost 1 Reputation.
    • naught’s Medium Stone Wall defended against 2 Flingers, and the Large Wooden Wall and Small Stone Tower defended against 7 Destrals, but the Razorspine got through the Large Wooden Wall, and naught took 5 Damage. Naught lost 1 Reputation.
    • Rubbelt’s Large Wooden Wall and Medium Wooden Wall defended against 2 Flingers, and the Small Stone Tower defended against 7 Destrals, but the Razorspine got through the Large Wooden Wall, and Rubbelt took 5 Damage.
  • Desertfrog gained 1 Serf due to Reputation but 1 Serf was turned away due to lack of Capacity.
  • Josh gained 1 Serf due to Reputation.
  • Desertfrog contributed 15 to the War Effort.
  • Josh contributed 41 to the War Effort.
  • naught contributed 29 to the War Effort.
  • Rubbelt contributed 25 to the War Effort.
  • The next Building Wave contains 37 total Strength of Enemies and Curses:
    • A Lightning Curse will cause the Structure (or Structures, if tied) with the highest sum of Defensive Values for each Vassal to be ignored.
    • 1 Drake (Large) (12 Strength each - Air)
    • 2 Tental (Medium) (5 Strength each - Sea)

Proposal: Oversucceeding

Timed out, 2-0. Enacted by JonathanDark.

Adminned at 07 Mar 2024 15:26:52 UTC

In the Fortnight atomic action, remove the bullet point which reads ‘If any Vassal loses Serfs due to this step, they also take 3 Damage.’

Doesn’t do anything as written, probably shouldn’t do the thing it’s intended to do.

Monday, March 04, 2024

Taara’s Castle Sinks Into the Swamp

Taara has been idled after 7 days of inactivity. Quorum drops to 3.

Sunday, March 03, 2024

Proposal: Call my Architect

Enacted popular, 3-0. Josh

Adminned at 05 Mar 2024 14:53:32 UTC

Add the following to the list of Structures:

| Iron Wall || Iron || Land, Sea, Air || 40, 10, 10
| Lightning Rod || Iron || Sea, Air || 15, 15
| Blasters || Iron || Land, Sea, Air || 0, 0, 0*

Add the following immediately after the table of Structures:

* At the point at which a Vassal builds Blaster, and at any time at which they upgrade their Blaster, they may choose a single Theatre and add a defensive value of 20 to their Blaster in that Theatre.

Proposal: Expanding the Menagerie

Popular, 4-0. Enacted by JonathanDark.

Adminned at 04 Mar 2024 21:46:31 UTC

In the subrule “Enemies” add the following rows to the end of the table:

|-
| Drake || Air || Large || 12
|-
| Carpathian || Land || Gargantuan || 25
|-
| Shoggal || Sea || Gargantuan || 22
|-
| Phlaxxon || Air || Gargantuan || 23

Saturday, March 02, 2024

Story Post: Herald: March 2, 2024

  • Desertfrog assigned 4 Serfs to Dig and 1 Serf to Smelt, gained 2 Stone, and converted 1 Ore to 1 Iron.
  • Josh assigned 3 Serfs to Chop and 4 Serfs to Dig, and gained 3 Wood and 2 Stone.
  • naught assigned 6 Serfs to Chop, and gained 6 Wood.
  • Rubbelt made no changes, and gained 3 Wood and 1 Stone.
  • Taara left all Serfs idle and gained nothing.
  • The following Wave of enemies attacked each Vassal’s castle:
    • 1 Tental (Medium) (5 Strength each - Sea)
    • 1 Donker (Medium) (6 Strength each - Land)
    • 3 Pilk (Small) (2 Strength each - Sea)
    • 2 Gobbos (Small) (1 Strength each - Land)
  • The results of the attack were as follows:
    • Desertfrog’s Medium Stone Wall defended against 1 Donker, 1 Tental, and 2 Pilk, and the Small Moat defended against 2 Gobbos. The 3rd Pilk broke through the Medium Stone Wall, and Deserfrog took 1 Damage.
    • Josh’s Large Wooden Wall defended against 1 Donker and 1 Tental, the Small Stone Wall defended against 2 Gobbos and 2 Pilk, and the third Pilk smashed through the Small Stone Wall but was stopped by the Small Dam. Josh took no Damage and gained 10 Land and 19 bonus War Contribution.
    • naught’s Medium Stone Wall defended against 1 Donker, 2 Gobbos, 1 Tental, and 2 Pilk. The third Pilk smashed through the Medium Stone Wall and swam unstopped by any other defenses, and naught took 1 Damage. Naught lost 1 Reputation.
    • Rubbelt’s Medium Wooden Wall defended against 1 Donker, the Small Stone Tower defended against 2 Gobbos, and the Small Dam defended against 3 Pilk, but the Tental swam under the Small Dam and broke through the Medium Wooden Wall. Rubbelt took 1 Damage.
    • Taara had no defensive structures and took 19 damage.
  • Josh gained 2 Serfs due to Reputation but 1 Serf was turned away due to lack of Capacity.
  • naught gained 1 Serf due to Reputation.
  • Desertfrog contributed 10 to the War Effort.
  • Josh contributed 31 to the War Effort.
  • naught contributed 24 to the War Effort.
  • Rubbelt contributed 14 to the War Effort.
  • The next Building Wave contains 28 total Strength of Enemies and Curses:
    • 1 Razorspine (Large) (11 Strength each - Sea)
    • 2 Flingers (Medium) (5 Strength each - Air)
    • 7 Destrals (Small) (1 Strength each - Air)

naught Returns

Per the CfJ “Live Game”, naught has been unidled. Quorum rises to 4.

Friday, March 01, 2024

Proposal: Window Tax

Timed out and failed, 1-1. Josh

Adminned at 03 Mar 2024 19:18:12 UTC

Make a new 4th bulletpiont in the fortnight action:

The vassal with the most structures losses wood. as much wood as he has structures. If he is unable to lose that amount of wood he loses 1 serf instead

Call for Judgment: Live Game

Popular, 4-0. Enacted by JonathanDark.

Adminned at 02 Mar 2024 17:56:42 UTC

Make the idle Vassal naught unidle.