- Status Fixed
- Percent Complete
- Task Type Bug Report
- Category Spell
- Assigned To No-one
- Operating System Windows
- Severity Low
- Priority Very Low
- Reported Version Development
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Wowaddicts Legion
Opened by katasztrophe - 13.11.2025
Last edited by wowaddicts - 15.11.2025
Opened by katasztrophe - 13.11.2025
Last edited by wowaddicts - 15.11.2025
FS#1323 - Shockwave - prot warrior ability
Shockwave ability worked fine for an hour, then it became grayed-out and is no longer functioning. I tried changing the talent while in a capital city, but this fixes the ability just for a couple of minutes.
Thanks
Loading...
Available keyboard shortcuts
- Alt + l Login Dialog / Logout
- Alt + a Add new task
- Alt + m My searches
- Alt + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + e ↵ Enter Edit this task
- Alt + w watch task
- Alt + y Close Task
Task Editing
- Alt + s save task
Forgot to mention: Shield Block doesn't work like it should, I simply cannot use it whenever I want. Can't combo it with Shield Slam. It does start to work, but after some time after I've engaged in combat.
Thanks
Hello, I will check Shockwave now.
About Shield Block, do you know that it uses 30 rage? maybe that is why you cant use it till you have engaged in combat and Shield Slam generate 15 rage only. https://www.wowhead.com/spell=2565/shield-block
Well I was testing it, and I didnt can reproduce the bug, I guess I will need more info. What others talents are you using?
By the way, you try to delete your cache folder of client, maybe that fixes it.
I will wait for your feedback and more details.
Oh, my bad about the Shield Block.
I did deleted the Cache folder - it didn't work.
I'll let you know about the talents as soon as i can log in.
Thanks
Not sure if you did anything, but after an hour of playtime, it seems to be working normally.
Thank you very much!
Well…I only checked it, surely what fixed it for you, it was deleting cache ;). Nice, if it happens again, you dont hesitate in reporting it back. Regards.