Game event SF

From Project Skyfire
Jump to: navigation, search

Back to world database list of tables.


The `game_event` table

This table is contains definitions for all game events that are activated or deactivated automatically by the Game Event System in the core.

Structure

Field Type Attributes Key Null Default Extra Comment
eventEntry tinyint(3) unsigned PRI NO Unique Entry of the game event
start_time timestamp signed NO 0000-00-00 00:00:00 Absolute start date, the event will never start before
end_time timestamp signed NO 0000-00-00 00:00:00 Absolute end date, the event will never start after
occurence bigint(20) unsigned NO 5184000 Delay in minutes between occurences of the event
length bigint(20) unsigned NO 2592000 Length in minutes of the event
holiday mediumint(8) unsigned NO 0 Client side holiday id
description varchar(255) signed YES NULL Description of the event displayed in console
world_event tinyint(3) unsigned NO 0 0 if normal event, 1 if world event


Description of the fields

eventEntry

Entry of the event. Keep it as low as possible and prevent making holes in the list. Higher the max id is, the more memory will be used to store the event data.

start_time

Absolute start date of the event. The event will start occurring only if the local time at the server is after the one set here.

end_time

Absolute end date of the event. The event will stop occurring if the local time at the server is after the one set here.

occurence

Number of minutes between 2 occurrences of the event. (2880 = 2 days, 1440 = 1 day, etc)

length

Number of minutes the event will last after the start of the occurrence. (2880 = 2 days, 1440 = 1 day, etc) This value must be lower than occurrence one or the event will never stop.

holiday

Holiday ID from Holiday.dbc. This is sent to the client to update the calender.

description

String containing the name of the event displayed in console each time it starts or stops.

world_event

This is a boolean field that determines if this game event is a world event or not. 0 = normal event, 1 = world event. For the world event to work, you need to at a minimum, populate game_event_condition and game_event_quest_condition.