Bard's 6.1 changes - why bother?

[QT_Melon]

I agree. I suppose seeing PP light up in two places on your bar could be an eyesore, but functionally speaking, nothing has changed if you want to keep the old layout (apart from the bug, which obviously needs to be fixed ASAP).

That said, I don't think "messes up muscle memory" is a good argument against a job change in the first place. It's pretty much a given that as jobs evolve over time you'll need to make some changes to your hotbar layout.

I appreciate this change, since while BRD is not button bloated, I'd still rather use as few keybinds as possible unless there's a functional demand for more of them. This change probably would have happened at some point to make way for new abilities anyways - just because the job isn't bloated now doesn't mean it never will be.

Yeah but you're not understanding WHY it screws with Muscle Memory.

WM changing to PP screws up with the Queue. So for years people are proc fishing for Pitch perfect so they hit it maybe double hit it. On its own not a problem, but now since your button shares with another skill, WM double pressed thinks you're trying to queue PP again.

So it's not that it screws with a muscle memory of the rotation or some kind of functionality of having it there twice. You're screwing with the proc fishing and how the button itself queues and causes more queue jams like it does with Raging Strikes. Some bard players aren't the mashy types but many are for years of priorty/proc fishing. Just overall conditioning for Bard. While it's been slowed down a lot with the RoB procs it's just the habit from the style of play Bard has had over the years.

Nor is anyone blind to knowing a job eventually evolves - even if we miss our Flaming Arrows and Wide Volley.

Removing button bloat for future job evolution is fine. However, I think the rework button share would have better suited Burst Shot/Straight/ Refulgent. Just feel that dual OGCD button sharing doesn't mix well vs dual GCD button sharing. But honestly, killing two GCD DoTs and merging them into 1 would have been the best solution since they seem to be bent on getting rid of multi DoT jobs anyways.