I think I did the boss 2-3 times on a few of my toons. I thought the boss was bugged and wasn’t giving loot for the kill lol.
This is the problem with Blizz making a blanket vague statement about punishing people for exploiting bugs.
I have 32 Level 120s. I killed Ivus on all of them.
On at least 1 when I died, I released, ran back for what feels like 2 minutes, and didn’t get credit for the kill for the WQ, but did get 59 gold. I then joined another kill attempt, did get credit for the WQ kill, and don’t think I got the 59 gold.
There was at least another attempt where the WQ just didn’t count, and again, I killed it again so that it did count. Did I cheat twice or was it just buggy twice? Did I take advantage of a bug, by trying to kill it to actually get my reward?
Stuff like this, Blizzard should just disable the mob/item once they discover a bug, hotfix it, test it, then make it available again. The problem that I see is that they just dont have people testing it, and they dont have people able to dynamically fix errors that are shown to them by players and what testers they do have.
1 Like
I love how alliance players act like they would have taken the moral high ground and not spammed the warfront had they started with it instead of the horde. They would have gladly waited until 325 to queue for it since they knew BEFORE THE RESTRICTION that doing it prior to that would have been “unfair”. Totally.
1 Like
Sure, you can have the same bugs we did where a lot of us didn’t get a bonus roll at all, ever. Flip a coin, heads you get to use all your rerolls in one day. Tails you don’t get to use a single reroll. I unfortunately rolled tails and (even though I had 5 reroll tokens) never got a single reroll option.
But of course you guys never want to talk about the second one and it’s always “horde bias” and you just disregard the fact that a lot of us were completely screwed from how buggy this bosses loot was. Anything that helps push the “horde bias” agenda is a big deal…and lets just ignore anything that doesn’t push that agenda.
1 Like
Let’s also ignore the fact that you started the warfront without needing a contribution phase (which horde did not get to skip). But yeah, horde bias.
I’ve heard of this bug, due in large part to the fact that when I made a premade group to kill the world boss, people asked me to do it multiple times. I refused, knowing this was likely a bug. So while I do hope the players who either encouraged others to exploit or exploited the bug themselves are actioned severely, I WILL contest the suspension if I’m actioned…and if I have to take my case to court to prove my point…SO BE IT.
1 Like
Let us know when it happens. Remember the screeching alliance who claimed horde got mythic 15’s first because of what they thought was super easy gearing from war fronts when they had done, at most, 1 warfront? That’s exactly what you’re doing.
Good luck with your court case goals of 2018.
1 Like
2019, you mean. And I’m about to get on the phone with my lawyer now…
That joke must have flown over my head
No, you should be fine. Anyone that only killed him once or twice are not their targets.
2 Likes
Then a new player can appeal. A player who has been playing over a few years though, it is pretty hard to make a case they didn’t know this wasn’t working right.
I mean taking away their items is enough, but a suspension knowing your company that you’re representing isn’t looking well? I’d be satisfied if they don’t return so you guys can sweat more bullets. Yeah sure they kept getting items, but how long 8.1 was in the ptr and your company has the option to remove items? Then there’s no need for a suspension on something small as this. Anyways cheers to this company’s destruction or perhaps handle the situation better than thinking suspension solves everything when it’s your own mistakes. Amend your mistake, but that’s wishful thinking.
1 Like
the thing i find hard to wrap my head around is how they botch up a world boss like this.
how many world bosses have been released in the past without this sort of issue? a few dozen by now. how something like this slips past QA testing is beyond me.
the fact that yet again something hits live servers with an unintentionally positive benefit that only effects horde really makes me wonder.
there is either a hidden bias or incompetence … and i don’t know which is worse.
If you develop ASP or other shared infrastructure, and someone violated the terms of use, you bet you suspend and punish them. Or, you’re a bad developer. Take your pick.
So what about the hivemind ban? There are hundreds of group selling the bug hivemind run
aren’t they bad because they let this work in game without jumping through some kind of hoops to get this to work?
Meh if the loot and titun residium is removed, all good. I mean a short suspension for the ones who did it an absurd amount maybe, but I don’t want anyone losing their account over it or anything.
2 Likes
damn, i wish i was more aware of this kind of stuff ![:wink:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/wink.png?v=6" ":wink:")
i looted… nothing from him as usual but yes i saw some smart guys who seemed to be very, very happy on the first day
If you withdrew $100 from an ATM, but it mistakenly spit out $1,000, would you feel entitled to keep it?