Re: [spoon-discuss] Re:The Direct Approach.

[Bryan Donlan <bdonlan@xxxxxxxxx>]

On Thu, 1 Jul 2004 23:24:20 -0400, Daniel Lepage <dpl33@xxxxxxxxxxx> wrote:
> 
> 
> On Jul 1, 2004, at 7.18 PM, Araltaln wrote:
> 
> > My point is, while an automated system would work great for ruleset
> > changes, it would take a good deal of work to create one that would be
> > great for gamestate changes. Not, mind you, that at least having an
> > automated way to deal with the simple cases is a bad thing, but we
> > probably need to start with a method that has players in charge of
> > everything, and automate from there. Which, come to think of it, you
> > said anyway, bd. So I'm not sure what my point is, just that I have
> > one.
> 
> I was imagining something that would only automate changes to the
> ruleset itself; a proposal that required other actions would simply
> list them at the end, and the various ministers and duty-fillers would
> take care of it.
> So a prop might say:
[nip]
> AMEND r27 {{
> REPLACE {{ If a player's score equals or exceeds 1000 points, that
> player is immediately awarded a Win. }} {{ If a player possess 2.8?? or
> more, that player is immediately awarded a Win. }}
[snip]

The problem is, if you make one typo, or an extra space, or your mail
client wraps, it won't match. A unidiff sent to a web interface (or as
an attachment) would be better.

> And that would be the prop. The script would look at this, read in the
> REPEAL, CREATE, and AMEND blocks, performing the appropriate changes,
> and then would, say, send a message to the public forum listing the
> contents of all DO blocks from passed props; we'd then send a Roster
> Minister/Roster Duty-filler to tweak the scores and entropies, while
> somebody else reset the clock.

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