tbaMUD Continued development of the CircleMUD core

Hello there.
My MUD is in a futuristic setting. Stock tbamud has time set at the year ~620.
The question is, will something explode if I just put something like
> time_info.year += 2000;
in time_reset function? Or shouldn't I even do that, just change ACMD(do_time) function?
Heh, guess I answered my own question. But still, isn't there a better way to handle dates on tbamud? I don't really understand how t_time works to be honest.
Cheers!

The original CircleMUD developers picked the original MUD time. No idea why. But it is saved in the lib/etc/time file and can be modified. Now I'm not sure of the equation it uses to generate that number, but you can change that number to change the MUD time. I'm guessing it is in seconds from some initial time. TBA's time is: 675255741 and that is year 561.

From db.c: beginning_of_time = 650336715;

I think a good case could be made to add MUD time into the system preference OLC menu. Additionally, MUD time could read/write from the system preference file instead of the existing time file in lib. In my opinion it seems a more appropriate way to handle time while keeping the data directory nice and tidy.

hey, are people allowed to come into your mud to look around? I'm a big fan of futuristic circle/tbamuds.

let me know!

I agree, though a few years back I tried to figure out how to set the time in seconds to a specific date. I failed, if someone else would like to tackle this feel free. If I remember correctly the problem was that they based the start time off something arbitrary that I never figured out.

Wasn't it related to player age (starting at 17?). I did some tweaking with this once. I'll take another look at it when I get back home. Had to go out of town and forgot to keep my remote login server on :|