Proposal: Another Shot at This Class Thing
Self-killed. Failed by Kevan.
Adminned at 29 Sep 2012 03:59:32 UTC
This Proposal is a Correction. Citation here.
This Proposal contains
WhiteInk.
Enact a new rule called “Classes†with the following text:
A Class is a named list of Tasks possibly having Punishments or Rewards attached. Existing Classes are listed as a Sub Rule of this Rule, each Class occupying its own section bearing the Name of the Class.
A Student Performing a Class is referred to as the “Learner” in the Class’ text.
A Class shall have a Name that is different from all other Class’ names and doesn’t contain non-alphanumeric characters,
for the purpose of this paragraph, spaces are considered alphanumeric.
A Class may only be created by an enacted Proposal.
A Class shall specify requirements for its Storing, Clearing, Performing and Failure Conditions, as well as the Punishments that may trigger if the Class is failed, and/or the Rewards that may trigger if the class is Performed.
A Class may have up to 3 Tasks. Each Task specifies actions that shall be taken upon Performing the Task. When all tasks in a Class are performed, that Class is said to have been Performed.
A Class can be Cleared - unless otherwise specified by the Class’ text - by it’s Leaner when it’s Failed or Performed. Clearing a Class this way doesn’t effect it’s Punishments or Rewards.
This should fix the problems of the other Proposal.
For example, making Classes sub rules definitely makes them Gamestate; and, now, classes can only be created by Proposals.
I tried to “use white ink” in the text to give my changes some emphasis, but it messed it up, so I had to edit it for legibility reasons.
This seems a bit too similar to the existing Grading system, really.
IceFromHell:
The current formatation of the Ink “feature” is breaking the lines. Can someone with a better understanding of why that happens propose a change to that rule?
Thanks in advance.