mirror of
https://github.com/TrinityCore/TrinityCore.git
synced 2026-02-14 05:59:29 +01:00
correct movement packet broadcasting
mover should be source of movement packets, not player resolves problem that movements of controlled unit not visible for nearby players (you can detect it only when controlled unit too far from player-controller) --HG-- branch : trunk
This commit is contained in:
@@ -1656,6 +1656,12 @@ void WorldObject::SendMessageToSetInRange(WorldPacket *data, float dist, bool /*
|
||||
VisitNearbyWorldObject(dist, notifier);
|
||||
}
|
||||
|
||||
void WorldObject::SendMessageToSet(WorldPacket *data, Player const* skipped_rcvr)
|
||||
{
|
||||
Trinity::MessageDistDeliverer notifier(this, data, GetMap()->GetVisibilityDistance(), false, skipped_rcvr);
|
||||
VisitNearbyWorldObject(GetMap()->GetVisibilityDistance(), notifier);
|
||||
}
|
||||
|
||||
void WorldObject::SendObjectDeSpawnAnim(uint64 guid)
|
||||
{
|
||||
WorldPacket data(SMSG_GAMEOBJECT_DESPAWN_ANIM, 8);
|
||||
|
||||
Reference in New Issue
Block a user