Open TheSCREWEDSoftware opened 1 day ago
Need to take care because some behaviour are voluntary. It looks strange but for example guards of stormwind or others npcs in Elwyn have the same behaviour. I was checked on retail and classic, all is correct. I don't know why blizzard do this choice.
Need to check for npcs reported.
Having patrols creatures that stop until restart doesn't sound something normal, I can go check same behaviour in retail or either cata classic or vanilla classic and make a video comparing. Sometimes npcs do stop for a bit, which is fine
Having patrols creatures that stop until restart doesn't sound something normal, I can go check same behaviour in retail or either cata classic or vanilla classic and make a video comparing. Sometimes npcs do stop for a bit, which is fine
Yes, it seems random, no adjustment of the and no adjustment of the Creature.MovingStopTimeForPlayer
or WaypointMovementStopTimeForPlayer
options makes any difference either.
But if this is actually intentional, it's such a strange decision.
During my tests, I waited 5min without restart from npcs . It's maybe more longer. So need to investigate on it's really work.
Sorry @Grimdhex i'm having a hard time understanding your comment. Did you encounter the issue?
Edit:
I will leave two videos with a side-by-side, at the first frame before the gossip menu appears. And has chapters, divided 2. 1 from the start to the end of the fatest npc to move and the second is the one that doesn't move.
Left it's Blizzard Classic-Classic (Vanilla) and Right it's AzerothCore. While the tests were made with less than 10 minutes. Until 30 minutes I gurantee they do not move.
Stormwind Guard Has 2 chapters.
Bread Vendor Has 2 chapters.
On AC npc doesn't restart to move. I can confirm this also.
Thanks you a lot for videos. the only bad news is the time to start moving again seems to not be the same for all npcs. And probably a min/max system. As I said before, I hadn't observed anything after 4/5min a while ago.
Thanks for confirming this, hopefully on the path to fix, I tried running my build in debug mode but no so sure this is actually going to throw errors of any kind.
Thanks for confirming this, hopefully on the path to fix, I tried running my build in debug mode but no so sure this is actually going to throw errors of any kind.
There are no errors or bugs. It's just that interacting with an NPC interrupt and finish their path. Need to implement a pause instead.
Current Behaviour
If you talk to any npc that has an interaction, like a gossip, they will stop and stay there until a server restart.
Expected Blizzlike Behaviour
After the interaction is done, for them to eventually move.
Source
N/A
Steps to reproduce the problem
For alliance, at the start of the server / loading the area.
.go c 208110
// Isle of Conquest EmissaryIsle of Conquest Emissaries
For horde, at the start of the server / loading the area.
.go c i 23713
// KraxxExtra Notes
Reported by
atlas
( iatlas |155066684774940674 ) in DiscordAC rev. hash/commit
AzerothCore rev. f14edcbdc90c
Operating system
Windows 10 x64
Custom changes or Modules
None