On 5/7/07, Ed Murphy <[EMAIL PROTECTED]> wrote:
This takes care of "what if no state is mentioned first?" (e.g. "the
values are the players"), but you should also state that null is a
possible state of any switch in this situation.
It would be simpler to delete ``possible''. A default state is a
state, so if the default state is null, then null is a state.
> Whenever a person registers, e becomes a player, and any
> switches attached to em due to eir being a player are
> automatically flipped to their default states.
This is already covered by "When a switch is created", except for
switches that were already attached before eir registration - so
"due to eir being a player" should be removed.
The intended function of ``attached'' here is as the head of an
adjectival phrase, not as part of an elliptical construction ``which
were attached...''. That is, I intend to refer to attachment as
timelessly as possible. I will have to think about how to reword
this.
I don't see why any switches not relevant to playerhood need to be
reset when a person becomes a player. This language was actually
intended to be redundant in some cases, to avoid uncomfortable
questions about whether engra^H^H^H^H^Hplayer switches get created and
attached to a person when e first becomes a player (and not on
subsequent reregistrations).
> Amend rule 1871 (Turns for All) to read:
What are your thoughts on "The Standing Court"?
Is that the sitting, standing, lying down proposal? My rewrite of
rule 1871 is not an attempt to counteract it, if that's what you mean.
I included a rewrite of this rule because my first version of
"Switches reborn" did and the rule still exists.
--
C. Maud Image (Michael Slone)
That's scary.
-- The Goddess Eris, in agora-discussion
