BlogNomic: The First Dynasty of Desertfrog

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>

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.

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

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

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.

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

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