DB/Holidays
Jump to navigation
Jump to search
3.3.5a 12340
Column | Field | Type | Notes |
---|---|---|---|
0 | eventID | Integer | Reference to the Holiday eventID |
1 | stage1duration | Integer[10] | Event preparation or main event (stage1) |
2 | stage2duration | Integer[10] | stage2 event timer, see schedulerType below (stage2) |
11 | date | Integer[26] | Unixtime-style timestamp - origin date 01.01.2000 (OR only date (not year) if column12-> is 0) |
37 | Region | integer | (THIS NEEDS MORE RESEARCH -click) |
38 | Looping | integer | (THIS NEEDS MORE RESEARCH -click) |
39 | calendarFlags | integer | (THIS NEEDS MORE RESEARCH -click) |
40 | eventName | iRefID | Ref to Loc in HolidayNames.dbc (THIS NEEDS MORE RESEARCH -click) |
41 | eventDescription | iRefID | Ref to Loc in HolidayDescriptions.dbc |
49 | calendarIconRefId | ??? | (THIS NEEDS MORE RESEARCH -click) |
50 | calendarBackgroundRefID | ??? | (THIS NEEDS MORE RESEARCH -click) |
51 | textureFilename | String | Overlay used for ingame calendar event-decorations |
52 | priority | integer | (THIS NEEDS MORE RESEARCH -click) |
53 | schedulerType | Integer | -1, 0, 1, 2 |
54 | flags | integer | (THIS NEEDS MORE RESEARCH -click) |
schedulerType defines what kind of timer is used for 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 every year based on column11, column12 etc dates - lengt and event stages handled by length given in column1 and column2 (adjusted in DBC to keep it in line with **yearly** changes) - if column12=0, use DATE only from field11 0: event repeats every 7 days, with a duration of <eventTimer1> hours (hardcoded startdate serverside depending on eventID) 1: event repeats based on column11, column12 etc values (see -1) - if eventTimer2 exists do eventTimer1 as event prestage, start eventTimer2 at once as it's timed out 2: event repeats every X hours (with eventTimer2 being the eventPause/eventWait timer)