- As long as we send the correct rotation quaternion to the client, the GAMEOBJECT_FACING must be set to 0
- GameObjectModel internal rotation matrices now take into account the rotation quaternion
* Fix "crash" by ".ticket accept" (unable to handled no args)
Fix .ticket info (ticket req Gamemaster+, info req Moderator+)
* Added comment on ".ticket accept"
* Added comment on ".ticket accept"
Rewrite Waypoint related commands (c2612)
Toggle the commands .wp add .wp modify and .wp show to be able to work with waypoints from creature_movement_template
Technical changes:
* Move Path Selection to WaypointManager
* Set visual waypoints to be summoned npcs
Remove .npc addmove command to add a waypoint. (c2619)
For this .wp add command is expected to be used
Remove unneeded functions from WaypointManager (c2620)
Waypoint Commands: Improve export command, remove import command (c2621)
* Also finally drop the wpguid columns from creature_movement[_template]
* Also remove all static spawns of id=1 (they are usually waypoints from the old system)
* Fix a minor bug in WaypointManager than can result in a crash if bad params are passed
Waypoint-Commands: Prefer current path's movement for handling (c2626)
WaypointMovement: Allow External sources to load waypoints (with different path ids) (c2627)
* Add SetExternalWaypointTable(..) function to ScriptMgr.h scope to be able to define from which table external waypoints are loaded
* Add AddWaypointFromExternal(..) function to ScriptMgr.h scope to load points into WaypointManager
* Expand MotionMaster::MoveWaypoint function to use source and pathId for specifying which path to load
* Expand MotionMaster::MoveWaypoint function to use some overwrite information for "entry".
This will be helpfull to have one path for mobs with different entry (ie ally/horde npcs with same behaviour)
* For externally loaded waypoints let CreatureAI::MovementInform have EXTERNAL_WAYPOINT_MOVE(256) + pathId as type.
This will allow an external user to know which of "his" paths is used
* Adapt the related commands a little bit such that parts of the commands will also be usable for external paths
At the moment .wp show and .wp export work with external paths.
WaypointMovement: Add support to set the next waypoint (c2635)
* Also add support to initialize a path with waittime before starting movement
* Add additional types for external use of MovementInform such that MovementInform is called when a waypoint is started, or when the last waypoint is handled
* Improve some minor technical issues
Let .wp add command start with 1 as first waypoint (c2640)
- Select a creature and type ".mmap path go" to move to that creature using generated path.
- Select a creature and type ".mmap path to_me" to see path from creature to your player char.
- You must be a GM to see these points.
