Sword and board dream
Please for all that is holy move the bastion talent! Move it in line with the other spec defining weapon talents and let me have my sword and board Dps dream.
I have made another post about the bastion talent but perhaps didn’t make a coherent point.
The argument could be that I can just use a 1h and shield already. My answer is that totally gimps you for no reason, with the bastion talent it gives you a defining talent to build around.
It was moved from row 5 to row 6 for no other reason then to make a path for secondary PvP tech. Smh
I don’t want to lose one of the coolest class fantasies, imo, because some end game pvp Dps warrior might want to pick up imp disarm? Moving bastion still wouldn’t affect that.
Going to rant about it until it becomes reality
**EDIT – Why I’m specifically suggesting row 4 for Bastion** Just wanted to clarify the reasoning behind the proposed talent placement.
With 51 talent points available, moving Bastion to row 4 would allow a **31 Fury / 20 Protection** build, combining Bloodthirst with 5/5 Bastion.
This would open up a sword-and-shield DPS playstyle that could benefit from Fury’s offensive talents, including Gore Drinker and Flurry, while retaining some of Protection’s defensive utility.
I’m not suggesting sword-and-shield should outperform conventional dual-wield Fury or two-handed Arms. The intention is simply to make it a viable alternative with different strengths and weaknesses.
**The shield requirement is already a significant trade-off.** You’re sacrificing the damage and rage generation of an off-hand weapon or the damage potential of a two-hander.
I appreciate the concerns about Fury/Protection hybrid tanking, but I’d argue that deep Protection should remain attractive through its dedicated tanking tools rather than by restricting access to alternative damage builds.
Ultimately, I’d love to see Bastion tested in row 4 during beta. If the resulting builds need tuning, that’s what testing is for. **The abilities and talents already exist. It’s their accessibility that I’m asking the developers to reconsider.**