This shouldn't take long.

This next group of variables is the Date & Time Variables. There's not really that many, and it annoys me that this is going to be a short page. 

Be that as it may, here's a bit of formatting info. If you've played around with both the main date variables, and the ones generated with WolfScript, you may have noticed that the main variables are all "zero padded", that is, if the month is Jan through Sept, they will be 01 to 09. In contrast, WolfScript is simply the single digit by itself. Thus was the nature of the beast when I found it, and leave it to avoid breaking scripts which rely on this formatting behavior.

A good guess on keeping the Furcadia Time synchronized. Once the parser loads the Furcadia Time variables, it checks the state of the FURCADIATIME flag, and if true, and it's a minute passing into the next, the function adds 1 to the minute, and if surpasses 59, is reset to 0. At which point the hour is updated. If the hour runs past 23, it's reset to 0. If you're going to rely on Furcadia Time for many things, it would probably be best if you also included a timer that regularly fetched the time from the server to maintain a more accurate server time over my internal function. Not that my function is bad, just better to do it like that. It's not something which needs to run very often, once a day may be enough, depends on how bad your clock is compared to a perfect world.