I did a little poking around the source, and discovered there is actually an
eqtime.h &
eqtime.cpp. The header doesn't really help, but I did find this:
eqtime.cpp
Code:
138 bool EQTime::saveFile(const char *filename)
139 {
140 ofstream of;
141 of.open(filename);
142 if(!of)
143 {
144 LogFile->write(EQEMuLog::Error, "EQTime::saveFile failed: Unable to open file '%s'", filename);
145 return false;
146 }
147 //Enable for debugging
148 //cout << "SAVE: day=" << (long)eqTime.start_eqtime.day << ";hour=" << (long)eqTime.start_eqtime.hour << ";min=" << (long)eqTime.start_eqtime.minute << ";mon=" << (long)eqTime.start_eqtime.month << ";yr=" << eqTime.start_eqtime.year << ";timet=" << eqTime.start_realtime << endl;
149 of << EQT_VERSION << endl;
150 of << (long)eqTime.start_eqtime.day << endl;
151 of << (long)eqTime.start_eqtime.hour << endl;
152 of << (long)eqTime.start_eqtime.minute << endl;
153 of << (long)eqTime.start_eqtime.month << endl;
154 of << eqTime.start_eqtime.year << endl;
155 of << eqTime.start_realtime << endl;
156 of.close();
157 return true;
158 }
In short, this is the format of the eqtime.cfg file:
Code:
EQTime Version (should be 1000)
Day
Hour
Minute
Month
Year
Actual Time (Unix timestamp)
Actually, after diving into the forums, I actually found
this post:
Quote:
Originally Posted by fathernitwit
Quick EQ time tutorial:
Code:
/* The minutes range from 0 - 59 */
// The hours range from 1-24
// 1 = 1am
// 2 = 2am
// ...
// 23 = 11 pm
// 24 = 12 am
// The days range from 1-28
// The months range from 1-12
//year is just a number
format of eqtime.cfg:
Code:
version(1000)
day
hour
minute
month
year
unix_time
|
I did notice a few odd things with the time while seeing if all of the zones (which are all currently dynamic) keep the same time. I started out in cabeast, and the time was showing Sunday, January 01, 3100 - 9AM (9:35 am according to #time). I then zoned to tutorial and the time showed Friday, November 06, 3102 - 8PM (8:34 pm according to #time). When I zoned back to cabeast, the time corresponded with what I was seeing in cabeast, and same when I zoned back to tutorial. I'm not really sure what the deal is, but it seems like the zones are seeing the correct time.
I wonder if this means instead of
using quest to handle spawn changes for different times of the day, if the
spawn_events table in the DB can actually be used.