We been saying that for a couple weeks now, fucked if I know how he threads the needle.

Are you angry about being left behind the Class arms race?
or do you hate the mythical "easy button"?

Normally feeling one of those would put you at odds with anyone who feels the other... But here in DDO land we have a new solution cleverly designed to make both of those camps feel warm inside!

It's called "OVER PERFORMING" and it is a amazing bit of word-wizardry!

See in months gone by so many fantastic and divisive things have become part of DDO land, things that divide the community and make it hard for a games publisher to find the right path without alienating one side or the other.

Confused? well here is a example to help explain! Holy sword is a hot little bugger of a topic and spell, Some people bloody love it and its sweet sweet Crit mods, while others think it is the spawn of satan, a spell that makes it too easy for players to achieve the level of DPS only a dedicated builder should have.

What to do? what to do? if the developers roll it back it will upset lots of players who enjoy it and insist loudly that they should be able to have it. But if the Developers don't do anything? well that upsets lots of players who think it is too OP and that it is a horrible "easy button" cheapening their virtual Heroics! And it's not just Holy sword, its bards, or Barb healing, or ice spinning, or any other laaaaaarge number of issues...

Quite a quandary eh? how can they keep everyone happy? To choose one way or another is to risk the wrath of bruised egos in both camps!! Just weeks ago it all seemed doomed to end in tears.... sob sob...

But then some mighty Spin-Sorcerer came up with a amazing new incantation to defuse the ticking time bombs! perhaps you have seen it beginning to pop up all over the forums in recent weeks? it is a amazing term, a term called "Over performing'!!!

By slyly suggesting some contentious issue or mechanic is "Over Performing" the wily Developer is able to stake out territory in the middle of the field of battle! It's simplicity is staggering in it's effect on the disputes, and no I'm not exaggerating.

When a hypothetical developer.... let's call him ... say... Barney, when Barney addresses something like holy sword he can say that while they are no plans to nerf or remove it they are aware that it may be "Over Performing", or even say that the developers are noticing that Holy sword can "Over Perform" in situations.....

This is brilliant, and I mean really BRILLIANT Word-wizardry on Barney's part, because while he is in the first case assuring the people who like it that he isn't changing it, he is at the very same time giving a knowing nod and wink to the other camp, beautifully conveying that he knows it is to easy for "real gamers" implying that really something will have to be done about it, without saying it will!

With the judicious use of the magic term "Over Performing" Barney really says nothing and promises nothing while at the same time Soothing both camps egos and re-enforcing their tightly held preconceptions and prejudices all while not actually indicating that anything concrete will be done!!

MAGIC!

Now this isn't the first Word-wizardy we have seen emerge in the Land of DDO this year but it is the most shockingly effective at stalling back and baffling the assorted camps of the land. A earlier incantation called the "Our Data" spell was fairly effective at shutting down opposition and dubious posters that didn't agree with the Development team, but really that was ML 14-16 spell casting at best, while the new "Over Performing" spell? it's bloody Epic stuff!

Hey Cordovan, why was the thread closed? there is no reason given.  I ask because it was a great thread that I was enjoying and was interested in the discussion. Sort of a new kind of light hearted approach to a something that has been happening too much with out all the normal Nerd-rage.

I understand you have to shut down threads sometimes, but you should really post the reason so people who were following it and part of it can know what Turbine thought the problem was.

For future reference.