fix(skill): a start with a skill handle still in progress is dropped, as the client

LWOSkillComponent::msgStartSkill (0x00d45cb0) logs and ignores a StartSkill
whose skill handle is still waiting on behavior syncs. The server ran it a
second time: the hits, the imagination cost and the mission progress twice.
Live captures hold 22 byte-identical StartSkill resends with the same
handle a few packets apart.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Aaron Kimbrell
2026-10-02 09:56:05 -05:00
parent 4fbebf7135
commit c9929f1c1e
5 changed files with 84 additions and 0 deletions

View File

@@ -126,6 +126,11 @@ public:
*/
bool HasSkill(uint32_t skillUid) const { return m_managedBehaviors.contains(skillUid); }
/**
* @return whether a skill with that handle still waits for the client to sync one of its behaviors
*/
bool IsSkillPending(uint32_t skillUid) const;
/**
* Starts a player skill. Should only be called when the server receives a start skill message from the client.
* @param behaviorId the root behavior ID of the skill