DB/Holidays
Jump to navigation
Jump to search
3.3.5a 12340
Column | Field | Type | Notes | Events with flag |
---|---|---|---|---|
0 | eventID | Integer | Reference to the Holiday eventID | |
1 | eventStage1Duration | Integer | stage1 event length (either preparation or main event, see eventSchedulerType for more info) | |
2 | eventStage2Duration | Integer | stage2 event length (starts stage2 directly after stage1 is completed, see eventSchedulerType for more info) | |
11 | eventDate | Integer | packed blizzdate (NOTE: Epoch date is 01.01.2000 00:00, and only the day/month is used if column12-> is 0) | |
37 | Region | integer | (??? schlumpf added this - needs more research -click) | |
38 | Looping | integer | (??? schlumpf added this - needs more research - only valid for Call To Arms events... -click) |
283 - Call to Arms: Alterac Valley 284 - Call to Arms: Warsong Gulch 285 - Call to Arms: Arathi Basin 353 - Call to Arms: Eye of the Storm 400 - Call to Arms: Strand of the Ancient 420 - Call to Arms: Isle of Conquest |
39 | calendarFlags | integer | (??? schlumpf added this - needs more research --click) | |
40 | eventName | iRefID | Ref to Loc in HolidayNames.dbc (??? schlumpf added this, needs more research -click) | |
41 | eventDescription | iRefID | Ref to Loc in HolidayDescriptions.dbc (??? schlumpf added this, needs more research -click) | |
49 | eventCalendarName | iRefID | Ref to Loc in HolidayNames.dbc | |
50 | eventCalendarDescription | iRefID | Ref to Loc in HolidayDescriptions.dbc | |
51 | eventCalendarOverlay | String | Overlay texture used for ingame calendar event-decorations | |
52 | priority | Integer | (??? schlumpf added this, needs more research -click) | |
53 | eventSchedulerType | Integer | -1: yearly, 0:weekly, 1:???, 2:repeated | |
54 | eventFlags | Integer | (??? schlumpf added this, needs more research -click) |
eventSchedulerType 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 - length and possible event stages is calculated by the information from 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)