Monday, April 14, 2025

Proposal: Overwatch

Reached quorum 7 votes to 0. Enacted by Kevan.

Adminned at 15 Apr 2025 12:39:08 UTC

Add a subrule to “Shadow Ruleset” called “Stopwatches”:-

Each Guard has a Stopwatch, being a piece of flavour text (tracked privately by the Concierge) which is either blank or the name of a proposal. A Guard may set their Stopwatch as a virtual action. If a Guard has a Stopwatch set which names a pending proposal, then the Concierge may not perform the Patrol Assessment action.

If a Guard includes a comment on a dynastic proposal consisting of the single word “PIVOTAL”, then that proposal is a Pivotal one. A Pivotal Proposal may not be enacted by Agents (or idle Agents) who are not the Concierge. The Concierge should not enact a Pivotal Proposal if there are unresolved virtual actions.

Under the proposed Shadow Ruleset system, if we’re in the Setting Patrols phase and there are consecutive proposals of “Guards Move Faster” and “Burglars Move Faster” in the queue, the Guards will very much want the Phase to change after the first enacts, but before the second does.

Rather than have that depend on the timing of when the last Guard submits a Route and when I’m able to process it, this allows any Guard to delay in advance the earliest queue point at which I’m able to perform the phase-change action, and to publicly put the later proposal on hold so that it can’t be enacted before I have a chance to change the phase.

Comments

JonathanDark: he/him

14-04-2025 14:20:07 UTC

Shouldn’t the Stopwatch only affect a dynastic proposal and not any proposal? I guess it doesn’t matter that much, but if the idea is prevent timing issues with resolving proposals, then non-dynastic proposals shouldn’t matter.

SingularByte: he/him

14-04-2025 19:25:47 UTC

for  but I’m in favour of the suggestion of core proposals getting a free pass.

JonathanDark: he/him

14-04-2025 21:09:17 UTC

for and we can fix later

ais523:

14-04-2025 21:29:23 UTC

for

DoomedIdeas: he/him

15-04-2025 01:43:17 UTC

for

qenya: she/they

15-04-2025 08:23:22 UTC

for

qenya: she/they

15-04-2025 08:23:58 UTC

(I’m not sure the fix is necessary anyway; it seems to me that obstructing a core proposal for gameplay purposes would fall under Fair Play?)

qenya: she/they

15-04-2025 08:33:18 UTC

(I guess it’s wise to tighten it up as much as possible anyway, though.)

Kevan: Concierge he/him

15-04-2025 08:48:17 UTC

I think JonathanDark’s fix is just saying that because it wouldn’t make much sense for a Guard to Stopwatch a pure Core proposal (to say “don’t process Patrol Assessment until after this enacts”), we should disallow it. It’s not impossible for some core amendment to be relevant to gameplay, though.

Allowing core proposals to be Pivotal isn’t being suggested here, if that’s what you mean by “obstructing a core proposal”. They maybe should be, though, by the same logic of their being possibly relevant to gameplay (and certainly there’s a cheap tactic of adding “and amend one word of Core” to stop a proposal from being Pivoted). I can’t see that there’d be any Fair Play breach in any of that.

DoomedIdeas: he/him

15-04-2025 09:51:51 UTC

for

Darknight: he/him

15-04-2025 11:03:14 UTC

for

Josh: he/they

15-04-2025 12:18:52 UTC

for