Re: [werewolf] Werewolf coding

[Ted Rathkopf <ted-pbmserv-lists@rathkopf.net>]

Meanwhile, back at the model home, Mark Ballinger <mballinger@ballinger.cx> said:

>> -dayend NNNN
>> -nightend NNNN
>>
>>   The day/night ends at NN:NN.  Since there isn't a timer
>>   mechanism, I plan on having it just checked with each incoming mail.
>
> Yes, but that raises a point.  You will need to give yourself the
> ability to end a round or even the game on any random chat coming
> in.  We want to avoid making a bunch of spaghetti in there, so
> perhaps the front-end of the code needs to be rewritten so we don't
> just jump off to "sub Chat" and be done with it.  (I realize I'm not
> being very clear here, but bear with me.)  Geoff suggested that we
> also queue up messages going out in some way, so we can send out
> that incoming chat but also build in "oh by the way, the day ended."

How about adding a PreProcess call in Run?  Or do we want it to be a
PostProcess so that if someone has just sent in a vote, it gets
handled before we check for time limits?


>>   DISCUSS: Should their be a minimum day/night length?  Perhaps 1/2 of
>>   the difference between the day and night end?  We don't want a night
>>   phase to end by action immediately before the dayend time, and have
>>   a day triggered immediately, and vice versa.
>
> That's good.  I think the day/night times should be number of hours
> rather than a time, though.

I don't.  :)  I don't like the idea of a deadline that creeps.
Especially because it would invariably work it's way around so that
the majority of the voting window is during the night.

>> Moot Queue messages.
>
> Yes, if you mean something like "Thanks for queueing, but it's just
> not your night."

No.  I meant "You queued markball for tonight, but he's been lynched.
Please reselect."


-- 
Ted Rathkopf