Friday, July 14, 2023

Proposal: Economic Links

Timed out and enacted 8-0. Josh

Adminned at 17 Jul 2023 08:40:48 UTC

Add the following steps to the end of the list of steps for the Passing Time atomic action in the rule “Time’s Passage”:

* Give each Machinist one of the Resource corresponding to the Megasystem they inhabit.
* If any Megasystem is Destroyed, set all its ACTIVE Facilites’ statuses to DORMANT.
* Set all remaining ACTIVE Facilities’ status to STANDBY.

If the proposal “Power Dynamics” is not enacted, remove the following text from the rule “The Great Machine’s Structure”:

As a daily action called Moving, a Machinist may change which Megasystem they’re inhabiting.

If the proposal “Power Dynamics” is not enacted, add the following text to the rule “Subsystems”:

As a daily action called Moving, a Machinist may either change which Megasystem they’re inhabiting or Activate a STANDBY Facility in their current Megasystem.

If the Proposal “Power Dynamics” is enacted, add the following text to the end of the rule “Subsystems”:

A Machinist who Moves may not subsequently Operate until the next instance of Passing Time, and vice versa.

Step 1: Basic resource injection
Step 3: Working facilities activated up to once per Passing Time
Step 2: Destroyed Megasystem’s running facilities still function. Once.

Comments

JonathanDark: he/him

14-07-2023 17:41:41 UTC

This could result in a Facility being ACTIVE less than 24 hours, for example if a Machinist performs a dynastic action that sets it to ACTIVE just minutes before the Great Machine performs Passing Time.

I’m sure the argument will be to simply set the Facility to ACTIVE earlier, but that might not be an option depending on the time zone of the Machinist vs the time zone of the Great Machine.

My suggestion is to name an undefined dynastic action, like “Activate”, that sets a STANDBY Facility to ACTIVE in the Passing Time action. Something like this:

<blockqoute>* Give each Machinist one of the Resource corresponding to the Megasystem they inhabit.
* If any Megasystem is Destroyed, set all its ACTIVE Facilites’ statuses to DORMANT.
* Set each STANDBY Facility to ACTIVE if a Machinist has performed the Activate action on that Facility
* Set all remaining ACTIVE Facilities’ status to STANDBY, excluding the ones affected by the preceding step
</blockquote>

Bucky:

14-07-2023 17:55:16 UTC

My idea of how facilities should function is that, when they become ACTIVE, the activator immediately processes their effects. Or else they have their effects when deactivated during Passing Time. I prefer the former to the latter to minimize the load on Lemon.

They shouldn’t have a passive effect only while continuously active, although they might while non-dormant.

In other words, combining this with the vague action drafting system I’d mentioned in the commentary for the Facilities proposal, DORMANT means it can’t be drafted this round, STANDBY means it’s available but hasn’t been drafted yet this round, and ACTIVE means it’s already drafted and the corresponding action taken. But there’s not enough character count to spell out the drafting, merely the round boundary reset.

JonathanDark: he/him

14-07-2023 18:58:01 UTC

Ah, ok, I see you where you’re going. That probably works better with the Proposal “Power Dynamics” anyway.

Bucky:

14-07-2023 19:18:45 UTC

I reread Power Dynamics and added some contingent changes to avoid duplication of functionality with Activate/Operate.

lemon: she/her

15-07-2023 00:22:48 UTC

i see — so rather than active being a signifier of ready-to-use, as intended in Power Dynamics, you would rather have Active status be a signifier that a facility has already been used and can’t be used again until it returns to Standby status? i don’t hate that, honestly. i’d be happy with this rule or the Power Dynamics rules, although i think having both would be a bit akward.

for if both this and Power Dynamics pass, i’ll propose a cleanup proposal that merges their mechanics a little bit better.

Lulu: she/her

15-07-2023 01:02:44 UTC

for

JonathanDark: he/him

15-07-2023 02:24:19 UTC

for

SingularByte: he/him

15-07-2023 05:07:30 UTC

for

Kevan: City he/him

15-07-2023 10:11:14 UTC

for

Raven1207: he/they

15-07-2023 17:04:36 UTC

for

JonathanDark: he/him

17-07-2023 06:27:56 UTC

This one’s been Popular for some time now, even before Maldor idled.

Josh: he/they

17-07-2023 08:40:00 UTC

imperial