I agree with you. I will add that I suspect things that didn't look broken were broken 'under the hood'. What better time to fix these than when you are going to revamp stuff to 1. make old vets think things are more difficult by making choices have visible consequences (hybrid builds might be less effective, so choosing your role at the beginning will matter), 2. unload some of the database bound load, 3. use the changes to normalize or regularize combat calculations so that updates in the future are more robust, 4. allow mob AI to be revamped to be less brittle, 5. reduce data transmission so that internet connection quality does not cause as much negative impact, and 6. fix some server side bugs that exacerbate lag associated with stressed database services.
Originally Posted by MarkoftheRealm
I might be wrong, of course. I see some downsides, for the tree system might make solo life gravitate to dps lines excessively (I say this as a support class type). Still, depending upon implementation details, having the ability to save multiple specs that you can change before you enter an instance, may mitigate that downside some. It is still way to early to know (other than any instances likely will not be open at initial launch).
"No sadder words of tongue or pen are the words: 'Might have been'." -- John Greenleaf Whittier
"Do or do not. There is no try." -- Yoda
On planet Earth, there is a try.
Indeed, in a world and life full of change, the only constant is human nature (A is A, after all :P).
We old vets need to keep in mind those who come after us.