Thursday, September 01, 2022

Proposal: One of the world’s certainties

Reaches quorum with 8-0 and is enacted -SingularByte

Adminned at 02 Sep 2022 04:11:34 UTC

Create a new rule called Stockpiles:

There exists Resources, with each type having a distinct name which is flavour text. Resources may also have a subtype, with subtypes of a Resource having distinct names with respect to the other subtypes of that resource. Resources of a given subtype have their name suffixed by that subtype’s name in brackets (e.g. “Food (Rations)” ). If a rule declares that a resource may be used for some purpose but does not specify subtype, then resources of that type with any subtype may be used for that purpose.

Each Baron has a publicly tracked Personal Resources Stockpile, which contains a list of Resources (defaulting to empty). A publicly tracked Resources Stockpile also exists which nominally belongs to the Demon King and which can be referred to as the Dungeon Stockpile. It contains a list of Resources (defaulting to empty). For ease of use, resources of the same type and subtype (if they have one) may be grouped together in stockpiles in the form “[Resource] x Y”, where Y is the number of copies of that resource that are being grouped together into that single list item.

Any time any number of Resources would be added to a Baron’s Stockpile, those resources are subject to Tax: one quarter of those resources (rounded up) and are instead added to the Dungeon Stockpile; the Baron chooses which of their newly gained resources are to be transferred into the Dungeon Stockpile. This Tax is applied collectively to all of the Resources gained by that Baron at that one time, rather than per type of Resource. If the Baron gains resources multiple times in a single atomic action, these gains are all considered to be simultaneous for the purposes of calculating the Tax.

Create a new rule called Labour:

Some actions are referred to as Labour Actions; these are all Atomic Actions that any Baron is able to perform, but the effect scales according to how long it is since their last Labour Action. The date and time that a Baron last performed a Labour Action is a publicly tracked value, and defaults to 23:59 on the 1st of September 2022 (representing that they have been accumulating Labour Actions since the start of the dynasty whether present or not).

When a Baron performs a Labour Action:
*If any Labour Actions have been performed that day by that Baron, or if they have performed any Labour Actions in the last 10 hours, then it is not legal to perform the action.
*Otherwise they gain the effect of that particular Labour Action once, and then gain it an additional time for every full 24 hours it has been since the midnight after the date and time they last performed a Labour Action (as per the tracked value).

I’m seeing this as one of the main mechanics of the dynasty. You earn resources by spending accumulated daily actions, and then spend those resources from your stockpile. Accumulating daily actions for weeks on end has the downside of not letting you split your efforts between multiple tasks however, so there’s some incentive to keep using your actions. As for the Dungeon Stockpile, I’ve got possible ideas for where the mechanic might go but I’m open to other ideas.

Comments

Trapdoorspyder: he/him

01-09-2022 16:04:17 UTC

I’d rather not have something in the ruleset that provides a possible incentive to check up on blognomic every 10 hours on the dot.

Habanero:

01-09-2022 16:07:44 UTC

Maybe it would be better to have the increasing effect of labour actions be continuous rather than going up in discrete steps? As it stands now, it’s optimal to perform a labour action every 10 hours, because you get one action every 10 hours and another every 24 hours after that.

SingularByte: he/him

01-09-2022 16:07:49 UTC

It’s matching the wording of Daily actions. If you do it every 10 hours, it’s illegal because you can’t do the action more than once a day.

Habanero:

01-09-2022 16:08:24 UTC

Ah never mind, missed the ‘that day’ bit.

SingularByte: he/him

01-09-2022 16:08:33 UTC

I’ll double check my maths on it is right, 2 mins.

Trapdoorspyder: he/him

01-09-2022 16:11:44 UTC

My bad, looks fine

SingularByte: he/him

01-09-2022 16:20:51 UTC

I might edit it for clarity though.

Trapdoorspyder: he/him

01-09-2022 18:54:05 UTC

Stockpiles do not appear to be publicly tracked

SingularByte: he/him

01-09-2022 18:56:36 UTC

Fixed

Trapdoorspyder: he/him

01-09-2022 20:10:58 UTC

for

thundershrike:

01-09-2022 20:24:34 UTC

for

Habanero:

01-09-2022 20:37:28 UTC

for

Brendan: he/him

01-09-2022 21:14:35 UTC

for

Bucky:

01-09-2022 23:14:22 UTC

for

Maldor: he/him

01-09-2022 23:31:25 UTC

for

Darknight: he/him

01-09-2022 23:35:45 UTC

for