Tabelle: 'waypoint_data'
The `waypoint_data` tableThis table contains all the path data for creatures that use waypoints. Field | Type | Attributes | Key | Null | Default | Extra | Comment |
---|
id | int(10) | vorzeichenlos | | NO | 0 | | Creature GUID | point | mediumint(8) | vorzeichenlos | | nein | 0 | | | position_x | float | vorzeichenbehaftet | | nein | 0 | | | position_y | float | vorzeichenbehaftet | | nein | 0 | | | position_z | float | vorzeichenbehaftet | | nein | 0 | | | orientation | float | vorzeichenbehaftet | | nein | 0 | | | delay | int(10) | vorzeichenlos | | nein | 0 | | | move_type | tinyint(1) | vorzeichenbehaftet | | nein | 0 | | | action | int(11) | vorzeichenbehaftet | | NO | 0 | | | action_chance | smallint(3) | vorzeichenbehaftet | | nein | 100 | | | wpguid | int(11) | vorzeichenbehaftet | | nein | 0 | | |
Description of the fieldsidID of the path The TDB standard way of assigning an ID is to multiply GUID of the creature by 10. So for a creature with a GUID of 1234 the path ID would be 12340. Any waypoints submitted to TDB should follow this standard. However, this is only a suggestion when creating your own waypoints. This ID can be anything you want as long as creature_addon.path_id is set to the ID you pick here for the creature you are creating a waypoint for. pointID of point of path positionX, Y and Z coordinates of destination orientationThe orientation of the creature. (North = 0.0; South = pi (3.14159)) delayTime (in ms) between each point move_type0 - walk 1 - run actionID of the action in the waypoint_scripts table that is to be performed. action_chanceAction chance in percents (0-100%) wpguidThis field is used by the core and is NOT to be set by hand. This field holds the GUID of the waypoint visual when you enable the visual mode for waypoints.
|