Bug Bounty Program
The Bug Bounty Program rewards players who help identify bugs or exploits in Soulbound. Submitting a valid, first-reported bug earns Bug Bounty Credits, redeemable at the Bug Bounty Vendor for unique cosmetics, mounts, pets, and other special in-game items. The program was added in update 5.9.[1]
This program is a gesture of goodwill, not a guaranteed process — not every report earns credits, and the developers are under no obligation to respond to or act on any individual submission.
How to submit a bug report
Bugs are reported in the official Discord server, in the bug-report channel. Reports must describe a bug that is consistently reproducible — account-specific issues should instead go through in game support (the headset icon).
To gain posting access, players must first read the channel rules in the linked agreement channel.
Required information
A report missing any of the following fields may not be investigated, and may be closed as "Could Not Reproduce" or "Not A Bug":
| Field | Description |
|---|---|
| Summary | A short summary of the issue, used as the post title |
| Description | A detailed description of the issue |
| Timestamp | The date and time the issue occurred. A Discord timestamp generator can be used to create a universal timestamp |
| Region | The server region you're on (e.g. euro-west9)
|
| User ID | Your in-game User ID |
| DGS | A three-word, hyphen-separated identifier shown in the System tab of chat. It changes whenever you enter a dungeon or new area — record the DGS that was active when the issue occurred |
| Reproduction Steps | A numbered list of steps that reproduce the issue |
| Actual Result | What actually happens after following the reproduction steps (the bug) |
| Expected Result | What should happen instead, if the feature weren't bugged |
| Frequency | How often the bug occurs vs. doesn't, out of your attempts (e.g. "4/5 times" means the bug happened on 4 out of 5 tries) |
| Evidence | Screenshots or video showing the issue, ideally following the same reproduction steps listed above |
| Version Number | The current game version, shown in the bottom-left of the settings menu |
How rewards work
| Step | What happens |
|---|---|
| 1. Submission | Report is posted with all required fields (see above) and logged as a ticket by a support team member |
| 2. QA Verification | QA attempts to reproduce the issue. Reports that can't be reproduced are not eligible |
| 3. Reward Criteria | Only the first valid report of a given bug is rewarded. Credits are assigned based on the bug's assigned priority level, after it's resolved |
| 4. Redemption | Bug Bounty Credits are sent to the reporter's in-game mail, then spent at the Bug Bounty Vendor |
Priority levels
QA assigns one of the following labels once a bug is confirmed; the specific credit reward per level isn't published and is determined at the developers' discretion.
| Priority | Label | Description |
|---|---|---|
| Prio 1 | S1-P0 | Urgent — must be fixed immediately |
| Prio 2 | S1-P1 (Major1) | Severe and easy to reproduce, with a major impact on gameplay or user experience. Fixed as soon as possible |
| Prio 3 | S1-P2 (Major2) | Severe but not easy to reproduce. Fixed quickly |
| Prio 4 | S2-P1 (Major3) | Severe, easy to reproduce, and impacts user experience significantly. Fixed quickly |
| Prio 5 | S2-P2 (Medium1) | Severe but not easy to reproduce; not fixed as urgently due to reproduction difficulty |
| Prio 6 | S1-P3 (Medium2) | Typically a crash or severe graphical issue that's very hard to reproduce. May be fixed later or closed as Will Not Fix |
| Prio 7 | S3-P1 (Medium3) | Minor but very visible and easy to reproduce, usually a widespread graphical issue. May be fixed later or closed as Will Not Fix |
| Prio 8 | S2-P3 (Low1) | Severe but hard to reproduce due to complex reproduction steps. May be fixed later or closed as Will Not Fix |
Terms
- First Reporter Policy — only the first person to report a specific bug or exploit is rewarded; duplicates are not
- Validity — reports must be reproducible and verifiable by QA; user-specific issues may not qualify
- Discretionary rewards — the developers may adjust credit amounts, the redeemable item list, or close an issue as Will Not Fix at any time
- No retroactive rewards — bugs reported before the program existed are not eligible
- Responsible disclosure — do not share exploit details publicly before the issue is resolved; doing so, or exploiting a bug for personal gain, can result in a ban from the program or the game