Skip to Content

WoW Insider has the latest on the Mists of Pandaria!
  • Elenac
  • Member Since Oct 14th, 2008

Are you Elenac? If So, Login Here.

WoW58 Comments

Recent Comments:

Breakfast Topic: Is "For the Horde" obsolete? {WoW}

Mar 3rd 2012 6:14PM Hmm, You No Take Candle!!! Hmm, that actually is pretty good! I rather shout that as a gnome than something about some human business. Heck, I rather use some dwarven battle cry than some Stormwind commité crap. But, You No Take Candle fits pretty well in my mouth... I can see myself shouting that while running out of the AB gates, or riding the SotA demos straight into a gate. It actually works in such situations much better than For Gnomeregan!

Breakfast Topic: Is "For the Horde" obsolete? {WoW}

Mar 3rd 2012 6:07PM Yes, exactly!!! I have no idea why people continue to say that we don't have an alliance battle cry.

For Gnomeregan!

Ol' Grumpy and the specter of pointless elitism {WoW}

Feb 2nd 2012 7:39PM Yes, this! Or, well... for me it's the BG big mouths going on and on and on about how everybody else sucks. Well, thank you, I feel so privileged that all of us were able to run in your uber pvp presence. We would have been totally lost without your leadership... oh... wait... they were really not doing much anything than typing insults the whole time.

The natural flow of a bg is that there are some high points and some low points, and hopefully it ends on a high point. But no, these idiots start running their mouths... um... fingers... at the sight of the first low, and of course that means that you will not see any high points after that... and I'm there to win the bg, so that makes me mad. And having to "listen" to idiots ranting totally takes the fun out of everything.

Retribution bug hotfixed, Vengeance temporarily returns to PvP {WoW}

Feb 2nd 2012 7:18PM "Better their developers have to look through that mess of code then me."
Amen to that!

I don't know how many times I have thought "Oh, that bug has absolutely nothing to do with my small fix to the code as it is totally unrelated." only to be proved totally wrong after a lengthy session of debugging. One small fix here affects a part there, which turns a flag up at some other part, which in turn... and finally it causes the bug in some _totally_ unrelated place.