Don’t be pedantic; I said nothing about moving, removing, or changing Bladestorm. I said Colossus does not need it, which is not the same thing as Colossus should not have access to it.
It makes plenty of sense:
- Demolish already fills the same role as Ravager and Bladestorm, layering the two is just more rotational steps that we’re trying to get away from.
- Ravager is AoE only and Bladestorm would be for Colossus as well, which is build limiting for such a centralized node.
- Ravager is unnecessary bloat and Bladestorm does not contribute to Colossus’ rotation, so an alternative is warranted.
- Avatar’s current position is inviable to a majority of builds.
- It would give Colossus builds a better breadth of options, without forcing them into an ability that isn’t conducive to their rotation or reducing their potential to break crowd control in PvP.
Yes it is. They may get there in different ways, but they’re both offensive cooldowns that serve the same purpose in the end.
I’d be fine with removing Avatar entirely as well; in fact I already recommended that about a month ago, but it would still necessitate either moving Bladestorm to a less centralized position or putting a more universal choice onto the node in place of Ravager.
- However, doing that would also hardline PvP players into Bladestorm, which is not necessarily a good thing, since it isn’t particularly conducive to Colossus’ rotation. The advantage of having Avatar and Bladestorm on a choice node is giving those players more choice.
Because Mountain Thane requires Avatar. Baking it into Recklessness could work, but then creates dissonance with Protection’s version that requires further adjustments to address. Similar to Arms, not having access to Avatar would also leave Thane players in a position of requiring Bladestorm for PvP, while PvE players would just have an unnecessarily dead node on the talent tree.