Compare commits

...

6 Commits

Author SHA1 Message Date
tabooo
b84f4435b0
Merge ca10c7cbe245745719395be58077b8b5bd14dd6e into f6c4164765afe447476114e632ee3d70b04a1777 2025-02-20 17:53:52 +04:00
Andrew
f6c4164765
chore(CI): Add mod-costumes (#21548) 2025-02-20 06:29:46 +01:00
tabooo
ca10c7cbe2 ### TITLE
## Type(Scope/Subscope): Commit ultra short explanation
## |---- Write below the examples with a maximum of 50 characters ----|
## Example 1: fix(DB/SAI): Missing spell to NPC Hogger
## Example 2: fix(CORE/Raid): Phase 2 of Ragnaros
## Example 3: feat(CORE/Commands): New GM command to do something
remove the brackets on one line if statements :)

### DESCRIPTION
## Explain why this change is being made, what does it fix etc...
## |---- Write below the examples with a maximum of 72 characters per lines ----|
## Example: Hogger (id: 492) was not charging player when being engaged.

## Provide links to any issue, commit, pull request or other resource
## Example 1: Closes AzerothCore issue #23
## Example 2: Ported from other project's commit (link)
## Example 3: References taken from wowpedia / wowhead / wowwiki / https://wowgaming.altervista.org/aowow/

### CO-AUTHOR(S)
## If there are more authors they can be mentioned like this
## Co-authored-by: name <name@example.com>

## =======================================================
##                     EXTRA INFOS
## =======================================================
## "Type" can be:
##    feat     (new feature)
##    fix      (bug fix)
##    refactor (refactoring production code)
##    style    (formatting, missing semi colons, etc; no code change)
##    docs     (changes to documentation)
##    test     (adding or refactoring tests; no production code change)
##    chore    (updating bash scripts, git files etc; no production code change)
## --------------------
## Remember to
##    Capitalize the subject line
##    Use the imperative mood in the subject line
##    Do not end the subject line with a period
##    Separate subject from body with a blank line
##    Use the body to explain what and why rather than how
##    Can use multiple lines with "-" for bullet points in body
## --------------------
## More info here https://www.conventionalcommits.org/en/v1.0.0-beta.2/
## =======================================================
## "Scope" can be:
##    CORE     (core related, c++)
##    DB       (database related, sql)
## =======================================================
## "Subscope" is optional and depends on the nature of the commit.
## =======================================================
2025-02-11 23:14:48 +04:00
tabooo
82a573699b ### TITLE
## Type(Scope/Subscope): Commit ultra short explanation
## |---- Write below the examples with a maximum of 50 characters ----|
## Example 1: fix(DB/SAI): Missing spell to NPC Hogger
## Example 2: fix(CORE/Raid): Phase 2 of Ragnaros
## Example 3: feat(CORE/Commands): New GM command to do something
whitespace remove

### DESCRIPTION
## Explain why this change is being made, what does it fix etc...
## |---- Write below the examples with a maximum of 72 characters per lines ----|
## Example: Hogger (id: 492) was not charging player when being engaged.

## Provide links to any issue, commit, pull request or other resource
## Example 1: Closes AzerothCore issue #23
## Example 2: Ported from other project's commit (link)
## Example 3: References taken from wowpedia / wowhead / wowwiki / https://wowgaming.altervista.org/aowow/

### CO-AUTHOR(S)
## If there are more authors they can be mentioned like this
## Co-authored-by: name <name@example.com>

## =======================================================
##                     EXTRA INFOS
## =======================================================
## "Type" can be:
##    feat     (new feature)
##    fix      (bug fix)
##    refactor (refactoring production code)
##    style    (formatting, missing semi colons, etc; no code change)
##    docs     (changes to documentation)
##    test     (adding or refactoring tests; no production code change)
##    chore    (updating bash scripts, git files etc; no production code change)
## --------------------
## Remember to
##    Capitalize the subject line
##    Use the imperative mood in the subject line
##    Do not end the subject line with a period
##    Separate subject from body with a blank line
##    Use the body to explain what and why rather than how
##    Can use multiple lines with "-" for bullet points in body
## --------------------
## More info here https://www.conventionalcommits.org/en/v1.0.0-beta.2/
## =======================================================
## "Scope" can be:
##    CORE     (core related, c++)
##    DB       (database related, sql)
## =======================================================
## "Subscope" is optional and depends on the nature of the commit.
## =======================================================
2025-02-11 22:59:48 +04:00
tabooo
8f30a36823 ### TITLE
## Type(Scope/Subscope): Commit ultra short explanation
## |---- Write below the examples with a maximum of 50 characters ----|
## Example 1: fix(DB/SAI): Missing spell to NPC Hogger
## Example 2: fix(CORE/Raid): Phase 2 of Ragnaros
## Example 3: feat(CORE/Commands): New GM command to do something
fix codestyle

### DESCRIPTION
## Explain why this change is being made, what does it fix etc...
## |---- Write below the examples with a maximum of 72 characters per lines ----|
## Example: Hogger (id: 492) was not charging player when being engaged.

## Provide links to any issue, commit, pull request or other resource
## Example 1: Closes AzerothCore issue #23
## Example 2: Ported from other project's commit (link)
## Example 3: References taken from wowpedia / wowhead / wowwiki / https://wowgaming.altervista.org/aowow/

### CO-AUTHOR(S)
## If there are more authors they can be mentioned like this
## Co-authored-by: name <name@example.com>

## =======================================================
##                     EXTRA INFOS
## =======================================================
## "Type" can be:
##    feat     (new feature)
##    fix      (bug fix)
##    refactor (refactoring production code)
##    style    (formatting, missing semi colons, etc; no code change)
##    docs     (changes to documentation)
##    test     (adding or refactoring tests; no production code change)
##    chore    (updating bash scripts, git files etc; no production code change)
## --------------------
## Remember to
##    Capitalize the subject line
##    Use the imperative mood in the subject line
##    Do not end the subject line with a period
##    Separate subject from body with a blank line
##    Use the body to explain what and why rather than how
##    Can use multiple lines with "-" for bullet points in body
## --------------------
## More info here https://www.conventionalcommits.org/en/v1.0.0-beta.2/
## =======================================================
## "Scope" can be:
##    CORE     (core related, c++)
##    DB       (database related, sql)
## =======================================================
## "Subscope" is optional and depends on the nature of the commit.
## =======================================================
2025-02-11 22:57:15 +04:00
tabooo
4fc4646d73 fix(Core/Spells): Druid Shapeshifting procs Omen of Clatiry
Druid talent Omen of Clatiry is proced by shapeshifting.

https://github.com/azerothcore/azerothcore-wotlk/issues/21401
2025-02-11 22:11:50 +04:00
2 changed files with 33 additions and 1 deletions

View File

@ -28,3 +28,4 @@ git clone --depth=1 --branch=master https://github.com/azerothcore/mod-server-au
git clone --depth=1 --branch=master https://github.com/azerothcore/mod-transmog.git modules/mod-transmog
git clone --depth=1 --branch=main https://github.com/azerothcore/mod-progression-system.git modules/mod-progression-system
git clone --depth=1 --branch=master https://github.com/azerothcore/mod-arena-3v3-solo-queue.git modules/mod-arena-3v3-solo-queue
git clone --depth=1 --branch=master https://github.com/azerothcore/mod-costumes.git modules/mod-costumes

View File

@ -64,7 +64,14 @@ enum DruidSpells
enum DruidIcons
{
SPELL_ICON_REVITALIZE = 2862
SPELL_ICON_REVITALIZE = 2862,
SPELL_ICON_FUROR = 210,
SPELL_ICON_MOONKINAURA = 46, // SpellId: 24907
SPELL_ICON_MASTER_SHAPESHIFTER = 2851, // SpellId: 48421
SPELL_ICON_NURTURING_INSTINCT = 2254, // SpellId: 47180
SPELL_ICON_FERAL_SWIFTNESS_PASSIVE_2A = 67, // SpellId: 24864
SPELL_ICON_LEADER_OF_THE_PACK = 312, //SpellId: 24932
SPELL_ICON_TREE_OF_LIFE = 2257 //SpellId: 34123
};
// 1178 - Bear Form (Passive)
@ -223,6 +230,24 @@ class spell_dru_omen_of_clarity : public AuraScript
if (spellInfo->SpellFamilyName == SPELLFAMILY_DRUID)
{
// Exclude shapeshifting
if (spellInfo->SpellIconID == SPELL_ICON_MOONKINAURA)
return false;
if (spellInfo->SpellIconID == SPELL_ICON_MASTER_SHAPESHIFTER)
return false;
if (spellInfo->SpellIconID == SPELL_ICON_NURTURING_INSTINCT)
return false;
if (spellInfo->SpellIconID == SPELL_ICON_FERAL_SWIFTNESS_PASSIVE_2A)
return false;
if (spellInfo->SpellIconID == SPELL_ICON_LEADER_OF_THE_PACK)
return false;
if (spellInfo->SpellIconID == SPELL_ICON_TREE_OF_LIFE)
return false;
return !spellInfo->HasAura(SPELL_AURA_MOD_SHAPESHIFT);
}
@ -235,6 +260,12 @@ class spell_dru_omen_of_clarity : public AuraScript
return false;
}
// Furor 210
if (spellInfo->SpellIconID == SPELL_ICON_FUROR)
{
return false;
}
return true;
}