The enemy player appeared to be a bot. I wrote down his name, but when I clicked on his nameplate he would disappear from view. There doesn’t seem to be a way to report someone unless you are able to click their nameplate.
There really isn’t. You can always send an email to hacks@blizzard.com with your suspicions, but the prefered method in right clicking the nameplate.
1 Like
You can also just open up a normal ticket. Also, you can target them and right click on their portrait.
Sending up normal tickets isn’t really something that’s needed for reporting botting - they’ll generally just recommend you report via the nameplate instead.
A GM isn’t gonna investigate someone suspected of botting, Blizzard has a team for that. That’s why I posted the hacks email.
I don’t think Blizzard ultimately cares how you report suspected bots. They offer that advice because it’s quicker and easier for us to report that way, but sometimes you lose the bot before you can target lock them and such.
Blizzard cares because tickets dont go to the right person right clicking sends 100x more info then the email or a ticket of a suspition.
3 Likes
They’ll route the ticket to that team.
They do. Right Clicking tells Blizzard a lot more than “Hey I think this is a bot” It captures a snapshot of the pertaining logs on that character among other things. Emailing hacks just lets right team to know that there are bots running in that area.
A player ticket is not gonna offer much information on a bot than right clicking on them. it just clutters the queue.
2 Likes
And sending an e-mail from Outlook or whatever will give them that information?
Now you are getting argumentative…
2 Likes
No, just pointing out your inconsistency.
I was right, you are not here for information, you just wanna start a fight.
2 Likes
The only incorrect information is the ticket blues have said time and time again that tickets arent a proper way of reporting either right click or use the email. GMS arent go betweens.
3 Likes
That might be your perception, but perception does not = reality. The OP already said they could not right click on the name plate so I told them the character portrait in the target frame
And I have not seen posts that say to send to that e-mail. The web ticket page, conveniently located at https://us.battle.net/support/en/help/product/wow/197/220/solution only says the right-click thing.
Oh… and while using Google to try and find a post I stumbled upon this gem…
https://us.blizzard.com/en-us/submit/hacks.html
I did. Name plate is different from target portrait. Name plate is what appear over the player. Target frame is the box that pops up when you target something.
Try looking at the 2nd post malfosa.
2 Likes
It can actually. Because you can put that information in yourself. Using the in-game feature allows investigators to Mark exactly when and where it happened. Forwarding a report from you does not. Generally speaking it’s not a GMs job to forward. ambiguous reports. " Player x us a bot. Ban him" , doesn’t help. The ingame feature provides the needed information.
Conversely if you send an email.to.the hacks team, you’re more inclined to flesh out the details.
Blues here have explicitly stated to use the email if the ingame feature isn’t viable.
4 Likes
Yeah, that sends an email to hacks@blizzard.com It’s just a handy dandy web form.
3 Likes
It’s not a perception. It is a reality. Blizzard representatives have stated so.
And your last link link? Has been around for years. We all know about it. Old news is old.
You’re just here to troll and spread misinformation. I’ll be reporting you for such.
The only Blue Post I’ve been able to find was one from Diablo III that stated the e-mail was for reporting exploits you discover and can provide the steps to reproduce.
The nearest one I could find was from Vrakthis (The bot problem - #13 by Vrakthris) and he does not mention the e-mail account either… just the right-click in game and the web form. If that’s where the form goes to, cool.
How do you know that? And that’s a legit question. I looked at the code and couldn’t find where the handler was submitting it too. It’s probably buried in the JavaScript but I didn’t look too hard I’ll be honest.