Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rename deprecated flag UNIT_FLAG_DISABLE_MOVE
- Loading branch information
1 parent
7699a66
commit 2032cfb
Showing
3 changed files
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2032cfb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
already researched: UNIT_FLAG_REMOVE_CLIENT_CONTROL (formerly UNIT_FLAG_DISABLE_MOVE) is a client-only feature that should not be used for NPC scripting
need port it from TC:
TrinityCore/TrinityCore#17311
TrinityCore/TrinityCore@061b62a
TrinityCore/TrinityCore#17543
Aokromes/TrinityCore@9c13a84
2032cfb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is insufficient and just confirms that naming is incorrect, no concrete info on what this flag is actually doing. From client side i can confirm that it shares movement limits lifting capability with a plethora of CC flags, but that is all there is to it for now.
2032cfb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment I left in TrinityCore source for this flag is the concrete info on what this flag is actually doing (meant to do in past) - opcode 0x159 handler in 12340 client has the same code (call chain: packet handler, sub_72CCA0, sub_520FE0 (also known as CGGameUI::OnClientControlChanged)) that
CGUnit_C::OnFlagChanged
in the 1.0.0.3368 named alpha client had (CGGameUI::OnClientControlChanged
)2032cfb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The potential presence of this flag on creatures coming from live server is what concerning me. If its found only on reasonably old creatures (vanilla->tbc, since tbc development started in 2005), could be a legacy/deprecation issue. If its met on newer creatures as well, its likely a dual-use flag and we don't know the real meaning yet.
I don't think we can trust our databases on this matter, since it could be prone to intentional misuse pollution.
2032cfb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not seen it myself on any creature (ever) but I'm working on researching latest clients - the documented use is the only use of it in current live client (movement/emotes)