Peter Cooper Jr. on Sun, 26 Nov 2006 10:18:01 -0700 (MST)

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [s-b] Back after a long absence...

"Mark Walsh" <flutesultan@xxxxxxxxxxxxx> writes:
> Most revered Administrator:
> Be advised that I find this posting to not be in accordance with the Rules.
> I'll delete inapplicable matters.
>> From: Bryan Donlan <bdonlan@xxxxxxxxx>
>> That is, my name shall be: all players
> As it turns out, this seems to me to not be a uniquely
> identifying name IAW Rule 1-4/0.
> It appears that Proposals/0009 contains the phrase
> {{
> ... all players ...
> }}
> connoted there to mean every current Player.
> Since the Game Document Proposition 0009 existed
> prior to the Request to Join by the Outsider once known
> in a previous ERA as 'bd', the name {{all players}} does
> not fulfill the requirements of 1-4/0: hence is invalid.

I certainly see your point, and I looked through the rules before
allowing it. But, "uniquely identifying" could be used to mean just
unique amongst current players (or all players?). And it's certainly
uniquely identifying amongst objects currently in the game. Proposals
just talk about changes that could happen to the game, but the mention
of a possible object in a proposal doesn't mean that it exists in the
game yet. So, I would think that "uniquely identifying" would have to
just refer to objects that currently exist, not objects that may exist
in the future.

And, just having a phrase talking about all players doesn't
necessarily mean that it refers to the player named "all players".

> This could create a prceedent by which a proposition's
> intent can be altered by a newcomer inadvertantly
> (or vertantly, for that matter). 

This could make for an interesting precedent, true. But if it starts
being a problem, we can make a prop or rule differently on a CFJ or
whatever. Changing things isn't a problem in this game. :)

Thanks for your input, but I think I'll stick with allowing it for

Peter C.
spoon-business mailing list