Bug reports, bounties and suggestions

Open Feedback › Known issues and press Report a bug. Opening the form from the page where the bug happened fills in the area for you.

Feedback is for bugs in Torning. A bug or glitch in Torn itself belongs with Torn's own bug bounty programme, so report it to Torn and don't use it in the game.

• Title: what broke, and where. As you type, known issues with similar titles appear under it with a Me too button. If yours is one of them, press Me too instead of sending a report.
• What happened and What you expected: copy any error message word for word.
• Steps: one per line, from where you started to where it broke.
• How often (Always, Sometimes or Once) and How bad (Blocks me, Annoying or Cosmetic).
• Screenshots: up to 3 images, 5 MB each.
• Keep this off Known issues: once a bug is confirmed, every player can read its title, what happened, what you expected and the steps on Known issues. Switch this on for anything that shows someone else's data or could be abused. The feedback team still sees the report, and the bounty is the same.

The form shows what is sent with your report so the feedback team can make the bug happen again: the page you came from, your browser, your theme, which clock you use (TCT or Local) and your screen size. Only the feedback team sees it.

Bug reports, replies, suggestions, comments and edits share one limit: 10 posts in 10 minutes.

A confirmed bug pays the first player who reported it 1 Xanax, sent to you in Torn by hand. Torning sees it arrive and marks your bounty sent, and you get an alert.

• Only the first report of a bug is paid. A report closed as a duplicate pays nothing; the original keeps the bounty, and you follow the original instead.
• A bounty is owed when the feedback team confirms the report. If the report is later closed as not a bug before the Xanax is sent, the bounty is cancelled. Xanax already sent is never taken back.
• Admins are not paid for their own reports. Feedback maintainers are paid like any player.
• Bounties are for bugs in Torning only. A bug in Torn is Torn's to reward.

Feedback › My reports shows each bounty as pending or sent, and how many Xanax you have earned.

A report is private: only you and the feedback team can open it. Feedback › My reports lists yours with a step bar: Sent, Confirmed, In progress and Fixed.

• New: waiting for the feedback team to look at it.
• Needs info: the feedback team asked you something. Open the report and reply below the question; your reply sends it back to the team.
• Confirmed, In progress and Fixed: it is a real bug, on its way to being fixed.
• Duplicate, Not a bug, Can't reproduce and Won't fix: closed without a fix, with the reason shown on the report.

Every step and every reply from the feedback team sends you an alert.

If a closed report is still wrong (the fix did not hold, or you think it was closed by mistake), open it and use Reopen report with a line on what is still wrong. It goes back to the feedback team as New. You can reopen a report up to 90 days after it closed, three times at most; a duplicate cannot be reopened, since you already follow the original. Reopening never changes your bounty: one owed stays owed, one sent stays yours, and a report confirmed again is not paid twice.

If you told an admin about a bug somewhere else, such as on Discord, they can file the report for you. It shows in your My reports like any other, and the bounty is yours. You get an alert naming the admin who filed it.

Bug reports and suggestions are looked after by the feedback team: Torning's admins and its feedback maintainers, players Torning trusts to read and sort reports and suggestions. The team confirms bugs, asks for more detail, replies and sets where each suggestion stands.

• Everyone on the team can read every report, including ones kept off Known issues, with their screenshots and what was sent with them.
• A maintainer never works their own report. Someone else on the team confirms or closes it, and the maintainer cannot read the team's notes on it.
• A maintainer's confirmed report earns the bounty like anyone's. Only admins send the Xanax, and only admins file a report or post a suggestion in another player's name.
• Maintainers hold Pro, and admins Ultra, for as long as they have the role.

Feedback › Known issues lists confirmed bugs, except any kept off the list, with how many players have each one. Bugs fixed in the last week stay listed so you can see they are done. Press Details on one to read what happened, what was expected and the steps to make it happen.

Press Me too on one you have run into. It tells the feedback team how many players it affects, and you get an alert when it is fixed. Press it again to take it back. Your own reports show Your report instead.

Feedback › Suggestions lists what players have asked Torning to build, the ones still taking votes first. Sort by Top or New, filter by status, or search.

• You have 10 votes to spend. Put up to 3 on one suggestion with its + and - buttons; the dots show how many of yours it holds. The bar under Your votes shows where they all sit.
• A suggestion moves through Open, Approved, Planning and Completed, or is Declined. When it is Completed or Declined, your votes on it come back to you.
• A duplicate may be merged into another suggestion. Your votes move with it, still at most 3 on one.
• Torning's answer is pinned on the suggestion as Response from Torning. Anyone can add a comment.

To post one, press Suggest something. Similar suggestions appear as you type the title, so you can vote on one instead.

If you gave an admin an idea somewhere else, such as on Discord, they can post it in your name. It shows under your name like any other, and you get an alert naming the admin who posted it.

The comments on a suggestion and the conversation on your bug report are threads.

• Reply under a message to answer it in its thread. Replying to a reply keeps you in the same thread and tags the player you are answering.
• Type @ and the start of a name to tag a player, then pick them from the list. They get an alert. Under a suggestion you can tag any Torning player. On a bug report you can tag only the people who can already read it: you and the feedback team. You can tag up to 10 players in one message.
• Edit your own message to change it. It then reads Edited, and anyone who can read it can open the earlier versions with when each was written. A player you newly tag hears about it; nobody else is told again.
• Delete your own message at any time. If others have replied under it, it reads Comment deleted and their replies stay; its text and its earlier versions are gone. The feedback team can delete any message, but only you can edit yours.
• A badge beside each name shows Torning's staff (Superadmin, Admin or Maintainer), or Ultra or Pro for a player who has it. Messages by whoever reported the bug or posted the suggestion also carry an OP badge.

A merged suggestion takes no new comments or edits. A closed bug report takes no new replies or edits unless you reopen it.

Staff can attach a document to a bug report, a suggestion, a site notice or an inbox message: a PDF, a spreadsheet or a picture that explains a fix or a change.

• On a bug report or a suggestion it shows in a Documents from Torning staff card. Only the people who can already see that item can open it: on a bug report, that is you as the reporter and the feedback team.
• On a site notice or an inbox message it shows as a link beside the message. A notice's document opens for anyone shown the notice, and a message's for the members who got it, while it is in their Alerts.
• Pictures open in a new tab. Every other file downloads.

Each link lasts 30 minutes. If one says it has expired, go back and reload the page for a fresh one. When staff take a document down, it leaves the item and any link to it stops working straight away.

The demo shows documents but does not open them.

The Feedback card on Account › Alerts lists the alerts this sends you, all switched on and landing in Alerts until you change them:

• Your report changed status, and a reply on your report.
• Bounty sent.
• A known issue you follow is fixed.
• A suggestion you posted or voted on changed status, and a comment on your suggestion.
• A reply under your comment or message, and being tagged with @.

The feedback team also gets the alerts marked Team on that card: a new bug report, a reporter replying, a report given to you and a new suggestion. A maintainer never gets them for their own reports.

Each can go to Alerts, to Discord or both once Discord is linked, or be switched off. Reset to default puts one back. The Guides card on the same page holds the alerts for replies to your guide questions and your writer application, and, for guide writers, questions on and reviews of their own guides.