Ritual of Summoning is actually still broken [Updated]
by Adam Holisky 
Jan 27th 2009 at 2:34PM
Ghostcrawler posted last night that Ritual of Summoning would be fixed today. Nethaera posted small, but important, patch notes saying that it had been fixed. "Ritual of Summoning no longer has a 2 minute cooldown and will now function as intended."
However people are reporting that it still isn't working correctly.
Ghostcrawler now comes out and says that it'll be fixed sometime later today. "We are still on target to get this fixed today (Tue, Jan 27). I did not mean to imply that it would be fixed when the servers came back up."
Left hand, let me introduce you to right hand. Right hand says things like "We'll fix this today." Left hand says things like "These are the patch notes for this patch, which is now live." Right hand should tell left hand that not everything is live just yet, and update the patch notes accordingly.
Now that I got my tenses all screwed up, we'll update when Ritual of Summoning actually is fixed.
Update: It is now fixed, for real this time.
Filed under: Warlock, Patches, News items
Reader Comments (Page 1 of 4)
joggoms Jan 27th 2009 2:38PM
Huh.
paul.marsico Jan 27th 2009 2:44PM
BWAH hahah
Pandemicus Jan 27th 2009 2:41PM
I'm considering re-rolling. Once again locks have been put on the backburner. I'm so ridiculously tired of this.
Jason Jan 27th 2009 2:48PM
All I'm using my Warlock for (my former main) is to farm Chilled Meat and level his Tailoring skill with the Frostweave my other two characters in Wrath content pick-up. I'm actively leveling my Mage who used to be a bank alt.
uncaringbear Jan 27th 2009 2:54PM
Wow, that is exactly what I'm doing too ^^
My lock has been pretty much retired after I had leveled him to 80, and maxed out his tailoring. He is pretty much a glorified bank alt now. Now it's all about my mage and DK. Two classes that are actually fun to play and not treated like dirt (not counting the DK nerfs in 3.08).
SnippyMcPhail Jan 27th 2009 3:03PM
I parked my level 70 Warlock in Ironforge as a guildmaster with a four tab bank.
... she's also wearing full Tier 1 just because!
I so have moved onto a mage!! ...well my second mage... w/e I've moved on!!
trombone Jan 27th 2009 4:00PM
My lock is still 70 & parked in IF as a DE mule.
Playing my Boomkin and loving it.
Zamboni Jan 27th 2009 4:51PM
Mine made it to 80 and ended up parked as an AH mule. Rerolled a Hunter and dragged my poor Moonkin out of retirement so I could actually get invited to instance runs.
My Magoo Jan 27th 2009 5:26PM
You should have several level 80's anyways.
Precisely for this reason. Blizzard keep nerfing/Op'ing a range of chars.
Locks used to be OP to hell remember? Hunters were the king of DPS without trying.
DKs are the new OP as are pallys.
Swings and roundabouts. Play the market. Etc.
rosencratz Jan 28th 2009 7:25AM
I'm still enjoying my lock. I'm affliction though and enjoy the complexity so it's not so bad, it's not great that were' a bit under powered where others aren't and all the issues we have but... well it's been far far worse than it is now and i weathered all that too and untill playing the clas becomes painful i'll keep soldiering on, i did after all choose the class because i enjoyed it, not because it was Fotm.
For me at least though being a lock hasn't reduced my personal chances of getting invites to runs and raids so far and i can still DoT up and draintank around 10 level 80 mobs at a time when farming solo content so and now dots tag mobs too?... meh... beats the hell out of the old days.
Sneekr Jan 27th 2009 2:44PM
This is why Dev's don't like to promise anything. Should they have fixed it? Probably, but don't hang on their every word.
Adam Holisky Jan 27th 2009 2:46PM
I'm actually okay with hanging on their every word.
I'm not okay with one part of Blizzard saying one thing (community team, "this is fixed now") and the one part saying another thing (dev team, "not fixed yet, will be fixed later").
Communication is so damn important in this day and age, and I think that Blizzard is failing hard core in respects to their more dedicated fan base.
Antonia Jan 27th 2009 2:58PM
@ adam
The fact of the matter is that he's the developers face to the rest of the world.. He's also on the forums CONSTANTLY so he's got to have a pipeline directly to Nethaera also.. there's no reason a few words that are ,seemingly, as important as those should have been missed or forgotten to be said ANY WHERE unless it was either of their faults..
GC's comment feels more like an "oh crap the glue didn't hold" comment then any thing else
Adam Holisky Jan 27th 2009 3:00PM
I think that pipeline needs to be tripled in capacity.
Utakata Jan 27th 2009 4:15PM
I suppose they could wait...and fix it in the next patch like they did with the Orc shoulder bug back in TBC, which will be months for anyone sees a fix. Or the Blink and Vanish bugs...that have been with us since the games release and hense, never see it really fixed. But it should be reminded of short memory WoW Insider writers...that least they are trying to get to it today. Instead, there's a phrase where I come from, "take a pill."
I'm not try'ing to be a fanboi/grrl...I'm trying t put things into perspective as an over 3 year'd player who seen my fair share of patch day bugs. That is, there's nothing new here to see folks, now run along.
Sneekr Jan 27th 2009 5:35PM
Just to clarify, he said they would try their best AND there was a slight chance it wouldn't happen. Emphasis on the slight chance.
MechChef Jan 27th 2009 2:45PM
We have a word for this where I come from: "Fail"
Elmo Jan 27th 2009 2:44PM
Blizzard never releases anything 'till it's absolutely perfect.
oh wait...
a patch of 4 bugfixes and they still manage to screw it up.
rosencratz Jan 28th 2009 7:45AM
What did they screw up exactly? Just because wowinsider posts some overly dramatic articles on a subject we're all meant to forget what has actually happened?
"Assuming nothing comes up at the last minute", Ghostcrawler says, "[these] will be fixed tomorrow."
Let me repeat the important bit;
"Assuming nothing comes up at the last minute"
Blizz were non commital in the first place with these bug fixes AND at the end of the day we DID get them...
Hasteur Jan 27th 2009 2:46PM
Yet again we get the "Fail" roll from Blizzard. To help motivate them I am organizing a "Ritual of Summoning" strike. Yes, that means that no warlock do summons to illustrate to group/guild/pug members the seriousness of leaving this spell broken. Blizzard will make this #1 priority (even hotfixing it) if suddenly they get flodded with support tickets asking when the spell will be fixed.