Each Student has a Schedule, tracked in the GNDT in a column called SCH. A Schedule is made up of 5 Slots, separated by commas. The default Slot is a space, and therefore, the default Schedule is ” , , , , ” . Each Slot may either have a space or a Class name in it. Storing a Class means replacing a Slot’s contents with the name of the Class. Clearing a Class means replacing the Slot with the Class’ name with a space in the GNDT. A Classâ€™ name may not have a comma in it. A Schedule can contain multiple Slots with the same Class’ name.
A Schedule can only be modified during Open Registration or Super-Secret Registration. A Schedule cannot be modified at any other time.
Every Student gains access to Open Registration every week on Sunday and Saturday, and at no other time.
Students gain access to Super-Secret Registration on an individual basis. A Student, upon becoming a Student, gains access to Super-Secret Registration. It lasts for exactly 2 days (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.
If a student has access to either Registration, that Student may change his Schedule by choosing 1 Class written in Class List, and storing it in his Schedule in the GNDT in the Slot of his choosing. He may choose to clear a Class by replacing its name with a space in his Schedule in the GNDT. A Student may both clear a Class and store a different Class in the same spot. A Student may clear/store a Class as many times as he desires, as long as he still has access to either Registration.
A Class has a name, and contains at most 3 Tasks. It can also contain Punishment(s) attached to one or multiple Tasks. It can also contain requirements for how it is to be stored, cleared, or performed. A Class cannot have the same name as any other Class.
A Class can be created, deleted, stored, cleared, or performed.
To create a Class, it is added the Wiki page “Class List” by writing its name in quotation marks, followed by an open brace. It is followed by the requirements for storing, clearing, and performing, if they exist. It then describes each of the Tasks with the phrase “Task #: TASK” replacing # with the Task number (1, 2, or 3), and replacing TASK with the Task to be performed when the Class is performed. Each Task with a Punishment is immediately followed with the phrase “Punishment for Task #: PUNISH” replacing # with the Task number (1, 2 or 3), and PUNISH with the Punishment to be performed when the Task is not. Finally, it is followed by a close brace. Class’ Tasks and Punishments are generally written in 2nd person form, with “You”, “Your”, “Yours” referring to the Student who has the Class stored.
To delete a Class, it is removed from the Wiki page “Class List”, including its name, the brackets immediately below it, and anything inside of the brackets.
Performing a Class refers to performing the Tasks of the Class. The Class in the first Slot of Schedule, if it exists, shall be performed by the owner of the Schedule on Monday, and no other day. The Class in the second Slot of Schedule, if it exists, shall be performed by the owner of the Schedule on Tuesday, and no other day. The Class in the third Slot of Schedule, if it exists, shall be performed by the owner of the Schedule on Wednesday, and no other day. The Class in the fourth Slot of Schedule, if it exists, shall be performed by the owner of the Schedule on Thursday, and no other day. The Class in the fifth Slot of Schedule, if it exists, shall be performed by the owner of the Schedule 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 may be performed once by any one Student the day after the Class was supposed to be performed. This is the only way a punishment may be performed. A Class may only be stored in a Schedule if the requirements of storing are fulfilled, and if it is written in the Wiki page “Class List”. A Class may only be performed if the requirements of performing are fulfilled. A Class may only be removed out of a Schedule if the requirements of removing are fulfilled. A Class, Task, or Punishment cannot directly modify Projects or Scored, declare Victory, or declare any Victory conditions.
Modification of the self-killed Proposal:
Added Class Lists to be stored to the Wiki.
Added requirements for the creation of Classes. Allowed empty classes (still must be named).
Clarified terms, and changed it so the same terms are used universally. Made it look better, and easier to read.
These classes have the potential to be stored by people other than the owner of the schedule.
I couldn’t figure out a good, bulletproof set of Classes to create new Classes, so for now, it will remain by proposal.
Third time’s the charm.