I have to agree, both as a first-round beta tester of WAR, and as a player of many other MMOs. But I don't think it has anything to do with "playing" their own game, but speaks volumes about the development and QA teams.

If such a globally affecting bug was known about, it should have been pushed to the very top of the "must fix this right now" list. A producer that assigns development assets to bugfixes needs to have the "big picture" in mind at all times, and this seems to be a pretty "big" issue. I would say that this type of an issue is as severe and game-affecting as a major crash-bug that locked people out of the game. The only thing that could possibly take precedence over something as large as this would be a server crash issue.

It's not like this will change one class or affect a small subset of the playerbase. (Although it could be argued that ANY change will only affect a small subset of the playerbase these days, since the playerbase itself is so small.) Sometimes the designers have to suck it up and accept that things are the way they are, even if that wasn't the original intent. It would have been better for them to "fix" this in other ways than simply roll out a completely revamped AP regen system.

Seriously, the game has been released for over a year now. How could such a fundamental game-affecting bug have gotten past QA testing, much less gone un-noticed by the development team for nearly a full year?

I love Mythic and their games, and I still have an active DAoC account. But I have no ill feelings about closing my WAR accounts.