fix(DB/Item): Include no-disenchant and refund flags to Savage Weapons#25440
fix(DB/Item): Include no-disenchant and refund flags to Savage Weapons#25440Apathyxia wants to merge 2 commits intoazerothcore:masterfrom
Conversation
…pons Disallows disenchanting of these items as well as makes them refundable for 2 hours after purchasing.
Then IMO this change should be made with those modules/scripts. Without proper sourcing, I don't think unobtainable items should have changes like this on AC. |
|
I would agree but then again we already kind of crossed that bridge when we corrected their stats last time around |
|
The stats change had a source to back it up though, no? |
|
It could be a plausible assumption this is the case for these though based on the paradigm that these are pvp items and therefor follow same rules? |
|
If this items were not available in official servers I would say keep it in a module or repo unrelated to the core, and the for the sql we shouldn't be over writing the flags, we should be adding or removing from, as stated in the sql standards . Flag = Flags | BitMask |
|
Refering to this: https://www.azerothcore.org/wiki/sql-standards To add to above, didnt read the messages prior, if we already went out the way to change the items stats before, than i cant say i disagree wit hte PR |
Updated way of adding flags according to sql standards.
Disallows disenchanting of these items as well as makes them refundable for 2 hours after purchasing.
The items have been unavailable on live servers (3.3.5a and classic wotlk). However, these items can be used via modules and custom scripts. They are PvP items so the flags are made to match other PvP items.
Changes Proposed:
This PR proposes changes to:
AI-assisted Pull Requests
Important
While the use of AI tools when preparing pull requests is not prohibited, contributors must clearly disclose when such tools have been used and specify the model involved.
Contributors are also expected to fully understand the changes they are submitting and must be able to explain and justify those changes when requested by maintainers.
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.