DB/Holidays: Difference between revisions
Jump to navigation
Jump to search
m (→9183) |
m (→9183) |
||
Line 9: | Line 9: | ||
|0 || eventID || Integer || Not complettely sure - most likely will be | |0 || eventID || Integer || Not complettely sure - most likely will be | ||
|- | |- | ||
|1 || | |1 || eventTimer1 || Integer || Event preparation or main event (stage1) | ||
|- | |- | ||
|2 || | |2 || eventTimer2 || Integer || Event stage2 or waitperiod untill next stage1 run | ||
|- | |- | ||
|11 || eventStart || Integer || Unixtime-style timestamp - origin date 01.01.2000 | |11 || eventStart || Integer || Unixtime-style timestamp - origin date 01.01.2000 | ||
Line 19: | Line 19: | ||
|24 - 36 || <unknown> || Integer || <Unknown> | |24 - 36 || <unknown> || Integer || <Unknown> | ||
|- | |- | ||
|49 || | |49 || eventName ||[[HolidayNames.dbc|iRefID]]|| Ref to [[Loc]] in HolidayNames.dbc | ||
|- | |- | ||
|50 || | |50 || eventDescription||[[HolidayDescriptions.dbc|iRefID]]||Ref to [[Loc]] in HolidayDescriptions.dbc | ||
|- | |- | ||
|51 || | |51 || eventOverlay || String || Overlay used for ingame calendar event-decorations | ||
|- | |- | ||
|53 || | |53 || eventTimeType || Integer || -1, 0, 1, 2 | ||
|- | |- | ||
|} | |} |
Revision as of 00:47, 19 October 2010
9183
Column | Field | Type | Notes |
---|---|---|---|
0 | eventID | Integer | Not complettely sure - most likely will be |
1 | eventTimer1 | Integer | Event preparation or main event (stage1) |
2 | eventTimer2 | Integer | Event stage2 or waitperiod untill next stage1 run |
11 | eventStart | Integer | Unixtime-style timestamp - origin date 01.01.2000 |
12 - 23 | eventReoccuranceTimes | Integer | Adjusted eventdates for certain events where needed |
24 - 36 | <unknown> | Integer | <Unknown> |
49 | eventName | iRefID | Ref to Loc in HolidayNames.dbc |
50 | eventDescription | iRefID | Ref to Loc in HolidayDescriptions.dbc |
51 | eventOverlay | String | Overlay used for ingame calendar event-decorations |
53 | eventTimeType | Integer | -1, 0, 1, 2 |
periodType - 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 based on field11, field12 etc values, adjusted in DBC to keep it in line with yearly changes) - if field12=0, use DATE only from field11 0: event repeats every 7 days, with a duration of <stage1Timer> hours (hardcoded startdate serverside depending on eventID) 1: event repeats based on field11, field12 etc values (see -1) - if stage2 exists do stage1 as event prestage, start stage2 at once as it's timed out 2: event repeats every X hours (with stage2Timer being the eventPause time)