DB/Holidays
Jump to navigation
Jump to search
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 - origin date 01.01.2000 |
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 | overlayName | String | Overlay used for ingame calendar event-decorations |
53 | periodType | Integer | -1, 0, 1, 2 |
periodType - defines what kind of timer the event uses, and when the event is to stop, start etc. - and if it uses different stages during it's "buildup"-phase (2 stages available) :
-1: event repeats based on field11, field12 etc values, adjusted in DBC to keep it in line with yearly changes) - if field12=0, use DATE only from field11 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: event repeats every X hours (with stage2Timer being the eventPause time)