[s-b] [auto] Peter submits p216

[automailer@xxxxxxxxxxxxxxx]

Peter has submitted a new Motion, p216.

---------------------------------
Motion 216/0: Changing A Rule Regarding Operating Time
A Proposal by Peter
Last modified on nweek 95, nday 6

[[Acronym: CARROT]]

[[Issues that this tries to solve:

When something says that someone has "2 ndays", it's not really clear to me whether that means at the end of the second nday from now, or at this moment of the day 2 ndays from now, and whether or not to count the current nday, and so on. Similarly, talking about something happening in "1 nweek" doesn't make it very clear whether it's at the start or the end of the nweek, or the end of the same nday of the next nweek, or what. I've kind of dealt with it based on what seemed to be game precedent, but I want to make it clear.

Also, I don't see a reason to delay actions while the Clock is Off. It seems like the rules have to handle all sorts of exceptions because of it, and the changes (for instance, at the end of an nweek) have already happened at that point, even if the displays don't reflect it. So why not allow them?

This makes it clear that things that happen at the end of one nday occur before all things that happen at the beginning of the next nday.

We don't really need wweeks, and so a game object for just tracking just wdays is superflous.

And well, like Wonko, I also like to rewrite the rules from time to time. :)
]]

Change the text of rule 3-1 in its entirety to be
{{
=== Definition ===
There is a Game Object known as The Clock. The Clock consists of the following values:
 * A positive integer known as the nweek
 * A positive integer known as the nday
 * A state of being Off or On
 * A nonnegative integer known as the ndelay

=== Clock Changes ===
At midnight (00:00:00) Coordinated Universal Time (UTC), if the Clock is On, then the nday is incremented by 1. Otherwise, the ndelay is incremented by 1. [[An online UTC clock is available at http://www.time.gov/.]]

If the nday would be set to a value greater than 12, instead it is set to 1, and the nweek is incremented by 1.

The Clock may not be changed from On to Off or from Off to On except in ways explicitly permitted by the rules. When the Clock is turned On, the ndelay is set to zero.

=== Durations ===
A duration to the effect of "X ndays", where X is a number, shall be interpreted to mean that the duration ends at the end of the nday after X consecutive changes of that value. [[Thus, if it is currently the middle of nday 2, something happening "in 2 ndays" will occur at the end of nday 4.]]

A duration to the effect of "X ndelays", where X is a number, shall be interpreted to mean that the duration ends at the end of the ndelay after X consecutive changes of that value. The resetting of an ndelay to 0 from the Clock being turned On does not count as a change for the purposes of this paragraph.

A duration to the effect of "X nweeks", where X is a number, shall be interpreted to mean that the duration ends at the end of the nday when the nday is the same value, but the nweek is increased by X.

=== Nyears ===
A period of 10 nweeks is known as an nyear. Hence, the first 10 nweeks (1-10 on the Clock) comprise nyear 1, the second (11-20 on the Clock) comprise nyear 2, and so on.

=== Starts and ends of nday ===
All events occurring at the end of an nday occur before all events occurring at the beginning of the next nday.
}}

In rule 4-1, in the "Entering a Ministry" section, change the text
{{
two wdays after the Referendum becomes Open, it becomes Historical.
}}
to
{{
two ndelays after the Referendum becomes Open, or two ndays after the Referendum becomes Open, whichever comes first, it becomes Historical.
}}
---------------------------------



This Message was sent automatically by the Wiki.
 Please do not reply to the sender of this message, as your replies will be ignored. Thank you.
_______________________________________________
spoon-business mailing list
spoon-business@xxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/spoon-business