- Type
- Bug report
- Status
- Implemented
It’s not just you. I am not sure how that happened.
It would be better if you made a support request because then a scam resolver could prefix it to the appropriated prefix.
It is likely that the scam resolver(s) missed prefixing it.
I only saw like 3 and assumed there could be more.
I didn't want to sound like I was the only one when I didn't check that.![]()
Indeed. Creating a ticket is the best way to go about doing this.There are 356 pages in the scam report archive (from what I can see). It would simply be a huge waste of the Scam Resolver team's time going through each page and correcting this for every user. If there is a scam report against the user and it does not have the proper prefix set, I recommend the user create a ticket and link the scam report(s) that need correcting. This would be a more adequate solution as the users being directly affected by this mistake can request this to be corrected rather than us going through hundreds of pages to find the scam reports without a prefix. Mistakes happen and people forget the small things. Please create a ticket if your scam report does not have the proper prefix.
