You’re in denial.
And refusing to be informed.
And enjoy the report for inappropriate behavior. Gotta enjoy the weekly ban.
1 Like
Sure.
Lets replace all your spells for macros that hit only your focus target.
Super natural gameplay.
And during a fight you will never target the boss. Just press your spells without even targeting the boss. But only start doing it after like 150 attempts or so.
Completely normal.
Right, he’s not doing anything that would warrant a ban.
I don’t watch it but I keep up with the race because it is some of the only original content about WoW out there. The copy/paste tier list, rotation guides and other guide content on Youtube is so uninspired. Most of them just copy MMO Champ/Wowhead verbatim.
Some of the more casual stuff can be fun to watch but there seems to such a desperation to explain away any mistakes Blizzard makes as the fault of the players. I can only take so much boot licking.
I agree that the way RWF is done is sad. All of the custom WA’s, the split loot runs, the simps and the exploits.
I thought you had left?
ii. License Limitations. Blizzard may suspend or revoke your license to use the Platform, or parts, components and/or single features thereof, if you violate, or assist others in violating, the license limitations set forth below. You agree that you will not, in whole or in part or under any circumstances, do the following:
- cheats; i.e. methods not expressly authorized by Blizzard (whether accomplished using hardware, software, a combination thereof, or otherwise), influencing and/or facilitating gameplay, including exploits of any in-game bugs, and thereby granting you and/or any other user an advantage over other players not using such methods;
You’re welcome.
Good for him tbh.
Spellslinger is functionally awful. He made a tradeoff; sacrifice the dot damage in order to ensure stacks don’t arbitrarily fall off. It’s not his fault the spec is so badly designed that it doesn’t even need that dot damage to remain competitive.
So now that apologizers are gone.
I think it is pretty obvious that stopping the mage in question from streaming their viewpoint shows that at least some other members of the guild knew what was going on.
And did he have help setting it up?
I think there is enough there that a win now would have an asterisk by it. Although Blizz is ultimately responsible for this by implementing systems they barely understand without outside help.
Then again maybe the mage in question was a loner in this. You would think that as knowledge as the raid leaders are for this guild that they would notice. But there are a lot of moving parts.
I agree with part of what Splints posted that spellslinger is functionally awful.
1 Like
I still don’t think he’s doing anything “abnormal” in a bannable sense. I don’t elevate it to “Cheating.”
I put it on the same level as finding a lucrative hyperspawn that always dropped excessively high raw gold. If you farm this spot and acquire 100,000,000g, are you abusing a bug while playing normally? You are certainly playing normally, but you also definitely benefitted from a bug.
I don’t think farming a hyperspawn is bannable. Likewise, I simply don’t think using a macro to abuse a spell bug is worthy of being bannable, especially when it isn’t disrupting the game for others.
There’s barely anything to set up. Have macros for all hostile abilities to cast @focus. Done. Takes like 2 minutes tops.
It isn’t some kind of elite hackerman setup. Most competent healers already know exactly how to macro something to not cast at target.
It is a bit more than one or two simple macros but ultimately the blame goes to Blizzard for letting the same people that work on RWF alpha and beta test for them instead of hiring a real QA department.
I think the bannable offense might be in hiding it knowing they could now down the boss and not wanting other guilds/Blizz to see the exploit they were using.
It was a bad judgement call.
1 Like
How isn’t that abnormal what he did.
He even “faked” his UI to make it look like it was normal, only people noticed that he was using focus target and not the target itself.
It is not normal. Unless of course you are completely new to World of Warcraft and has absolutely no clue how to play, then you wouldn’t understand the difference.
It would come down for one explaining to you the normal and then saying what he did, so you could understand that it was not normal.
That would be a normal outcome.
An abnormal outcome would be someone saying “I don’t think it is abnormal”.
It is not like he was simply playing normally and the bug was happening and it was inevitable.
He went there, did a lot of things to make it happen. Went out of the way to do that.
1 Like
except it was reported over 40+ times and it was ignored.
Also who cares anymore you aint doing RWF nore does it matter.
Letem kill it so crap gets nerfed mythic+ example crap is busted look boards on healers and tanks. its one sided due to tuning
While I do think it’s exploiting I also think this is on blizzard for not fixing it after being told in beta.
If blizz appears to not care than something can move from “exploiting” to “clever use of mechanics” real fast.
QA departments are pretty much getting phased out. Blizzard isn’t developing critical software such as pharmaceutical instruments/Bio-medical devices. Where failure = extreme fines or legal battles. They can have a critical fault, and close down for a few hours or extend maintenance. Or, have guild banks wiped and nothing happens. Its an “oops”.
That’s also why they heavily rely on PTR.
It stems from agile forcing developers to be their own QA. While tech “start-up” culture makes everything development wise a priority due yesterday. I say that, because every large tech company uses the word “start-up environment” now even though they’ve been in business for 30+ years.
It’s not exploiting to choose one type of flask over another.
It’s not exploiting to pick good talents over worse ones.
It’s not exploiting to lose dot damage in order to do more direct damage.
You make a great point. It is hard for me to believe that the raid leadership didn’t know about it either.
It is not a question whether it is a bug or not, since he knew it since beta and reported it.
But I wonder what is this phenomenon happening here:
- reports a bug in beta.
- It doesn’t get fixed yet.
- exploits it during race to world first event
- People say it is not an exploit of a bug
I don’t really get it. It is literally the definition of exploit and knowing it was a known bug already makes it 10 times worse.
4 Likes
It’s not a bug. The talent was designed that badly.