-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dressnpc_master] DressNPC - Upright Orcs #107
Comments
I'm gonna guess that means DressNPC is just straight-out incompatible with upright orcs or is there something else that decides about this? |
I have not found what it is that decides this or if dressnpcs is capable of this. If blizzard is able to do it, then it should be possible in dressnpcs. |
Hello, instead of creating new issue i'm gonna use this one, i noticed something with uprights orcs in bfa 8.3 (my actual rev : 5a6970e) You can see upright orcs when you go away from them (more than 600 yards) and come back Step to reproduce :
That's weird, because the mirror image doesn't handle the upright pose, even on live realm |
Interesting. I have not had enough time and motivation to install a client and go see.
If that is the case, then its probably worth trying to look into if the features can somehow be applied earlier in creating a creature or potentially force sent/updated to client. |
Description:
Orc characters that use the upright posture have
customDisplay3 = 1
(characters
table) but settingfeature3 = 1
doesn't make them upright for DressNPC.Current behaviour:
Nothing happens, the orc remains non-upright if you set
feature3 = 1
.Expected behaviour:
The DressNPC Orc uses the upright Orc model/skeleton/posture
Steps to reproduce the problem:
customDisplay3 = 1
in thecharacters
table.feature3 = 1
and notice it doesn't emulate the same behaviour.Branch(es):
dressnpcs_master
TC rev. hash/commit:
Any BFA commit that supports upright Orcs (8.0.1+), so latest hash:
TrinityCore@d11b9a6
TDB version: TDB 7.3.5 (it's never been updated)
Operating system: Windows 10
The text was updated successfully, but these errors were encountered: