Commit Graph

6 Commits

Author SHA1 Message Date
avirar
739a0df44c Warrior strategy update (#838)
* Enraged regen at critial health

* Enraged regen action context

* Enraged regen on critical health trigger

* Enraged regen on critical health trigger

* Added logic for Arms to use Retaliation

* Added logic for Arms to use Retaliation

* Used correct class enums for !players

* Retaliation on medium health

* Removed temp line

* Added check for attacker->GetVictim() != bot

* Adjusted triggers for emergency actions

* Added Shattering Throw logic

* Added Shattering Throw logic

* Added Shattering Throw logic

* Added Shattering Throw logic

* Added Shattering Throw logic

* Added Shattering Throw logic

* Fixed ActionNode for Shattering Throw

* Added debug logging

* More debug logs

* Better debug logs

* Adjusted range on action

* Adjusted priorities

* More logging

* Update WarriorActions.cpp

* Update WarriorActions.h

* Changed trigger name for differentiation

* Updated to new shattering throw trigger name

* Update WarriorTriggers.h with new ST name

* Update ArmsWarriorStrategy.cpp

* Changed priority

* Shattering Throw and Retaliation stance reqs

Battlestance needed for Shattering Throw and Retaliation

* Created isUseful for Shattering Throw

* Created isUseful for Shattering Throw

* GetTarget instead of GetTargetValue

* Changed to GetTarget instead of GetTargetValue

* Commented out Execute function

* Commented out Execute function

* isPossible was failing, created basic isPossible

IsImmuneToSpell was returning true for Shattering Throw

2 DAYS! :(

* isPossible was failing, created basic isPossible

* Added some more isPossible checks

* Update WarriorActions.cpp

* Missing )

* Missing !

* Removed logging

* Removed logging

* Clean up

* Cleanup

* Corrected logic for Rogue's Expose Armor trigger

Logic was checking the Rogue, not the Rogue's target, for Sunder Armor before casting Expose Armor.
2025-01-03 16:06:47 +01:00
avirar
5c8283d40a Prot warriors cast vigilance when in a group (#825)
* Add Vigilance

* Vigilance

* Update WarriorTriggers.h

* Update TankWarriorStrategy.cpp

* Update WarriorAiObjectContext.cpp

* Update WarriorTriggers.cpp

* Update WarriorTriggers.h

* Update WarriorTriggers.cpp

Check for existence of Vigilance in raid already

* Update WarriorActions.cpp

Check for existence of Vigilance in raid already
Apply to tanks, then highest gearscore DPS.

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Added logout

Bots keep assigning it to me and not maintank? Added logging to clarify

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Update WarriorTriggers.cpp

* Update WarriorTriggers.cpp

* Update WarriorTriggers.cpp

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Update WarriorTriggers.cpp

* Update WarriorActions.cpp

* Update WarriorActions.cpp

* Removed Logs

* Removed logs

* Added check for spell in trigger

* Update WarriorTriggers.cpp

* !member->IsAlive()

* !member->IsAlive()
2024-12-29 21:47:22 +01:00
Yunfan Li
53611c9040 Run clang-format 2024-08-04 10:23:36 +08:00
Yunfan Li
036a890aa1 Optimize fury warrior 2024-02-11 00:17:04 +08:00
Yunfan Li
33576bd969 fix(spell): paladin and dk aggro spell, warrior 2023-06-11 15:55:36 +08:00
UltraNix
b952636f0d Big update. 2022-03-12 22:27:09 +01:00