Thursday, February 25, 2010

Proposal: Why the last part of rule 3.2.1 is a bad idea

Times out 13-2 -Darth

Adminned at 27 Feb 2010 10:15:05 UTC

In the Glossary, replace

No action may be taken which would require setting a gamestate variable to an illegal value.

with

A Guest who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action’s effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one of those values to an illegal value.

If the keyword “Guest” has been replaced by a different keyword since this proposal was created, then change “Guest” in the replacement to whatever the keyword “Guest” was replaced with.

Consider the following rules from the ruleset:

No action may be taken which would require setting a gamestate variable to an illegal value.

If four Guests have become Arrested during the course of the game, further Guests may not become Arrested.

The Executor shall change the state of any Murderers currently in the Manor to “Arrested”, and the Guest who made the phonecall achieves victory.

It’s sheer luck here that no more than 4 Guests ended up Arrested during the course of the game. Otherwise, flurie’s email to Kevan would have caused Kevan to change a further Guest’s status to Arrested, which would be an illegal value. As a result, flurie’s email itself would have been illegal, rather than winning the game. This is a ridiculous concept; arguably the dynastic rules are broken, but I think it’s more likely that the Glossary is broken as it keeps on encouraging this sort of stupid situation.

Really, something needs to be done about this rule before someone scams it. The intent of the rule is presumably to prevent people doing purchase-type actions, like spending Money to buy Armour, or whatever, that would bring a value out of its normal range; by restricting the scope of this rule to GNDT-trade-type actions, I think it’s likely to have the intended effect in the situation it was intended to cover, without breaking situations it wasn’t. (The restriction to dynastic-defined actions is probably redundant here, but is added as a separate safety measure; did you know that the old version of this rule can even prevent CFJs enacting?)

Comments

Klisz:

25-02-2010 18:24:45 UTC

for

Oze:

25-02-2010 18:40:40 UTC

for

Kevan: City he/him

25-02-2010 18:59:23 UTC

for

Purplebeard:

25-02-2010 19:00:10 UTC

imperial

Anonyman:

25-02-2010 19:24:56 UTC

for

Keba:

25-02-2010 19:26:17 UTC

for

Qwazukee:

25-02-2010 20:24:22 UTC

against I think it is more that the Dynastic Rules are broken. Also, I think “variable” covers more possibilities than “value.”

Roujo: he/him

26-02-2010 00:44:23 UTC

for Good fix. But… Is “variable” defined in the ruleset?

redtara: they/them

26-02-2010 01:03:43 UTC

for

Put:

26-02-2010 11:26:17 UTC

imperial

tecslicer:

26-02-2010 19:14:54 UTC

for

Excalabur:

27-02-2010 01:31:02 UTC

against

Darknight: he/him

27-02-2010 04:40:12 UTC

can we veto this?

Darknight: he/him

27-02-2010 04:42:49 UTC

ACK! Lol, didn’t remember that it doesn’t change a dynastic rule. my bad. and since it seems like i never voted to begin with imperial

NoOneImportant:

27-02-2010 09:47:21 UTC

imperial