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
feat(Core/Items): Implemented elemental weapon damage. Source: Trinit… #13050
Conversation
from checks |
Tested with custom melee weapons with fixed elemental damage. Only arcane damage is affected by resistances, while other types of damage have no partial resists nor full resists. Melee weapon damage is increased by Ossirian Crystal debuff (Fire Weakness, Frost Weakness, etc) Melee weapon damage is increased and decreased by Chromaggus Elemental Shield. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Gultask I need all items you used during the tests. |
Wands: Melee Weapons:
and |
Tested with fire wand and fire weapon with
Remember that spells like
@Gultask Please, retest it. |
Oh yes, I forgot about re-testing Ossirian and Chromaggus' weaknesses. They work fine now with wands. |
@Gultask |
|
I messed up Ossirian in another PR. I'm sorry 🤦 |
@Gultask So everything is okay now? |
I'll try again ASAP |
Yes, my mistake. The resistances look fine, sorry about that. |
@Gultask Should be okay now. |
Other than that I don't know of any other bosses where a testing could be useful, so I'm a bit limited here. |
@Gultask Melee immunity should be okay now. |
Spell, melee and wand immunities still work ok 👍 |
@Gultask Viscidus should be okay as well :) |
😮 |
@Gultask Big kudos to you for testing this :) |
Thanks for making the PR ^^ |
Merge conflicts due to QAston Edit: It has been reverted :) |
…yCore.
Closes #12165
Issues Addressed:
Tests Performed:
How to Test the Changes:
More info here
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.