dude it’s not up to you to play blizzard CS, in fact that’s a bannable offense, now what you should do is just let blizzard do their job (lol) and either confirm this is a bug or that this on their reference client and as such will remain unchanged.
Also weird to see retail chars with post #s that indicate they live here do blizzard’s job for free (and very poorly) after news has come out that blizzard doesn’t pay their employees in fair wages but instead in game time, imagine wanting to work for a company like that, but worse yet, imagine attempting their job badly for free
edit: and since you seem like the debate me kinda nerd I’m just gonna say for argument’s sake that no, we don’t know if this is on the reference client or whether or not even if it’s on the reference client if this is or isn’t another one of those snapshot bugs like c’thuns eye beam was, customers are not their QA team, nor are they the devs. And with the huge amount of undocumented changes happening since AQs release there’s no way of telling whether this is true to vanilla, nor is that our job, that is blizzard’s job, people here are trying to make blizzard aware of a bug (or maybe a vanilla feature) but it’s not up to the customers to determine that, that job lies with blizzard.
and that also means that job does not lie with you, stop doing it badly and for free, it’s their job to confirm or deny these things and throw them on the >notabuglist< which btw hasn’t been updated since uhhh end of last year? also the EU forums have no bugreport subforum so you are just going to have to deal with these things getting posted here my dude
Those are target changes that result in movement. That’s not what we’re seeing. What we’re seeing is that the boss randomly decides that he’s in fact no longer a ranged mob. He’s now melee. This is very obviously a bug and should be a high priority fix. In my experience the bug only happens in 1/3 IDs, so you probably won’t have the same issues next reset (or it’s a fresh bug starting somewhere after sunday).
I’ll concede that to an untrained / inexperienced / unaware eye they look similar, but I assure you they’re radically different.
How can you be so sure about it being a bug? He was also slapping warrior tanks with melee in vanilla:
It should be pretty easy to find more examples if you want to.
I’m sure it also happened to warlock tanks in vanilla, but that would most probably have resulted in a wipe and the recording not being published.
What makes you think it’s ID related, and not just complete RNG?
All the initial wipes of the people the op links to are due to not being able to handle the teleport/tank swap resulting in their warlocks being killed by Vek’nilash. None of the Calamity warlocks gets hit by vek’lor’s melee until their third pull, after over 15 minutes of fighting the boss. In the North raid no warlock tank gets hit by Vek’lor’s melee until their fifth pull, after a total of 17 minutes of fighting. It also doesn’t happen during their next two pulls.
The op makes it sound like Vek’lor’s melee made cost him loads of consumables, while it is in fact his own personal mistakes causing most of the wipes in the public logs.
When exactly did this “bug” start?
Here is an example of it happening on wednesday, during a fairly early kill. https://classic.warcraftlogs.com/reports/dpkxBMG8aQYbN7c6#fight=26&type=damage-taken&source=16
That sounds like confirmation bias to me, until someone can provide logs where it happens frequently before a soft reset, and not at all after. In the available logs for the guilds the op provided clips from it only happens during a single pull for each guild.
They got 1 melee hit at the beginning of their 10 min kill after soft-resetting, where they got 9 (3 min), 2 (11 min), 3 (3 min), 2 (2 min) and 9 (3 min) on their earlier attempts.
The supposed “reset fix” is between their last attempt and their kill.
And the reset clearly didn’t remove the issue. Or, are you now saying that resetting reduces the frequency of the issue? The op refers to people experiencing this once in their public logs. How would resetting help them?
Your guess is as good as mine. It’s clearly bugged af and random as hell. We’re currently brainstorming potential ways of preventing the bug from occuring. Multiple raids have reported success after soft-resetting the instance. Some raids have had zero issues ever. Some thought it was because of being too close, others thought it was because of being too far away. Some even thought it was caused by being somewhere in the middle range distance. Some thought it was caused by being on the stairs…
So. After we’ve cleared it today it might be fixed.
Vek’lor wasn’t chasing down the warlock but they weren’t standing on the stairs eather and so I’ve heard that was the cause. The only melees Vek’lor was dishing out was a slap to the warrior tanks right after teleport. And it was infrequent aswell one of them took overall 6.3k the other 3k from him as melee.
What we tried on tonights clear that seemed to work, as in we did not see the running towards and going melee on the warlock behaviour, was that not a single person went above the highest step on the stairs, going on the platform seems to be what causes the odd behaviour.
Last week we had people coming and going on the platform area during the fight and we saw the running into melee behaviour several times.
This week we had zero people going up above the highest step on the stairs and we did not see him do it even once.
Only 1 melee hit from a messy swap but thats it.
Either this fixed it or Blizz made a stealth fix to the fight.
More kills on the boss will tell us.
If it does not happen again, after happening so many times last week, one would not be able to really call it random.
Although it is difficult to see, I believe I spot someone up on the platform at some point on all of those videos posted in this thread.
