Frost wands not freezing Viscidus

Guess I better get back to gnomeregan. Left my wand in there.

2 Likes

Go to DM:N. Cho’rush has a better wand.

Damage is irrelevant, a wand with 1.4 speed doing 1-2 dps is better than the Cho’rush wand doing 68-127 damage at 1.6 speed for this fight.
All that matters is hitting him with frost abilities in order to freeze him as quickly as possible during that phase of the fight.
Farming the wand in Gnomeregan can be a pain though, so just get the 1.5 speed wand from AV, or the green 1.5 wand from Desolace quest.

It’s much, much more than 20. I ran it on my shaman for xmog and it took several dozen frost shocks. It was a while ago, but I’d say it could’ve been over 100.

Activision would pay them peanuts anyways. Hard to focus on finding bugs in a game when you can’t afford to eat and pay rent at the same time.

you might be on to something here…

Who or what time traveler did you know at the time that ran a logs website for WoW back in 2006, and/or proivided you with an addon that gives anything close to the level of information that you’re implying?

Elitist Jerks - otherwise known as the website run by the current WoW Game Director Ion Hazzikostas - not full logs that we have today but they analyzed EVERYTHING

2 Likes

Thank you for an actual useful response from a GM. You are superior to your peers sir.

Have to ask, why was the ability to freeze him with wands removed in 2008? Was there a behind the scenes change that affected how wands worked or was this a deliberate change for this encounter?

Legitimately curious, it seems like an odd thing to change, especially after the boss lost all relevance.

Everyone is using wands, even the mages. The description of the video: “Server first kill of Viscidus in the Temple of Ahn’Qiraj with a 40 man raid. By The Last Watch of Turalyon EU. Note that this kill was particularly difficult for an Alliance guild during classic WoW because of the lack of Shaman with Cleansing Totems.”

Was there literally no internal testing for AQ? These arent minor bugs that are hard to miss or something.

No one casted a frost wand on viscidus at blizzard?

Same with the later anubisath having literally ZERO of their abilities for some guilds.

No one pulled this trash internally at blizzard?

I know the PTR AQ40 was kept hushhush for some reason, but these are really simple easy to see bugs that took players ONE RAID through the dungeon to find…

1 Like

I visited Elitist Jerks on the regular. They did not have logs or provide addons anything close to what we have today. It was more a theorycrafting hub than anything else, but OK.

Glad you are too lazy to put up a PTR for this kind of stuff.

1 Like

never said that they did - however they did discuss anything and everything under the sun as far as boss strategies

Doesn’t really matter, does it? People remember using frost wands, contemporary videos show people using only frost wands, Blizzard comes out and says “oops we changed this in 2008; frost wands were supposed to work and now they do again.” Problem solved.

1 Like

My question was:

Your answer response was:

So if your goal was to completely ignore my actual question to answer your own question with a downright falsehood, good job. ElitistJerks, in reality, did neither of the things I asked about. I would know as I was a frequent visitor. Talking about stuff in-depth =| logs and detailed combat log addons.

Also mentioning Ion does nothing for me, the dude is responsible for much of the current absolute ruin of the game we are playing right now.

If you’re gonna cite anecdotes from 2006 WoW and say “We checked out logs”, be prepared to back that up with actual credible citations because anyone who actually played back then knows that stuff didn’t exist.

go outside and get some fresh air friend - clearly you need it

ps you forgot to bold the most important part of my original response:

"but they analyzed EVERYTHING"

1 Like

Whatever you say boss~ :smiley:

Yes, this is bugged since at least sometime in Legion and I am pretty sure that I filed a bug-report for that back then.

Does that this will be finally fixed for Retail as well?