Re: [spoon-discuss] Re: [Spoon-business] The Roster

[SkArcher <SkArcher@xxxxxxxxxxxxxxxxx>]

On Tue, 25 Nov 2003 14:51:22 -0500, Daniel Lepage <dpl33@xxxxxxxxxxx> 
wrote:



> > B.1.Entries for Players must show the Players Name, eir Dimensions and 
> > a list of any other attributes >> associated with em.
> You might want to specify 'public' attributes - I don't think we have 
> any secret attributes right now, > but we might at some point.

Prop that when we need it, it hasn't be necessary so far, as Rule 24 
stands, and I'd prefer not to put a loose end into the rules

> > {{
> > The Roster Duty.
> > The Roster Duty shall Require Attention at the begining of the nweek, 
> > if there
>
> So we won't keep a running total of players' scores?

A running total of the players score exists, as it were, in potentia. The 
Roster as it is is only updated a few times per nweek as it is. Maybe it 
would be worth making this Duty require attention every checkpoint if 
there had been any changes, but I was wary of running hard into the 'A 
player may not perform a Duty which e has performed in the last 2 nweeks' 
clause, you see.
> > has been any change made to the information that should be noted on The 
> > Roster in the preceeding nweek. It is the responsibility of the Player 
> > carrying out
> > The Roster Duty to ammend The Roster so that it shows the correct 
> > information
>                        ^ the word 'ammend' needs one fewer m.

I request that the admin rectify my poor spelling.

> At some point the Generic Nomic Data Tracker was brought up (see 
> http://kevan.org/generic ); a system like that might be the best, rather 
> than simply using a Wiki, as it better allows people to log the reasons 
> for the changes and whatnot (so that we don't have one person updating 
> the Wiki to give a player the 20 points e just got, then another player 
> doing it again without realizing the points have already been added)

As I understand it the Wiki will prevent edits that are too close together 
anyway, but certainly this program creates a webpage and so would be fine 
for the purpose.

> > comments, questions, nitpicks? Oh, it needs keywords, but i'll sort 
> > that tomorrow when I can track down exactly what keywords it needs in 
> > Wonkos new system (suggestions will be accepted, hint hint).
>
> Hmmmm... some things are harder to categorize...
>
> I'd suggest that 24 get Objects:Roster, Duties:Roster, Objects:Players, 
> Objects:Societies, maybe? I dunno - does this seem like something you'd 
> want to see if you looked up players or societies? Maybe not...
>
> How about: (Objects:Roster, Duties:Roster, Gameplay:Reporting:Roster) ?
>
> If we're planning on seriously remodeling the ruleset, though, I may 
> just wait until we've done so and then go through and propose new 
> keywords for whatever we have left.

I was hoping to shift a fair few things over to Duty status instead of 
Ministerial status, Duties are a lot more flexible.


SKArcher
--
 
_______________________________________________
spoon-discuss mailing list
spoon-discuss@xxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/spoon-discuss