Wednesday, September 19, 2012

Proposal: SCH What should I do with my time?

Self-killed. Failed by Kevan.

Adminned at 21 Sep 2012 02:14:56 UTC

Enact a new rule called “SCH Schedule” with the following text:

Each Student has a Schedule, tracked in the GNDT in a column called SCH.  A Schedule has a default of ” , , , , “. The Classes are stored in the GNDT via the Schedule.  Each classes’ name is written in order in Schedule, separated by a comma.  A blank designates that there is no Class in that spot.  Removing a class means replacing the class with a space in the GNDT. A Class’ name may not have a comma in it.  A Schedule can only contain classes.

A Schedule can only be modified during Open Registration or Super-Secret Registration.  A Schedule cannot be modified at any other time.

Open Registration occurs every week on Sunday, and at no other time.
Super-Secret Registration occurs on an individual basis.  A Student, upon becoming a Student, gains access to Super-Secret Registration.  It lasts for exactly 1 day (or 86400 seconds), starting the moment he becomes a student.  Super-Secret Registration may occur at other times, but only as dictated by other rules.

During both Registrations, a Student may change his Schedule by accessing the GNDT, using the storage method listed above.  For each day he may choose 1 Class out of the Class List, storing it on the day of his choosing.  He may choose to remove a Class by replacing the name with a space in the GNDT.  A Student may both remove a Class and store a different Class in the same spot.  A Student may remove/store a class during the allotted time as many times as he desires.

A Class is a list of at least 1 Task, and at most 3 Tasks.  It may also contain Punishment(s) attached to one or multiple Tasks. A class can be created, deleted, stored, removed, or performed.  Creating and deleting refer to the Class in the Class List, while storing and removing refer to the Class in the Schedule.  Performing a class refers to performing the Tasks of the Class.

The first Class, if it exists, shall be performed on Monday, and no other day. The second Class, if it exists, shall be performed on Tuesday, and no other day. The third Class, if it exists, shall be performed on Wednesday, and no other day. The fourth, if it exists, Class shall be performed on Thursday, and no other day. The fifth Class, if it exists, shall be performed on Friday, and no other day. 

If the Class’ Task is not performed on the day the Class is to be performed AND the Task has a punishment attached, the punishment is performed.

The Class List is a list of Classes that all players can store as described above, except for Classes that explicitly define who can store them.  If a Class is created, it is simultaneously added to the Class List.  If a Class is deleted, it is simultaneously removed from the Class List.

Modification of the Selfkilled Proposed SCH Schedule
http://blognomic.com/blognomic/archive/sch_where_is_my_schedule/
I’m writing up rules to dictate ways to create Classes.

Comments

quirck: he/him

20-09-2012 08:39:54 UTC

What about players who might occasionally skip a day or two? What about those who can’t log in on Sundays? Who performs punishment? Where is the Class List stored?..

Tee:

20-09-2012 13:45:30 UTC

Class List is not stored anywhere, it is just a compendium of Classes (You write the classes down, but not the Class List).
For players who can’t login…they shouldn’t fill that day with a class.
Punishments can be dealt out by anyone if the conditions are met (I ‘m not sure how to define that, though)
And, good reasoning on Sunday.  It should be Saturday and Sunday.

Tee:

20-09-2012 14:06:49 UTC

And, potentially, there could be a class that creates a Super-Secret Registration.

quirck: he/him

20-09-2012 15:24:12 UTC

Still I’d like to have Class List written out explicitly somewhere, because the wording “create a class if it doesn’t already exist” in a newly created rule is somewhat tricky. Where does the class exist? Where should it be created? In the Class List in our minds? :)
I’d suggest to write in the rule something like all classes are listed in the subrules, then the Class List is a set of subrules, and creating a class becomes creating of a subrule, and “unless it already exists” clause becomes not a rule text but a proposal text.

Clucky: he/him

20-09-2012 18:56:01 UTC

imperial

IceFromHell:

20-09-2012 23:41:52 UTC

against  per quirck.
But I’m in favor of this if corrected.

Tee:

21-09-2012 01:47:21 UTC

against
Self killing yet again.