DB/Holidays: Difference between revisions
Jump to navigation
Jump to search
m (→9183) |
m (→9183) |
||
Line 35: | Line 35: | ||
0: event repeats every 7 days, with a duration of <stage1Timer> hours (hardcoded startdate serverside depending on eventID) | 0: event repeats every 7 days, with a duration of <stage1Timer> hours (hardcoded startdate serverside depending on eventID) | ||
1: event stage2 exists : do stage1, start stage2 at once as it's timed out | 1: event stage2 exists : do stage1, start stage2 at once as it's timed out | ||
2: wait X hours untill next occurance (with | 2: wait X hours untill next occurance (with stage2Timer being the eventPause time) |
Revision as of 00:10, 19 October 2010
9183
Column | Field | Type | Notes |
---|---|---|---|
0 | eventID | Integer | Not complettely sure - most likely will be |
1 | stage1Timer | Integer | Event preparation or main event (stage1) |
2 | stage2Timer | Integer | Event stage2 or waitperiod untill next stage1 run |
11 | eventStart | Integer | Unixtime-style timestamp with WotLK startdate as origin date, or just simply day/month pickup. |
12 - 23 | eventReoccuranceTimes | Integer | Adjusted eventdates for certain events where needed |
24 - 36 | <unknown> | Integer | <Unknown> |
49 | Holidayname | iRefID | Ref to Loc in HolidayNames.dbc |
50 | Holidaydescription | iRefID | Ref to Loc in HolidayDescriptions.dbc |
51 | Calendarname | String | If the Holiday is part of the Calendar its name is written here |
52 | periodAdjustment (?) | Integer | Adjustment for reoccurance-timers (+/- the amount of "periodTypes" |
53 | periodType | Integer | -1, 0, 1, 2 |
periodType - defines if the event is to wait, pause, stop, start etc., and if it uses different stages(?) :
-1: <currently unknown> 0: event repeats every 7 days, with a duration of <stage1Timer> hours (hardcoded startdate serverside depending on eventID) 1: event stage2 exists : do stage1, start stage2 at once as it's timed out 2: wait X hours untill next occurance (with stage2Timer being the eventPause time)