Time after time. in Design Philosophy
|
|
There's really two questions here... one practical, one aesthetic.
I've never really done much with anything aside from world.time, and although I've done some fancy things with that, when I get HRH up permanently, I want to make time proceed on the basis of one real-life week (168 hours) == one game season, regardless of server outs, down time, etc. As of now, there's no night or day system, but I may add a system that formally tracks days as two hour intervals. The main thing I'm looking for is a way to check and see if, in reality according to the host computer, it's (for example) Friday at midnight, and if so, move the seasons along one.
Now, the aesthetic point... following the one week == one season formula, when should I make the change: Friday or Sunday would seem to be the most obvious choices, but actually, I'm aiming at making 9:00 to 11:00 CST or so Friday night be day 42 of each 84-day season, marking it in game with an announcement "It is now Seasonheight!", but that would actually make the season change in the middle of the day Tuesday. Of course, there's advantages to having the season change at a time where it's almost guaranteed the server would be empty.
Anyways, any thoughts on either matter?
|
Have an HTML document. Every 10-50 ticks (doesn't have to be very often) update it with the current time and date (or the time and date on seperate files). I forget the HTML tag for this, but I'm looking it up. Then, run a text parser through it, and you can access your computer's time through BYOND.