More often than not, gamers would likely jump into the fray first before giving any thought about it. When it comes to the more serious aspects, gamers often would raise priorities of thought first above all else. So we could probably forgive World of Warcraft players if they took minor aspects of the game - like guild naming - less seriously than they should have.

 

But Blizzard might not take too kindly to that. Again. Steaky of Barthilas created a new guild called ROFLCOPTER which is in direct violation of Blizzard's Naming Policy for pets, guilds, characters and Arena team names. More appropriately, it fits in the section of "Leet" or "Dudespeak":

Contain "Leet" or "Dudespeak"

This category includes names which:
* Consist of language existent only in online communication (i.e. Roflcopter, xxnewbxx, Roxxoryou)
If a player is found to have such a name for their character, guild, arena team, or pet, he/she may:
* Be prompted to select a new name for the character upon next login

An unworthy name doesn't have too dire a consequence, but smelly Vrakthis wanted to point out one thing: your guild name may be changed, only if a Game Master reviews a petition you send in and decides if your name needs a change or not. Emphasis on "may."

So while a hidden and obviously serious punishment looms over repeat violators, it's still not certain if you'll be able to keep your guild and simply have its name changed, or completely lose the guild and be forced to create another one again. So just in case, hop on over to the Read link below to absorb Blizzard's "guidelines" in World of Warcraft's naming conventions.

World of Warcraft Forums member Grallax has recently noted that he's been having trouble with with the UBRS Key Quest. Much like other folks who have been having problems with the Seal of Ascension Quest, whenever he talks to the NPC inside LBRS his quest items and his quest gets "deleted."

Blizzard CM Vrakthris has informed Grallax that yes, there is a problem with the NPC for the quest. They're still working on it, but at least, until the fix comes in, they have a work around that players can use.

If you're planning to go on this quest yourself, and you're curious about the workaround that Blizzard's got, feel free to head to the thread discussing the lengthy solution by clicking on the Via link below.

If you're not willing to do that, and you don't want to scour through post after post just to get the workaround, here's a pertinent quote from Vrakthris:

The issue with Vaelan and the Seal of Ascension is a known one and we hope to have a resolution to it added in a future patch. Unfortunately right now I can only present you with a work around for the issue.

Basically what is happening is when the instance resets Vaelan will forget that he has ever spoken to you. In order to get around this you will need to acquire another Unadorned Seal of Ascension. Once you have the Unadorned Seal of Ascension speak with Vaelan, he will examine your Unadorned Seal of Ascension and continue his dialog as if you had never been there before.

Once he runs through his starting dialog he will offer you the quest that you should be on, since you have already completed the first Seal of Ascension quest he will give you the second one as well as Vaelan's Gift which will have the Unfired Seal of Ascension and the Orb of Draconic Energy in it.

Complete the quest and return to him, again if you had left the instance long enough for it to reset you will need to speak with him while a Unadorned Seal of Ascension is in your inventory.

Another take at the work-around can be found here.