mirror of
https://github.com/Kelsidavis/WoWee.git
synced 2026-03-22 23:30:14 +00:00
net: ack SMSG_MOVE_SET/UNSET_CAN_TRANSITION_SWIM_FLY and SMSG_MOVE_SET_COLLISION_HGT
These three server-push opcodes were silently consumed without sending the required client acks, causing the server to stall waiting for confirmation before granting the capability. - SMSG_MOVE_SET_CAN_TRANSITION_BETWEEN_SWIM_AND_FLY → CMSG_MOVE_SET_CAN_TRANSITION_BETWEEN_SWIM_AND_FLY_ACK (via handleForceMoveFlagChange) - SMSG_MOVE_UNSET_CAN_TRANSITION_BETWEEN_SWIM_AND_FLY → same ack opcode (no separate unset ack exists in WotLK 3.3.5a) - SMSG_MOVE_SET_COLLISION_HGT → CMSG_MOVE_SET_COLLISION_HGT_ACK via new handleMoveSetCollisionHeight() which appends the float height after the standard movement block (required by server-side ack validation)
This commit is contained in:
parent
c72186fd11
commit
84558fda69
2 changed files with 49 additions and 1 deletions
|
|
@ -1535,6 +1535,7 @@ private:
|
|||
void handleForceSpeedChange(network::Packet& packet, const char* name, Opcode ackOpcode, float* speedStorage);
|
||||
void handleForceMoveRootState(network::Packet& packet, bool rooted);
|
||||
void handleForceMoveFlagChange(network::Packet& packet, const char* name, Opcode ackOpcode, uint32_t flag, bool set);
|
||||
void handleMoveSetCollisionHeight(network::Packet& packet);
|
||||
void handleMoveKnockBack(network::Packet& packet);
|
||||
|
||||
// ---- Area trigger detection ----
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue