This was in vanilla. You can disagree with the design choice, but it’s not a bug because it was an intended interaction.
1 Like
It was not tho. Not in this manner. The caster did NOT randomly stop casting to go melee the warlock who was out of melee range.
1 Like
god forbid a wipe. i can’t believe people are complaining about this. Seriously?
I’m honestly thinking how this lazy mentality came about. You obviously have the people who want their instant gratification. You then have people from private servers who want to feel like they “beat” a game they were terrible at 15 years ago. They want things easy so they feel powerful. They are the same demographic. Both were kids 15 years ago, just forked in a different direction. Both want things quick and mindless for different reasons.
But either way, everything points to retail. We have retail today, because that’s where everyone’s the mindset is. Activision didn’t kill WoW. The people did. Activision actually did it right. That much is becoming clear and clearer every day.
1 Like
There are plenty of videos from both vanilla and tbc of this happening.
I’m tired of repeating myself. Yes, it did happen in vanilla. But not in this manner. Not randomly and for no reason.
1 Like
Yes it happened the guilds in Vanilla just figured out how to control it and it’s something that’s still clearly gone over your head.
2 Likes
Yeah, the way to control it is to stay out of melee range. The issue is that he still randomly runs to and melees the warlock while out of melee range.
You mean the same way every other boss can run up to someone out of melee range and melee them when they are the highest threat target?
And for the last time, it’s not random, it’s completely predictable and preventable.
1 Like
-
There are no other bosses that are tanked this way in the game so far.
-
Name one caster boss or mob that will randomly run up to its ranged target and melee it even when it isn’t out of mana. PS: Shazzrah doesn’t count because randomly dropping threat and blinking into the ranged groups is part of its core mechanic.
Name one caster boss or mob that will randomly run up to its ranged target and melee it even when it isn’t out of mana. PS: Shazzrah doesn’t count because randomly dropping threat and blinking into the ranged groups is part of its core mechanic.
1:49
Are you seriously sending me a link to an end-game TBC raid? You cannot possibly be serious. I’m obviously talking about vanilla.
1 Like
What other pure caster bosses are there in vanilla raids?
1 Like
Its worked liked this since the raid was released, it doesn’t need to be changed.
The castery twighlight hammer dudes are the same. You cna interupt them with earth shock and they can meelee without casting for a good 5-6 seconds before they remember they’re casters.
Exactly.
10word
All the actual server and world first vanilla guilds didn’t use a warlock tank. It wasn’t a strategy that was actually realized and utilized until a bit later.
They had a warrior spam demoralizing shout on Vek’lor with all ranged focusing on killing bugs instead for this very reason, so saying that “this shouldn’t happen this way because we don’t use this strategy on anything else” is just a flat out false statement. There are other ways of doing it besides using a warlock tank. Using a warlock tank only becomes optimal if you actually know how to transition and position properly, and if Vek’lor if still meleeing your warlock or running up to him then your guild clearly doesn’t
There are plenty of counter examples of mobs that happen to be primarily casters that will also run up to a high threat ranged target and melee it. It’s not a bug it’s completely intended.
I think his post might have gone over your head.
Particularly your insistence on Vek’lor being a “pure” caster boss.
If the melee swing is not intended/a bug, then it would be a FIX to change it.
Respectfully, I think you don’t know what you’re talking about. 1.9 was released in January 2006 and there are records of people warlock tanking the caster boss as early as April. To say this is a relatively new strategy betrays your lack of first-hand knowledge.
That being said, I never said that Vek’lor was a caster-only boss. He can definitely melee. But he shouldn’t be going out of his way to melee his target unless they are within melee range. Vek’lor would only melee the warlock tank if he was moved close to the warlock; he did not interrupt his casting and run towards the warlock specifically to melee him as we are experiencing now. The issue is not that he can melee, it’s that for some reason he will randomly melee even if the person that has aggro is not within his melee range.
Guilds were already past Twin Emperors before April 2006…
if you’re gonna tell people “I think you don’t know what you’re talking about” can you actually be bothered to look up actual dates so you don’t make a fool out of yourself?
Nothing about Vek’lor’s behavior has changed sinced vanilla and I know this because I am the warlock tank for my guild and I have been melee’d a total of 0 times and have caused vek’lor to run out of position 0 times on complete 1 shot kills. Guilds cleared this hours after the gates opened with no problem.