On Sun, 2019-03-03 at 05:16 +0000, James Cook wrote:
> On Sat, 2 Mar 2019 at 05:23, ais...@alumni.bham.ac.uk
> <ais...@alumni.bham.ac.uk> wrote:
> > That said, there is a possible failure state: if every player has at
> > least 13 Blots, and nobody has any Ribbons, the adoption of a proposal
> > within four weeks would require someone with fewer Blots than that to
> > register.
> Wouldn't the gamestate part of Rule 1698 ("If any other single
> change...") prevent that situation from arising? I agree it would be
> nice to close it off, but I don't see how it affects the ruleset
> ratification.

Indeed, but I thought I'd point it out so that people were aware.

In general, rule 1698 triggers should be avoided as much as possible.
The problem is that it (intentionally) defeats Agora's existing
mechanisms for ensuring that we know what the gamestate is; it's better
to have an unknown but playable gamestate, than a known but ossified
gamestate. However, when it does trigger, it can take a lot of effort
to figure out what the resulting gamestate is.

On another note, whose idea was it to put rule 1698 as the second rule
in the Ruleset? That was really clever, as it manages to serve as a
fundamental "protection of Agora" rule, and an explanation to new
players as to what the game is all about, at the same time.


Reply via email to