(As I am still in the process of patch downloading, this is currently being posted from my phone. Hence the lack of pictures from one of the more...amusing bugs)
Oh Patch 5.0.4. The pre-expac patch. Since this is my first pre-expac patch, I thought it would be exciting. Oh how wrong I was. I've slowly become accustomed to life without my melee weapon on my hunter, and I really haven't missed my relic on my DK or shammy. My hunter abilities make up for through loss of my weapons. Seeing my girlfriend go "WTF WAS THAT?!?" when Dire Beast summoned a massive spider on her druid during a duel caused plenty of giggles. Mostly because of how unexpected the result was! Finding out my shaman healer only had 100k mana was a bit alarming at first, but I can burn through my entire healbot rotation and only burn through 10% of my mana? And that's with the inclusion of Healing Rain into my rotation.
Out of all the toons I've checked out this far into the new patch, I have to say that the hunters finally got some really fun toys to play with. The aforementioned Dire Beast is so much fun to play with at a target dummy, and Fireworks is a cool vanity glyph. Every time I use it, all I can picture is something out of Mythbusters involving a compound bow and some sort of high explosives. Fetch would be a spiffy glyph to have as well. My druid comes in second for "NEW TOYS!" fun. I love stag form so much, and it suits him far better than the old cheetah form. The fact that he can carry people around on it after it's glyphed is a bonus. Plus Tree of Life now has a permanent Treant glyph. Despite being a Cata-baby, I can see what was so fun about running around as this crazy old man tree. And Blizz finally did something about that godawful seal form. The second I can get back on without crashing, Glyph of Orca will be my first purchase on my druid.
Then there's my shammy. Poor girl. If her totems weren't taken away, they were beaten beyond recognition by the Nerf Bat. Now my old buff totems function like auras, my utility totems are reduced to raid cooldowns, and I feel like I don't know who I am without them. Totems made us shaman unique in the vast pool of healers in the game. Yes, we had our situational CD totems in Mana Tide and Spirit Link. Now even my beloved Healing Stream is a situational CD, and no amount of totem catapults will make that better. At least our spells seem to cost less mana, to coincide with the new mana cap.
All the account-wide stuff is pretty nice too. My shaman can go around with the "Astral Walker" title, which feels like a far better match for her than "Destroyer's End." And once my DK hits 80, he will proudly wear his "of the Ashen Verdict" title as he flies around on his Bloodbathed Frostbrood Vanquisher.
But this patch isn't without its glitches. And this one seems to have them in spades, if the tech forums are to be believed. I've only witnessed two of these glitches. One is more hilarious than game-breaking, but I do hope they're fixed soon. The hilarious glitch causes all player characters to have no armor on their backsides. Needless to say, I've been seeing a lot more than I ever cared to. If I see one more saggy gnome butt, I will probably cry. I have attempted everything to fix this glitch, but no luck. Maybe it'll get itself sorted out soon. If not, I guess I'll have to learn to live with saggy gnome butt.
The second glitch I've had the dubious honor of encountering is the dreaded error 134. It causes random game crashing due to some sort of corruption an unlucky mpq file. Luckily for me, mine is more a case of my OS getting confused when my game tries to load something from the textures.mpq file, since my game is still patching. Basically, data is still being downloaded into these compressed mpq files, but Windows will read them as being complete. In attempting to bring up data that isn't there, the OS gets confused, can't figure out what to do, and a fatal error occurs in the form of error 134. I can only hope that this error won't affect my gameplay after the patch finishes downloading, since quite a few players are experiencing the same error with their world.mpq files. Scuttlebutt is that it could have something to do with these new cross-realm zones they're creating for the lower population servers, but that's just hearsay until there are new Blue Posts on the tech forums.
Obvious edit on 9/1/12 to include the insane glitchy fun of the nakedness!
My game hadn't quite caught up with my girlfriend's Vial of the Sands cast here, leading to this interesting pose.
Yeah, I don't know what went wrong here. But EVERYTHING was exposed there. This happened after one too many Error 134 crashes.
Oh Patch 5.0.4. The pre-expac patch. Since this is my first pre-expac patch, I thought it would be exciting. Oh how wrong I was. I've slowly become accustomed to life without my melee weapon on my hunter, and I really haven't missed my relic on my DK or shammy. My hunter abilities make up for through loss of my weapons. Seeing my girlfriend go "WTF WAS THAT?!?" when Dire Beast summoned a massive spider on her druid during a duel caused plenty of giggles. Mostly because of how unexpected the result was! Finding out my shaman healer only had 100k mana was a bit alarming at first, but I can burn through my entire healbot rotation and only burn through 10% of my mana? And that's with the inclusion of Healing Rain into my rotation.
Out of all the toons I've checked out this far into the new patch, I have to say that the hunters finally got some really fun toys to play with. The aforementioned Dire Beast is so much fun to play with at a target dummy, and Fireworks is a cool vanity glyph. Every time I use it, all I can picture is something out of Mythbusters involving a compound bow and some sort of high explosives. Fetch would be a spiffy glyph to have as well. My druid comes in second for "NEW TOYS!" fun. I love stag form so much, and it suits him far better than the old cheetah form. The fact that he can carry people around on it after it's glyphed is a bonus. Plus Tree of Life now has a permanent Treant glyph. Despite being a Cata-baby, I can see what was so fun about running around as this crazy old man tree. And Blizz finally did something about that godawful seal form. The second I can get back on without crashing, Glyph of Orca will be my first purchase on my druid.
Then there's my shammy. Poor girl. If her totems weren't taken away, they were beaten beyond recognition by the Nerf Bat. Now my old buff totems function like auras, my utility totems are reduced to raid cooldowns, and I feel like I don't know who I am without them. Totems made us shaman unique in the vast pool of healers in the game. Yes, we had our situational CD totems in Mana Tide and Spirit Link. Now even my beloved Healing Stream is a situational CD, and no amount of totem catapults will make that better. At least our spells seem to cost less mana, to coincide with the new mana cap.
All the account-wide stuff is pretty nice too. My shaman can go around with the "Astral Walker" title, which feels like a far better match for her than "Destroyer's End." And once my DK hits 80, he will proudly wear his "of the Ashen Verdict" title as he flies around on his Bloodbathed Frostbrood Vanquisher.
But this patch isn't without its glitches. And this one seems to have them in spades, if the tech forums are to be believed. I've only witnessed two of these glitches. One is more hilarious than game-breaking, but I do hope they're fixed soon. The hilarious glitch causes all player characters to have no armor on their backsides. Needless to say, I've been seeing a lot more than I ever cared to. If I see one more saggy gnome butt, I will probably cry. I have attempted everything to fix this glitch, but no luck. Maybe it'll get itself sorted out soon. If not, I guess I'll have to learn to live with saggy gnome butt.
The second glitch I've had the dubious honor of encountering is the dreaded error 134. It causes random game crashing due to some sort of corruption an unlucky mpq file. Luckily for me, mine is more a case of my OS getting confused when my game tries to load something from the textures.mpq file, since my game is still patching. Basically, data is still being downloaded into these compressed mpq files, but Windows will read them as being complete. In attempting to bring up data that isn't there, the OS gets confused, can't figure out what to do, and a fatal error occurs in the form of error 134. I can only hope that this error won't affect my gameplay after the patch finishes downloading, since quite a few players are experiencing the same error with their world.mpq files. Scuttlebutt is that it could have something to do with these new cross-realm zones they're creating for the lower population servers, but that's just hearsay until there are new Blue Posts on the tech forums.
Obvious edit on 9/1/12 to include the insane glitchy fun of the nakedness!
My game hadn't quite caught up with my girlfriend's Vial of the Sands cast here, leading to this interesting pose.
Yeah, I don't know what went wrong here. But EVERYTHING was exposed there. This happened after one too many Error 134 crashes.
OMG NAKED ASS!!!
ReplyDeleteI'm just glad they fixed that with that mini-patch a few weeks ago. Skin skirts and naked ass wasn't very fun to stare at.
Delete