DB/Holidays: Difference between revisions

From wowdev
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 9: Line 9:
|0  || eventID  || Integer  || Reference to the Holiday eventID
|0  || eventID  || Integer  || Reference to the Holiday eventID
|-  
|-  
|1  || stage1duration || Integer[10]  || stage1 event timer (preparation or main event, depends on schedulerType)
|1  || eventStage1Duration || Integer || stage1 event timer (preparation or main event, depends on schedulerType)
|-
|-
|2  || stage2duration || Integer[10]  || stage2 event timer (main event if schedulerTypee is  
|2  || eventStage2duration || Integer || stage2 event timer (main event if schedulerType is 2) - starts stage2 X hours after stage1 (see eventSchedulerType)
|-
|-
|11 || date || Integer[26] || Unixtime-style timestamp - origin date 01.01.2000 (OR only date (not year) if column12-> is 0)
|11 || eventDate || Integer || Unixtime-style timestamp - unixtime-like, epoch date is 01.01.2000 00:00 (uses only date (not year) if column12-> is 0)
|-
|-
|37  || Region || integer || (THIS NEEDS MORE RESEARCH -click)
|37  || Region || integer || (schlumpf, care to elaborate on this ? -click)
|-
|-
|38  || Looping || integer || (THIS NEEDS MORE RESEARCH -click)
|38  || Looping || integer || (schlumpf, care to elaborate on this ? -click)
|-
|-
|39  || calendarFlags || integer || (THIS NEEDS MORE RESEARCH -click)
|39  || calendarFlags || integer || (schlumpf, care to elaborate on this ? -click)
|-
|-
|40  || eventName ||[[HolidayNames.dbc|iRefID]]|| Ref to [[Loc]] in HolidayNames.dbc (THIS NEEDS MORE RESEARCH -click)
|40  || eventName || [[HolidayNames.dbc|iRefID]] || Ref to [[Loc]] in HolidayNames.dbc (this is field 49 for me -click)
|-
|-
|41  || eventDescription||[[HolidayDescriptions.dbc|iRefID]]||Ref to [[Loc]] in HolidayDescriptions.dbc (THIS NEEDS MORE RESEARCH -click)
|41  || eventDescription|| [[HolidayDescriptions.dbc|iRefID]] || Ref to [[Loc]] in HolidayDescriptions.dbc (this is field 50 for me -click)
|-
|-
|49 || holidayNameRefId || ??? || (THIS NEEDS MORE RESEARCH -click)
|49 || eventNameRefId || [[HolidayNames.dbc|iRefID]] || Ref to [[Loc]] in HolidayNames.dbc
|-
|-
|50 || holidayDescriptionRefID || ??? || (THIS NEEDS MORE RESEARCH -click)
|50 || eventDescriptionRefId || [[HolidayDescriptions.dbc|iRefID]] || Ref to [[Loc]] in HolidayDescriptions.dbc
|-
|-
|51  || textureFilename || String || Overlay used for ingame calendar event-decorations  
|51  || calendarTextureFilename || String || Overlay used for ingame calendar event-decorations  
|-
|-
|52  || priority || integer || (THIS NEEDS MORE RESEARCH -click)
|52  || priority || integer || (schlumpf, care to elaborate on this ? -click)
|-
|-
|53  || schedulerType|| Integer || -1, 0, 1, 2
|53  || eventSchedulerType|| Integer || -1, 0, 1, 2
|-
|-
|54  || flags || integer || (THIS NEEDS MORE RESEARCH -click)
|54  || flags || integer || (schlumpf, care to elaborate on this ? -click)
|}
|}
[[Category:DBC]][[Category:DBC_WotLK]]
[[Category:DBC]][[Category:DBC_WotLK]]
'''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)
'''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 - lengt and event stages handled by length given in column1 and column2
   -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
       (adjusted in DBC to keep it in line with **yearly** changes) - if column12=0, use DATE only from field11

Revision as of 06:42, 15 February 2013

3.3.5a 12340

Column Field Type Notes
0 eventID Integer Reference to the Holiday eventID
1 eventStage1Duration Integer stage1 event timer (preparation or main event, depends on schedulerType)
2 eventStage2duration Integer stage2 event timer (main event if schedulerType is 2) - starts stage2 X hours after stage1 (see eventSchedulerType)
11 eventDate Integer Unixtime-style timestamp - unixtime-like, epoch date is 01.01.2000 00:00 (uses only date (not year) if column12-> is 0)
37 Region integer (schlumpf, care to elaborate on this ? -click)
38 Looping integer (schlumpf, care to elaborate on this ? -click)
39 calendarFlags integer (schlumpf, care to elaborate on this ? -click)
40 eventName iRefID Ref to Loc in HolidayNames.dbc (this is field 49 for me -click)
41 eventDescription iRefID Ref to Loc in HolidayDescriptions.dbc (this is field 50 for me -click)
49 eventNameRefId iRefID Ref to Loc in HolidayNames.dbc
50 eventDescriptionRefId iRefID Ref to Loc in HolidayDescriptions.dbc
51 calendarTextureFilename String Overlay used for ingame calendar event-decorations
52 priority integer (schlumpf, care to elaborate on this ? -click)
53 eventSchedulerType Integer -1, 0, 1, 2
54 flags integer (schlumpf, care to elaborate on this ? -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 - 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)