Monday, April 06, 2020

Proposal: [Special Case] Busy Work

Self-killed. Failed by Kevan.

Adminned at 08 Apr 2020 15:12:03 UTC

Rewrite the introduction of Special Case so it reads:

Special Case Rules can be Active or Inactive. The status of a Special Case Rule is notated in the title of that rule ending in “[X]” where X is the word Active or Inactive, denoting that Rule’s status.

Special Case Rules have a Default Status, which can be Active or Inactive. The text of a Special Case Rule may state its Default Status; if it does not, its Default Status is Active.

When a new Dynasty is started, the Ascension Address may list any number of existing Special Case Rules to be set to a status other than their respective Default Status. All other Special Case Rules are set to their respective Default Status.

The text of a Special Case Rule that is Inactive is flavour text.

Something I’ve been meaning to do for a while, but finally got the kick to put into words.


Josh: HE/HIM

04-06-2020 15:49:25 UTC


Kevan: HE/HIM

04-06-2020 15:53:44 UTC

There’s an unintended flip here; if a Special Case rule is written as Default Inactive, and is Inactive, then at the start of the next dynasty we look at to see whether the “text of a Special Case Rule may state its Default Status; if it does not, its Default Status is Active” - it doesn’t state this (it’s only flavour text!), so it defaults to Active and wakes up.

Tantusar: HE/THEY

04-06-2020 15:54:44 UTC

it’s looking at the text not the rule itself

Tantusar: HE/THEY

04-06-2020 15:55:23 UTC

and we’ve established that the text of a rule is accessible to other parts of the rules even if it would be flavour text

Kevan: HE/HIM

04-06-2020 15:58:00 UTC

Flavour text “is not considered to have any meaning beyond being a string of characters” and “any statements that flavour text makes about gamestate are ignored”. The flavour text of an Inactive Special Case rule cannot “state its Default Status”.

Kevan: HE/HIM

04-06-2020 16:00:24 UTC

Ah, wait, your clause of “The text of a Special Case Rule may state its Default Status” is intended to allow the text to make one brief and specific statement, even if it’s flavour text?

Tantusar: HE/THEY

04-06-2020 16:02:01 UTC

that is the intention yes

pencilgame: HE/HIM

04-06-2020 17:29:32 UTC

Hmm….I agree that using flavor text to determine the active/inactive state of a rule is being a little loose with the rules. But what would be the way around this?

There would have to be a seperate always-active rule that stated the default status of all special case rules. You wouldn’t want that bit of information to get turned off when a special case was toggled.

Kevan: HE/HIM

04-06-2020 18:08:49 UTC

You could have an Ascension effect of “All other Special Case Rules are set to Active, and then set to their respective Default Status.” A bit clunky but I think better than having to resolve unusual precedence issues.

pencilgame: HE/HIM

04-06-2020 20:27:27 UTC

That would do the trick. But I think you could get rid of that last piece of clunk with something like this:

Upon the posting of an ascension address, unless otherwise noted, the special case rules return to the following states:
Seasonal Downtime ... Active
Dormancy ... Active
Simple Numbers ... Inactive


pencilgame: HE/HIM

04-06-2020 20:34:44 UTC

Agh, I don’t know. The more I think about it, the more they each have their own flavor of klunk.

Kevan: HE/HIM

04-07-2020 11:56:25 UTC

against On the grounds that this could be clearer about what it’s doing, and is non-urgent.

Darknight: HE/HIM

04-07-2020 14:29:06 UTC


Tantusar: HE/THEY

04-07-2020 14:55:58 UTC

against self-kill for rewrite