-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(Core): Crashfix. #11740
fix(Core): Crashfix. #11740
Conversation
This modification may not fix the issue. Addittional information: |
|
Oh, Vehicle::IsVehicleInUse (this=0x0) Salvaged Siege Turret has seat1 defined at vehicle.dbc. |
tested. |
* master: (31 commits) Core/Combat: rename getThreatMgr() to GetThreatMgr() (azerothcore#11758) fix(Core/Spells): Windfury, Flametongue, Healing Stream, Cleansing … (azerothcore#11761) fix(Core/Spell): Enslaved Demon does not auto-attack/auto-cast (azerothcore#11677) chore(DB): import pending files fix(DB/Quest): Quest "Relic of the Earthen Ring" should be reset on … (azerothcore#11755) fix(Core/Spells): The Earthshatterer 8/9 set bonus should be removed … (azerothcore#11757) chore(DB): import pending files fix(DB/Spells): Fixed Shaman's Clearcasting proc. (azerothcore#11754) chore(DB): import pending files fix(DB/Gossips): Earthcaller gossips (azerothcore#11792) chore(DB): import pending files fix(DB/Quest): Coward Delivery... Under 30 Minutes or it's Free (azerothcore#11734) fix(DB/Creature): Goblin Land Mine playing Hakkar voiceline (azerothcore#11756) fix(Core/Scripts): Black Template Area Boundary (azerothcore#11705) fix(DB/SAI): Fixed crystal fang to spawn 4 spiders on death (azerothcore#11732) refactor(Core/Combat): implement compatiblity layer for ResetAllThreat() (azerothcore#11778) fix(DB/Creature): Hakkar should be taunt immune. (azerothcore#11777) fix(Core/Spells): Priest with Spirit of Redemption should be immediat… (azerothcore#11771) fix(Core): Crashfix. (azerothcore#11740) fix(Core): Crashfix. (azerothcore#11741) ...
Issues Addressed:
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.