DB/Holidays: Difference between revisions
Jump to navigation
Jump to search
m (→12340) |
(→12340) |
||
Line 9: | Line 9: | ||
|0 || eventID || Integer || Reference to the Holiday eventID | |0 || eventID || Integer || Reference to the Holiday eventID | ||
|- | |- | ||
|1 || | |1 || duration || Integer[10] || Event preparation or main event (stage1) | ||
|- | |- | ||
|11 || | |11 || date || Integer[26] || Unixtime-style timestamp - origin date 01.01.2000 (OR only date (not year) if column12-> is 0) | ||
|- | |- | ||
| | |37 || Region || integer || | ||
|- | |- | ||
| | |38 || Looping || integer || | ||
|- | |- | ||
| | |39 || calendarFlags || integer || | ||
|- | |- | ||
| | |40 || eventName ||[[HolidayNames.dbc|iRefID]]|| Ref to [[Loc]] in HolidayNames.dbc | ||
|- | |- | ||
| | |41 || eventDescription||[[HolidayDescriptions.dbc|iRefID]]||Ref to [[Loc]] in HolidayDescriptions.dbc | ||
|- | |- | ||
| | |51 || textureFilename || String || Overlay used for ingame calendar event-decorations | ||
|- | |- | ||
| | |52 || priority || integer || | ||
|- | |- | ||
| | |53 || calendarFilterType || Integer || -1, 0, 1, 2 | ||
|- | |- | ||
|54 || flags || integer || | |||
|54 || | |||
|} | |} | ||
[[Category:DBC]] | [[Category:DBC]] |
Revision as of 19:11, 16 April 2011
12340
Column | Field | Type | Notes |
---|---|---|---|
0 | eventID | Integer | Reference to the Holiday eventID |
1 | duration | Integer[10] | Event preparation or main event (stage1) |
11 | date | Integer[26] | Unixtime-style timestamp - origin date 01.01.2000 (OR only date (not year) if column12-> is 0) |
37 | Region | integer | |
38 | Looping | integer | |
39 | calendarFlags | integer | |
40 | eventName | iRefID | Ref to Loc in HolidayNames.dbc |
41 | eventDescription | iRefID | Ref to Loc in HolidayDescriptions.dbc |
51 | textureFilename | String | Overlay used for ingame calendar event-decorations |
52 | priority | integer | |
53 | calendarFilterType | Integer | -1, 0, 1, 2 |
54 | flags | integer |
eventTimeType - 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 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)