Friday, February 09, 2024

Proposal: Clock Cycle Rate

Enacted 4-0. Josh

Adminned at 11 Feb 2024 19:01:29 UTC

Add to the end of the first paragraph of the Mainframe, if it is not already present:

Wherever the Mainframe would refer to an Agent by name in places where gamestate is publicly tracked, the Mainframe should instead use their IP address.

Make the “Ping” and “Change Passcode” shell commands subrules of “Shell Commands” called “Ping” and “Change Passcode”, respectively. Then a new rule called “Clock Cycle”:

As a daily action, the Mainframe should perform the following atomic action called Clock Cycle:
* Resolve all Shell Commands initiated since the last clock cycle.
* Post a newsletter on the blog.

Add a subrule to Clock Cycle called “Newsletter”:

A ‘’‘newsletter” is a story post by the Mainframe whose title is in the format “Newsletter

“. A newsletter post always contains:
* A ranked list of Agents, sorted by reputation (not including the reputation itself)
* A list of new clients created since the last clock cycle.
* The number of shell commands resolved in the last clock cycle.

The remaining contents of the newsletter are flavour text.

This type of gameplay loop has worked for the past few dynasties so I think we can still get back on track.


Josh: he/they

10-02-2024 12:24:52 UTC



10-02-2024 13:14:45 UTC


JonathanDark: Publisher he/him

10-02-2024 20:32:45 UTC