A strange mechanic is not automatically a bug. To classify it, document exactly what happened, check the current build’s official patch notes and known-issue tracker, reproduce the behavior, and compare the actual result with an expectation supported by the game’s rules or documentation. A mechanic that works consistently but feels unfair is usually design feedback; a repeatable contradiction, failure, or inconsistency is a stronger bug-report candidate.
Without the game, version, platform, mechanic and circumstances, nobody can reliably determine the developer’s intent. When the evidence remains ambiguous, send a focused report through the game’s official support channel and let the developer resolve the classification.
As an Amazon Associate I earn from qualifying purchases.
Bug, intended feature, or design problem?
Players commonly use “bug,” “glitch,” and “feature” interchangeably, but the distinction matters because developers route each kind of report differently.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsA bug is a failure against an established expectation
A bug is behavior that fails to implement a documented rule, breaks a previously reliable function, produces an inconsistent result under the same conditions, or prevents the game from operating as described. The expectation should have a defensible basis: an in-game tutorial, item description, official documentation, a patch-note promise, or a developer statement. “This feels wrong” is not enough on its own.
#1 Best Overall
An intended feature can still be surprising
A mechanic may be deliberately difficult, counterintuitive, hidden behind a condition, or unpopular. If it behaves consistently and matches an official explanation or established rule, it is evidence of intended design even when players dislike the outcome. A balance complaint belongs in a feedback channel rather than a defect tracker.
A technical issue may sit between design and gameplay
When a mechanic changes with a platform, graphics setting, add-on, network state, server, or game mode, the cause may be compatibility or a technical fault rather than a design decision. Preserve those conditions in your notes instead of assuming that an update or a particular device is responsible.
The seven-step decision process
1. Describe the exact event
Record the action that triggered the behavior, the location or mode, your inputs, the result, and every condition that might matter. Include the starting state: character status, inventory, quest progress, world seed, match state, or other relevant variables.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Use observable language. “The door opened after pressing the interact button while the alarm was active” is useful. “The stealth system is broken” is a conclusion that still needs evidence. Also separate dissatisfaction from contradiction: an enemy that defeats you quickly may be working as designed, while an attack that ignores an explicitly stated immunity is a potential defect.
2. Capture the build and environment
Write down the exact game version or build, platform, operating-system version when relevant, graphics and accessibility settings that affect the mechanic, installed add-ons, and whether the session was solo, peer-to-peer, dedicated-server, or otherwise multiplayer. Note the server or region if the game exposes it.
Bungie’s bug-report template and Minecraft’s reporting guidance both request environment details because the same action can produce different results across builds or systems. A report that says only “this happened yesterday” cannot tell a support team which implementation to investigate.
3. Search official explanations before drawing a conclusion
Check the current patch notes, known-issue list, issue tracker, support articles, and developer forum posts. Search with the mechanic name plus a short symptom, such as “shield blocks damage while sprinting” or “quest marker disappears after reload.” Arrowhead Game Studios and Minecraft explicitly advise searching existing reports before filing a new one. Guild Wars 2 support directs players to its known-issue tracker and release notes as well.
Read the entry for the same version you are playing. A known issue may have been fixed, may affect only one platform, or may be acknowledged without a promised fix date. An absence from the list does not prove that your observation is intended; public trackers are not always exhaustive.
4. Reproduce the behavior
Repeat the same sequence several times. Record whether it happens every time, only occasionally, or only once. If practical, change one condition at a time: keep the character, location, and inputs constant while changing only the platform, setting, add-on, network state, or game mode.
A repeatable result gives quality-assurance staff a route to the failure. An intermittent problem is still worth reporting, but include its frequency and the conditions in which it appeared. A short video that shows the setup and the result can be more useful than a long explanation without context.
Rank #3
- Brand New in box. The product ships with all relevant accessories
5. State the actual and expected results
Write two separate statements. Bungie Help’s official template labels these fields “ACTUAL RESULT” and “EXPECTED RESULT.” The actual result says what the game did after the listed steps. The expected result says what should have happened and why you believe that: a tutorial instruction, rule description, official documentation, or a developer statement.
Free tools Windows power users keep installed
One-click scans. No signup required.
For example, “After activating the documented fire-resistance perk, the character takes full fire damage” is an actual result. “The character should receive the reduced damage described in the perk text” is an expected result. “The perk is bad” is feedback, not a testable expectation.
6. Choose bug reporting or design feedback
Use the bug-report route when the implementation appears broken, contradicts documented behavior, or produces an unintended-looking failure. Use design feedback when the mechanic works consistently but you object to its difficulty, balance, pacing, reward structure, or general feel.
Roberts Space Industries’ Issue Council guidance separates suspected defects from intended-design feedback. EVE Frontier likewise distinguishes defect reports from design, balance, and general opinions. Electronic Arts separates bug reports, technical troubleshooting, and feedback. If a game provides separate forms, choosing the right one helps your report reach the team that can act on it.
7. Search for duplicates, then submit one focused report
Search the tracker again using the mechanic, symptom, platform, and version. If an existing report matches, add your evidence where the tracker permits rather than creating a near-duplicate. If no match exists, submit one issue per report. Minecraft specifically asks for one issue per report, and Bungie, Arrowhead, and Innersloth all emphasize clear reproduction information and visual evidence.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #4
How to read the strongest clues
| Observed clue | What it suggests | What it does not prove |
|---|---|---|
| The behavior appears in an official known-issue list | The developer recognizes it as an issue in at least the listed context. | It does not promise a fix date or establish that every similar symptom has the same cause. |
| The behavior is consistent and documented | It supports intended behavior, especially when an official explanation describes the mechanic. | A documentation error or an implementation mismatch is still possible. |
| The behavior began after an update or differs by version | Version-specific release notes and regression checks are warranted. | The timing alone does not prove that the update caused the problem. |
| The behavior depends on settings, add-ons, network conditions, or mode | A compatibility or technical issue may be involved; those conditions belong in the report. | It does not establish whether the underlying mechanic was designed that way. |
| The mechanic is merely surprising, difficult, or unpopular | Design feedback may be appropriate. | Unfairness or surprise alone is not evidence of a defect. |
What a high-quality report contains
Prepare the report so another person can attempt the same test without asking you to reconstruct the session. Include:
- Game title and exact version or build.
- Platform and relevant system, graphics, accessibility, add-on, or network settings.
- A short symptom summary that describes one issue.
- Numbered reproduction steps, including the starting state and each input.
- The actual result.
- The expected result and the rule or documentation supporting it.
- Frequency: every attempt, intermittent with an observed rate, or one-time.
- The date and circumstances in which it occurred, including mode, server, and region when relevant.
- A short video or screenshots that show the setup and outcome.
- Logs or system details if the developer’s form requests them.
- The identifier or link of a similar report if you found one.
Bungie’s template also asks for notes, related links, and PC system information when applicable. Arrowhead says video is especially useful, while Minecraft requests a clear title, environment details, reproduction steps, and evidence.
A reusable report structure
Title: [short symptom, platform, and version]
Game/build: [exact version or build]
Platform: [platform and relevant system details]
Mode/server: [solo, multiplayer, server or region]
Settings/add-ons: [only those relevant to the behavior]
Frequency: [every attempt, intermittent, or one-time]
Steps to reproduce:
1. [Starting state]
2. [Action and input]
3. [Next action and input]
ACTUAL RESULT:
[What the game did]
EXPECTED RESULT:
[What should happen and the rule or documentation supporting it]
Evidence:
[Video, screenshots, logs, or related report identifier]Replace the bracketed fields with your observed information before submitting. Do not combine several unrelated symptoms in one ticket; separate reports make it easier to verify, triage, and close each issue.
Examples of ambiguous cases
A consistent but undocumented interaction
Suppose a status effect always disappears when you enter a particular zone, but the game never explains the interaction. Consistency points toward deliberate design, yet the lack of documentation leaves intent unconfirmed. Search patch notes and support posts, test the effect in comparable zones, and report it if the behavior conflicts with a stated duration or rule. If no contradiction exists, ask for clarification or submit design feedback rather than declaring it a bug.
A mechanic that changed after a patch
If an ability worked one way before an update and another way afterward, record both builds if you can. Read the update’s notes for an intentional change, then test on the current version. If the notes promise one result but the current build produces another, the mismatch is a strong bug-report candidate. If the notes intentionally changed the rule and the implementation matches, the remaining complaint is balance or design feedback.
A problem that occurs only on one platform
Keep the platform, operating-system version, graphics settings, controller or input method, and network conditions in the report. Ask another player to test the same build only if doing so does not change the relevant conditions. A platform-specific failure may be a technical compatibility issue even when the underlying mechanic is intentional.
An intermittent multiplayer result
Record the server or session type, participants, latency or connection symptoms visible in the game, and how often the result occurs. Do not label it a design feature merely because it cannot be reproduced on demand. Intermittent evidence is valuable when the report explains the conditions and includes a recording of at least one occurrence.
A mechanic that feels unfair
If repeated tests show the same result and the rules describe it accurately, classify the complaint as design feedback. Explain the player impact and suggest the change you want, such as a clearer warning, different timing, or revised balance. A feedback post should not claim a defect unless you can identify a broken or contradictory behavior.
Where to look for official guidance
Use the game’s own support and community channels first. The following official resources illustrate the kinds of instructions to expect:
- Bungie Help, “Reporting Bugs to Bungie”: provides a structured template with platform, summary, reproduction steps, actual result, expected result, links, notes, and PC information.
- Arrowhead Game Studios, “I’ve found a bug! How do I report it?” (updated October 6, 2026): advises checking known issues, supplying reproducible steps, and attaching screenshots or video.
- Minecraft, “Bug Us About Bugs”: asks players to search the tracker, use a clear title, report one issue at a time, include environment details, and provide evidence.
- Roberts Space Industries, “Bug Reports: Using the Issue Council”: explains the distinction between suspected bugs and intended-design feedback.
- EVE Frontier Support, “Bug Reporting”: separates defect reports from design, balance, and general opinions.
- Electronic Arts, “How to Bug Report”: distinguishes bugs, technical issues, and feedback so each can be routed appropriately.
- Innersloth Help Center, “How do I report a game bug/error!”: emphasizes specific descriptions and video or screenshot evidence because investigation can be complex.
- Guild Wars 2 Support, “Reporting Bugs & Exploits”: points players to known-issue tracking and release notes before filing reports.
These channels differ in their forms and moderation rules. Follow the selected game’s current instructions rather than copying a field that the form does not request.
Common mistakes that make classification harder
- Reporting a conclusion instead of an observation: “The physics are broken” gives investigators no test sequence.
- Omitting the build: A fix, regression, or platform difference cannot be checked without version information.
- Changing several variables at once: Reinstalling, changing settings, switching modes, and using a different character simultaneously hides the cause.
- Using community expectation as proof: A popular interpretation is not an official rule.
- Filing duplicates: Search the tracker and add evidence to an existing report when appropriate.
- Combining unrelated symptoms: One issue per report produces clearer reproduction and triage.
- Submitting only a long video: Give timestamps or numbered steps so reviewers can find the relevant moment.
- Arguing about intent publicly instead of reporting evidence: Developers can decide classification from reproducible details; speculation cannot replace them.
When public evidence cannot settle intent
Players can establish what happened, when it happened, and under which conditions. They usually cannot establish why the developer implemented it without an official explanation. A mechanic can be undocumented but intentional, documented but implemented incorrectly, or correct in one build and defective in another.
That is why the most useful conclusion is often conditional: “This is repeatable on version X, contradicts the stated rule Y, and is not listed among known issues.” Submit those facts through the official channel. If the developer confirms that the behavior is intended, the appropriate next step is feedback about clarity, balance, or player experience. If the developer confirms a defect, follow any workaround or status information they provide.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
