-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
fix(DB/Creature): Remove aggro from Abandoned Fuel Tank #21352
Conversation
Needs to be sniffed/checked on retail for proper npc flags |
Unfortunately I don't have the means to check retail or sniff. Is there a process for sniffing requests or a 'needs sniff' tag? Thanks. |
create object from a
|
the tanks also have aura |
Unit flags 33554432 is unselectable, unselectable creatures dont aggro |
I am only seeing this
|
Could not find reliable information about the usage of these. According to wowhead these have abilities so opted not to remove the
SmartAi
flag.Changes Proposed:
This PR proposes changes to:
Issues Addressed:
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
Known Issues and TODO List:
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.