DB/Holidays: Difference between revisions

From wowdev
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 1: Line 1:
==3.3.5a 12340==
==3.3.5a 12340==
{| style="background:#FCFCFC; color:black"
{| style="background:#f3f3f3; color:black; border: 1px dashed;"
|-  
|-  
! width="80" | Column  
! width="70" | Column  
! width="180 " | Field  
! width="200" | Field  
! width="80" | Type  
! width="70" | Type  
! width="600" | Notes
! width="700" | Notes
|-  
|-  
|0  || eventID  || Integer || Reference to the Holiday eventID
|0  || eventID  || Integer || Reference to the Holiday eventID
|-  
|-  
|1  || eventStage1Duration || Integer || stage1 event timer (preparation or main event, depends on schedulerType)
|1  || eventStage1Duration || Integer || stage1 event length (either preparation or main event, see eventSchedulerType for more info)
|-
|-
|2  || eventStage2Duration || Integer || stage2 event timer (main event if schedulerType is 2) - starts stage2 X hours after stage1 (see eventSchedulerType)
|2  || eventStage2Duration || Integer || stage2 event length (start stage2 in stage1+X hours, see eventSchedulerType for more info)
|-
|-
|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)
|11 || eventDate || Integer || packed blizzdate (NOTE: Epoch date is 01.01.2000 00:00, and only the day/month (not the year) is used if column12-> is 0)
|-
|-
|37 || Region || integer || (schlumpf, care to elaborate on this ? -click)
|37 || Region || integer || (??? schlumpf added this - needs more research -click)
|-
|-
|38 || Looping || integer || (schlumpf, care to elaborate on this ? -click)
|38 || Looping || integer || (??? schlumpf added this - needs more research -click)
|-
|-
|39 || calendarFlags || integer || (schlumpf, care to elaborate on this ? -click)
|39 || calendarFlags || integer || (??? schlumpf added this - needs more research - only valid for Call To Arms events... -click)
|-
|-
|40 || eventName || [[HolidayNames.dbc|iRefID]] || Ref to [[Loc]] in HolidayNames.dbc (this is field 49 for me -click)
|40 || eventName || [[HolidayNames.dbc|iRefID]] || Ref to [[Loc]] in HolidayNames.dbc (??? schlumpf added this, needs more research -click)
|-
|-
|41 || eventDescription|| [[HolidayDescriptions.dbc|iRefID]] || Ref to [[Loc]] in HolidayDescriptions.dbc (this is field 50 for me -click)
|41 || eventDescription|| [[HolidayDescriptions.dbc|iRefID]] || Ref to [[Loc]] in HolidayDescriptions.dbc (??? schlumpf added this, needs more research -click)
|-
|-
|49 || eventName || [[HolidayNames.dbc|iRefID]] || Ref to [[Loc]] in HolidayNames.dbc
|49 || eventCalendarName || [[HolidayNames.dbc|iRefID]] || Ref to [[Loc]] in HolidayNames.dbc
|-
|-
|50 || eventDescription || [[HolidayDescriptions.dbc|iRefID]] || Ref to [[Loc]] in HolidayDescriptions.dbc
|50 || eventCalendarDescription || [[HolidayDescriptions.dbc|iRefID]] || Ref to [[Loc]] in HolidayDescriptions.dbc
|-
|-
|51 || calendarTextureFilename || String || Overlay used for ingame calendar event-decorations  
|51 || eventCalendarOverlay || String || Overlay texture used for ingame calendar event-decorations
|-
|-
|52 || priority || integer || (schlumpf, care to elaborate on this ? -click)
|52 || priority || Integer || (??? schlumpf added this, needs more research -click)
|-
|-
|53 || eventSchedulerType|| Integer || -1, 0, 1, 2
|53 || eventSchedulerType|| Integer || -1: yearly, 0:weekly, 1:???, 2:repeated
|-
|-
|54 || flags || integer || (schlumpf, care to elaborate on this ? -click)
|54 || eventFlags || Integer || (??? schlumpf added this, needs more research -click)
|}
|}
[[Category:DBC]][[Category:DBC_WotLK]]
[[Category:DBC]][[Category:DBC_WotLK]]
'''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)
'''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 - 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
       (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)
   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
   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)
   2: event repeats every X hours (with eventTimer2 being the eventPause/eventWait timer)

Revision as of 06:36, 15 February 2013

3.3.5a 12340

Column Field Type Notes
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 (start stage2 in stage1+X hours, see eventSchedulerType for more info)
11 eventDate Integer packed blizzdate (NOTE: Epoch date is 01.01.2000 00:00, and only the day/month (not the year) 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 -click)
39 calendarFlags integer (??? schlumpf added this - needs more research - only valid for Call To Arms events... -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)