Saturday, December 23, 2017

Proposal: Combo Rework

Self-killed. Failed by Kevan.

Adminned at 28 Dec 2017 11:53:26 UTC

Rename “Combos” to “Proclamation” and replace its ruletext with the following:

A Failed Experiment can perform actions and have their effects applied to the gamestate via making a Proclamation post for this purpose, which is a blog post with [Proclamation] in the title.

A Proclamation has two parts:
* Description: This is an explanation of the actions taken, in clear and unambiguous natural language.
* Gamestate Changes: This is a statement of the gamestate before and after the actions performed in the Proclamation. This section tracks the gamestate about these changes in particular.

If any actions in such a Proclamation requires a die roll or other random event that is visible to the public, Failed Experiments must make all those rolls in the same GNDT comment before posting the Proclamation, along the string “[Proclamation]” at the start. This is a Proclamation Roll Comment until its associated Proclamation has been posted. A Failed Experiment with a Proclamation Roll Comment cannot perform any action besides posting its associated Proclamation (and the actions consequently made via it).

A step upwards from that previous combo suggestion, which seems to be going well.

A bit less wordcount than Combo and lets you make those complicated posts in better ways, and clears out ambiguity about how these “via-proxy” actions are made in regards to the gamestate.

Comments

Kevan: he/him

27-12-2017 11:42:10 UTC

Why do we need “This section tracks the gamestate about these changes in particular.” here? Why not track it in the places it’s usually tracked?

“cannot perform any action besides” should also be restricted to dynastic actions, for safety’s sake. Seems like a useful first step towards solving the ignored-roll dice problem in general.

Kevan: he/him

27-12-2017 11:51:32 UTC

against for now, will hold off on processing the queue while people wake up.

Madrid:

27-12-2017 18:30:58 UTC

against Queueboosting. We’re back up, yes?