Tuesday, December 01, 2020

Proposal: Start the clock

Timed out and enacted, 6-0. Josh

Adminned at 03 Dec 2020 21:22:19 UTC

I’m the ruleset, replace the string “An individual DEVA is known as a Bogey, and has statistics” with “A DEVA has statistics”.

Add a new rule to the ruleset, called The Future Is Already Written:

A DEVA becomes a Bogey when it enters the game. All Bogeys are publicly tracked.

The Poindexter is responsible for privately scheduling and tracking, and then publicly or secretly (as appropriate) carrying out, the actions of all DEVAs. For each DEVA, the Poindexter should secretly keep a chronological list of planned actions and when they will occur. To whatever extent is possible, the Poindexter must generate and maintain any necessary information to map out the generation and actions of any DEVA for at least the next week. If a DEVA’s planned actions do not cover the full period of the next week then the Poindexter should randomly generate new actions for it until the full period of the next week is scheduled with actions.

Subrules to this rule detail actions that the DEVAs may take, how they are generated and how information about them is tracked.

All scheduled actions for a DEVA must include a specific date or time at which they will come into effect. Planned DEVA actions should be enacted by the Poindexter as close to that date or time as possible. If the specific time is missed then the Poindexter should carry it out at their first opportunity thereafter.

If a DEVA’s scheduled action can’t legally take place for any reason (such as an invalid target) then it is stunned and all subsequent actions on its schedule are delayed for 48 hours.

Add a subrule to that rule, called Emerging from the Breach:

When Poindexter has created a new DEVA, the first item on its schedule should be Emerging from the Breach. Emerging from the Breach may not be selected as an action for a Bogey. When a DEVA carried out an Emerging from the Breach action, they enter the game, become a Bogey, and become publicly tracked. A DEVA should Emerge from the Breach at a secretly randomly selected time between 24 and 120 hours after it has been created.

The date and time upon which the next new Bogey will Emerge from the Breach is publicly tracked information.

Add a further subrule to the rule called The Future Is Already Written, called Attack a Civilian Target:

When attacking a civilian target is added to a DEVA’s schedule, it must be scheduled to take place between 2 and 72 hours after the action on that schedule that takes place immediately before it. Whenever a Bogey’s attack on a civilian target is enacted, Poindexter must make a blog post informing the Pilots that the attack has taken place.

Add a further subrule to the rule called The Future Is Already Written, called Attack a Military Target:

When attacking a military target is added to a DEVA’s schedule, a Jockeying Pilot must be secretly randomly selected as its target, and it must be scheduled to take place between 48 and 96 hours after the action on that schedule that takes place immediately before it. Whenever a Bogey’s attack on a military target is enacted, Poindexter must make a blog post informing the Pilots that the attack has taken place and the Attack value of the Bogey who carried it out, which then becomes publicly tracked information. The targeted Pilot then loses Power equal to the Attack of the Bogey minus their own Defence.

Kicking the wheels on this a bit. I’m sure there’s a more elegant way of phrasing it, but the gist is: all of your enemies have their next week’s worth of actions invariably planned out. They won’t deviate from their plan but you can disrupt them.

Comments

Coderblaze:

01-12-2020 16:17:42 UTC

I think you meant to put “Whenever a Bogey’s attack on a Jockeying Pilot is enacted” in the military target rules. Currently as written whenever a civilian attack happens then a pilot also gets attacked also? In addition: You might need to add a clause to the military target for if the pilot is no longer Jockeying. (e.g. target no longer is legal)

Bucky:

01-12-2020 16:21:47 UTC

“Replace the string” should mention that it’s replacing the string in a rule and not e.g. in this proposal.

Josh: he/they

01-12-2020 16:54:28 UTC

Thanks both, updates made.

@Coderblaze The last para of the first time should cover failure states.

Kevan: City he/him

01-12-2020 17:00:09 UTC

Hmm, would maybe pad out “If a DEVA’s scheduled action can’t take place for any reason” to mean what you say - is the intention that it’s only when an scheduled action becomes impossible, rather than when you’re asleep and can’t immediately perform it?

Josh: he/they

01-12-2020 17:04:01 UTC

The para before should cover my missing time slots. But I should tighten the language; thanks for the feedback.

Kevan: City he/him

01-12-2020 18:10:47 UTC

for

robotabc773: he/him

01-12-2020 18:29:09 UTC

for

Coderblaze:

01-12-2020 18:43:17 UTC

for

pokes:

01-12-2020 20:56:33 UTC

for

Raven1207: he/they

01-12-2020 20:58:08 UTC

for