If you’ve come across a bug, thanks for taking the time to report it. Accurate bug reports help improve the game for everyone. This post will walk you through how to do it the right way so your report doesn’t get overlooked or closed.
0. Always Use the Bugtracker
All bugs should be reported through the official bugtracker.
Please do not post bug reports on the forum. These posts will not be reviewed by the development team.
Additionally, bugs should not be reported in-game to developers or staff members. While they may be online, they will not be able to assist with bug reports directly.
The bugtracker is the official channel for submitting reports, helping ensure that every issue is properly reviewed and tracked by the team. We appreciate your help in keeping Return of Reckoning running smoothly!
1. Check if it’s already been reported
Before submitting anything, search the bugtracker using relevant keywords.
If the bug is already reported, don't make a duplicate.
If a report is closed, that means the issue was either fixed or found to be invalid. That doesn’t mean it was ignored.
If you have new information or proof that the issue still exists, comment on the original report instead of creating a new one.
2. Don’t use the tracker for support issues
Please don’t report things like:
• Trouble with the launcher
• Stuck characters
• Account issues
• Missing items
These belong in the support section on the forum or should be handled by GMs in-game.
Note: We do not restore missing items. If something disappeared, report the bug itself so we can fix the cause, but we cannot verify individual claims or reimburse lost gear, items, or crests.
3. Provide clear evidence
The more useful details you provide, the better.
Screenshots, videos, logs, and step-by-step instructions are incredibly helpful — especially for bugs that are rare or hard to believe.
4. Don’t bump tickets
The bugtracker isn’t like a forum.
Old tickets aren’t forgotten just because they haven’t been commented on.
Avoid posting things like "still broken?" or "any update?" unless you’re adding new evidence or helpful info.
5. If staff say it’s working, bring proof if you disagree
If a developer or staff member explains that something is working as intended and you believe it is not, please provide evidence to support your position.
Saying “I played that class for years on live” is not considered proof. Share something concrete that the team can review.
6. Don’t ask when something will be fixed
The bugtracker is not a suggestion box or support ticket system.
Please avoid posting comments such as:
• "When will this be fixed?"
• "Any updates on this?"
• "Please fix this ASAP."
If a fix is in progress or has been completed, it will be reflected in the ticket status or announced in the patch notes.
7. Use the correct names and keywords
To help staff and other players search for your report (and avoid duplicates), make sure to include the proper names for:
• Abilities
• Classes
• NPCs or monsters
• Items
• Zones or locations
Spell them correctly whenever possible.
8. Use clear English
Please write your report in readable English.
We understand that English isn’t everyone’s first language, but reports need to be understandable to be useful.
Reports written entirely through translation tools like Google Translate may be closed.
9. One issue per report
Only include one bug per ticket.
Multiple issues in one report are harder to sort and fix.
If you find more than one issue, make separate tickets for each one.
10. Griffon and Manticore Mount Policy
Griffon and Manticore mounts are awarded at the discretion of the development team for reports that meet specific criteria. These mounts are reserved for significant issues that are not obvious and pose a risk to the stability, security, or economy of the game.
Please do not request these mounts or attempt to present minor issues as major concerns. This only diverts attention from meaningful reports and slows down progress.
Players who consistently submit detailed, helpful reports that contribute to improving the game may also be considered for a mount. If you are eligible, the team will contact you directly. There is no need to ask about eligibility.
Thanks for helping improve Return of Reckoning.
We’re all here because we care about the game. Taking the time to report bugs the right way makes a big difference.
— RoR Team
