First off, I’ve just-about completed the script to do the original “midnight updating”.  This proposal is in response to some people’s dissatisfaction with that.

Until a script is written and implemented to adjust user stats at a certain time based on a GNDT value, this proposal has no effect.  If such a script is not implemented within 10 days of this proposal’s passing, this proposal has no effect.

Strike “A Monk may often set eir Moves equal to twice eir Fitness.” from rule “Movement” if Proposal: Aha, attempt no. 2! is not enacted, else strike “Daily, at midnight UTC, a Monk’s moves shall automatically be set to twice eir Fitness.”

Replace with “At a time, specified by a Monk in UTC in the GNDT field ‘Update’, a Monk’s moves shall be automatically be set to twice eir Fitness.  The ‘Update’ field will be expressed as a two-digit 24 hour time.  For example, a value of ‘20’ would mean that Monk wishes eir moves to be reset at 8 PM UTC.”

Add a new column to the GNDT: “Update”.

If more than half of all comments containing counted votes also contain the text “No Example”, the italicised portion of the replacement (the example) will be stricken.

Like I said, I’m working on the midnight one, but the way i’ve got it set up, I can pretty easily keep track of the time, as well. (I LOVE Python.  string key to list containing moves and time.)  Also, as a note, this script is… “relatively” easy to modity to update other values that may change “often”, for instance, but thussofar it just does Moves based on Fitness.  Also, sorry if the formatting looks wonky.  The preview was looking weird.

BIG IMPORTANT QUESTION TO THOSE IN THE KNOW:  If an idle user is updated, the GNDT cgi ignores it, right?