arcane-missiles
Latest
Arcane Brilliance: PvPing as an Arcane Mage after 3.1
Each week Arcane Brilliance comes to work totally motivated, ready to sit down and manufacture a fantastic, insightful, entertaining column about Mages. Then Arcane Brilliance's wife brings him breakfast, because she's awesome like that, and Arcane Brilliance takes a break to eat it. Fat and happy, Arcane Brilliance flexes its fingers and gets ready to resume the creative process. Then winamp shuffles through to a song from the new Silversun Pickups album and Arcane Brilliance gets distracted again, and has to listen to the whole album before it can concentrate. Then Arcane Brilliance's kids come in the room and Arcane Brilliance plays with them for awhile. Lunch approaches, and Arcane Brilliance needs to get the column up. And, that, loyal readers, is a preemptive apology for any inaccuracy, inconsistency, misspelling, and grammatical eror that may follow this opening paragraph. Sorry!Before we begin, let's get a couple items out of the way.First: In case you haven't gotten it yet, or weren't aware, today is your last day to obtain Polymorph: Rabbit, at least during this calendar year. This is purchasable from the Noblegarden vendors for the low, low price of 100 Noblegarden Chocolates (it's only visible on the vendor if you're a Mage), which shouldn't take very long to obtain if you put your mind to it. Noblegarden ends tonight at 11:59pm server time, so even if you have no interest in the rest of the holiday, don't miss out on this little Mage-only perk.Second: Mirror Images aren't stupid anymore! Yes, when the PTR for patch 3.1.2 went live, the patch notes included one tiny note for Mages, but what a note it was. Your Mirror Images will now attack only the target that you've generated the most hate from, instead of targeting whatever shiny object happens across their fields of vision first. In addition, they'll no longer break CCs whenever they feel like it. I've tested this out a bit, and I'm happy to report that it seems to be working as advertised. Rejoice, my fellow Mages: our copies are no longer ham-fisted, drooling, mouth-breathers. I'm giddy.And with the news and notes out of the way, we are free to move on to this week's topic: PvPing as an Arcane Mage.
Ask a Lore Nerd: Life and Death
Welcome to Ask a Lore Nerd, where each week blogger and columnist Alex Ziebart answers your questions about the lore and history of the World of Warcraft. Ask your questions in the comments section below, and we'll try to answer it in a future edition. Today we're fielding a lot of questions on the Light and the Shadow, and Life and Death. I don't know why, really, that's just how things happened! Trends like that are always fun, like the week or two where we had nothing but dragon questions. It makes picking out themes really easy!Emorich asked... I was under the impression that C'Thun wasn't dead. I thought we simply stopped him. After all, we were attacking one of his eyeballs, hardly a vital organ. Is Kil'Jaeden dead too? I thought we basically just pushed him back through the portal and now he's really pissed.
Undocumented Arcane Mage changes in patch 3.0.8a
From the first moments that the servers came up today there were unconfirmed reports of an undocumented Arcane nerf to Mages flying around. Not so long ago, those reports were confirmed via some commentary on the issue from Ghostcrawler.There were some changes made to how Arcane Barrage, Arcane Missiles, and the Arcane Blast buff interact to prevent a fun little trick that was being used to get the most out of the buff. Second, the Arcane Blast glyph received a flat nerf, losing 2% damage per stack. Unfortunately, along with those changes came a potential bug to that glyph. Arcane Missiles may not be receiving the additional damage bonus at all.Overall, these aren't terrible nerfs, and probably should've been expected at some point. Arcane Mage is one of the class/spec combos pulling far, far ahead of the competition, so some changes had to happen eventually. Probably the only real issue here is the fact that once again, there should have been some documentation beyond hoping Ghostcrawler bopped onto the forums to confirm or deny.
