-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[TBC/HellfirePeninsula] Pit Commander #18619
Comments
AzerothCore rev. 061d414 2024-04-20 01:20:52 +0000 (master branch) (Unix, RelWithDebInfo, Static) Having this issue. Just rebuilt. |
That's odd. One would assume it's the other way around. Good of you to discover that. |
So with |
Fel Reavers and Pit commander starts when they are loaded.... |
The strange thing in my mind is that no matter what they won't move (on my end at least) when preload and set as active are enabled. Even if I stick around near them and can even see them they still won't move. |
Oh i must add... i use the playerbot fork... |
can you paste your worldserver.conf please |
Remeber , i am using the Playerbots version from Liyufan https://github.com/liyunfan1223/azerothcore-wotlk/tree/Playerbot |
Current Behaviour
The creatures that are supposed to march towards The Stairs of Destiny in Hellfire Peninsula do in fact not path at all. Pit Command and Wrath Masters can be seen at the Portal Xilus, Portal Kruul, Gateway Shaadraz and Gateway Murketh.
There may be more spawn locations for these.
Expected Blizzlike Behaviour
They should path across The Path of Glory towards The Stairs of Destiny, or the Dark Portal if you prefer.
Source
No response
Steps to reproduce the problem
Extra Notes
Portal Xilus:
.go xyz -99 1892 79 530
Portal Kruul:
.go xyz -418 1828 76 530
(This is where Pit Commander is at)Gateway Shaadraz:
.go xyz -276 1529 31 530
Gateway Murketh:
.go xyz -172 1513 29 530
If it matters at all I do have
PreloadAllNonInstancedMapGrids
andSetAllCreaturesWithWaypointMovementActive
enabledAC rev. hash/commit
3ff8de2
Operating system
Ubuntu 22.04
Custom changes or Modules
Tested with nothing enabled
The text was updated successfully, but these errors were encountered: