You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The talent Ancestral Protection Totem (ID:51485) given to Chaman Restoration at lv.75 has an issue
Ancestral Protection Totem: Summons a totem at the target location for 30 sec. All allies within 20 yards of the totem gain 10% increased health. If an ally dies, the totem will be consumed to allow them to Reincarnate with 20% health and mana.
Current behaviour:
The talent doesn´t work, when you summon the totem it appears but it doesn´t do anything.
Expected behaviour:
when you summon the totem all allies 20 yards around it should gain 10% increased health, and if an ally dies the totem should be consume allowing the ally to reincarnate with 20% health and mana
Steps to reproduce the problem:
Create a Chaman character
Reach lv.10 and choose the Restoration Spec
Reach lv.75 and choose the talent Ancestral Protection Totem
Use the talent surrounded by allies and enemies who can kill them
Description:
The talent Ancestral Protection Totem (ID:51485) given to Chaman Restoration at lv.75 has an issue
Ancestral Protection Totem: Summons a totem at the target location for 30 sec. All allies within 20 yards of the totem gain 10% increased health. If an ally dies, the totem will be consumed to allow them to Reincarnate with 20% health and mana.
Current behaviour:
The talent doesn´t work, when you summon the totem it appears but it doesn´t do anything.
Expected behaviour:
when you summon the totem all allies 20 yards around it should gain 10% increased health, and if an ally dies the totem should be consume allowing the ally to reincarnate with 20% health and mana
Steps to reproduce the problem:
Branch(es):
Master
TC rev. hash/commit:
7c66e7b
TDB version: 7.2.0+updates
Operating system: Windows 10
Description in wowhead http://www.wowhead.com/spell=207399/ancestral-protection-totem
The text was updated successfully, but these errors were encountered: