Feedback:User/Tennessee Ernie Ford/Easier reporting of bots / phishers / RMTs
Easier reporting of bots / phishers / RMTs | |
---|---|
User | Tennessee Ernie Ford |
Categories | Resolved feedback |
I think this is a good idea, but I don't think ANet is ever going to consider it for GW1. resolution = withdrawn .
|
Easier reporting of bots, phishers, and real money traders[edit]
Background[edit]
Currently, if a suspected bot, phisher, or real money trader (B/P/R) leaves a district, the in-game reporting tool, /report becomes useless; filing a useful report will take eight to fifteen minutes. This discourages honest players from reporting and deprives the relevant support teams of critical information needed to cut off the tentacles of B/P/R networks.
The goal is to reduce the total amount of time spent reporting allegedly criminal actions to less than 3 minutes.
Update to /report emote[edit]
When /report is used on a character name that exists in the database, but is not active in the district:
- immediately create a "report code" that stores the outpost/district/time to speed ticket generation (see below)
- replace the current, cannot report message by opening the default browser to guildwars.com's new information page on reporting (see below)
- on that page, include a link to a new reporting tool
New reporting tool[edit]
This reporting tool works together with Ask a Question, but is designed specifically to speed report generation. Selecting, Report suspect activity from the question type pull down offers a new series of questions. Instead of asking for information about the operating environment of the reporter, the questions ask about the suspected character and their activities:
- Report code (see above); ideally, this automatically generates the following information for the ticket
- Outpost name / District
- Time and time zone
- Anything else that ANet would find valuable to grab as a snapshot
- Suspected activity [pull down]: Bot, Phishing, Real Money Trading, Other/Several
- Suspected character name
- Text from suspected character. [short message field < 255 characters]
- Other details [long message field] (same as current Ask a Question functionality)
- Screenshots if relevant (same as current Ask a Question functionality)