Friday, April 09, 2021

Proposal: Adopted Variables [Appendix]

Fewer than quorum not voting against, 2-5. Failed by pokes.

Adminned at 10 Apr 2021 19:23:29 UTC

In the rule Orphan Variables, add the following to the beginning of the second paragraph:

If the Special Case rule Dynastic Tracking is active, any otherwise Orphan Variable may be considered to be publicly tracked. Otherwise,

Comments

Kevan: he/him

09-04-2021 12:39:08 UTC

Is there any danger of this revealing private player stats, if we declare them carelessly, or if other variables which are calculated from them aren’t declared as private?

Looking at the ruleset, a player’s Hand may actually be an orphan variable right now - under the current Orphan rule we’d be forced to fix that; under the public-by-default, I’d instead be required to reveal all active players’ current Hands.

lemon: she/her

09-04-2021 12:45:06 UTC

all something needs to keep from being an orphan variable is to have a place where it’s tracked, right? i’d say that player’s hands are tracked in PMs– but i guess the ruleset doesn’t *specify* that’s where they’re tracked, does it, and that’s also a stipulation

huh

Josh: he/they

09-04-2021 12:50:04 UTC

I think that neither outcome is ideal, but that no solution is fully ideal, as they’re all catches for an imperfect set of circumstances; this deals with the issue in a neater way than the status quo.

I’m not sure that the Hands example is ideal as I don’t think that they’re an orphan variable, on the grounds that they are privately tracked (“Privately inform both Participants of their Hand” establishes that there is a documentary record of the hands being generated and distributed). But I do take the point that privately tracked info can be improperly set out in the ruleset, and this creates a risk. The mitigation to it is that, because such info would be privately held, it can’t just be spilled by fiat; the entity holding it can chose to hold onto it until a CfJ passes, if they wish.

Kevan: he/him

09-04-2021 13:02:29 UTC

Where’s that choice coming from - that it “may be considered to be publicly tracked”, and that if the information holder personally declines that consideration (even if some players would very much want “identity of the Werewolf” to be considered to be publicly tracked), it isn’t?

Josh: he/they

09-04-2021 13:16:58 UTC

CfJs.

There’s a reason why this bolts on to Orphan Variables - because that language is currently in place, has been tested, and hasn’t caused any major controversies.

The rule change here doesn’t really change anything - your “Werewolf identities are public!” litigant is just a “Werewolves can’t do anything as their status is an orphan variable!” litigant under the status quo.

Kevan: he/him

09-04-2021 13:48:35 UTC

Werewolves wanting to do something when they can’t is easily CfJable; Werewolves wanting to be anonymous when the ruleset requires their identities to be tracked publicly is not.

I think that’s the only problem here: secret information can’t go back in the bottle, so we should be careful about automatically requiring anything to be publicly tracked. If auto-tracked Orphan Variables are boring basically-public stuff (“the order that the Emperor received private messages”) then we can yawn and wave it through on a CfJ; if they include secret information (“the order that the Emperor received attack messages from Werewolves”), then an invested, late-game, by-the-book-scam player has a strong cause for insisting that the Emperor reveal that information.

Lulu: she/her

09-04-2021 15:22:14 UTC

for

Raven1207: he/they

10-04-2021 00:32:28 UTC

for

Kevan: he/him

10-04-2021 07:30:01 UTC

against As above: shouldn’t default to publicly tracking all poorly-described game data, when that will sometimes be privately-tracked information like Werewolf identities or hands of cards.

Darknight: he/him

10-04-2021 14:38:11 UTC

against

Lulu: she/her

10-04-2021 15:34:14 UTC

against cov

Clucky: he/him

10-04-2021 19:19:03 UTC

against

pokes:

10-04-2021 19:22:58 UTC

against