Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A strange mechanic is not automatically a bug. Classify it by checking the game’s current patch notes and known-issue tracker, reproducing the behavior under recorded conditions, and comparing the result with a documented rule or clearly defensible expectation. If the evidence remains inconclusive, send a focused report through the game’s official support channel; if the mechanic works consistently but feels unfair or unfun, use the game’s design-feedback route instead.
What separates a bug from an intended mechanic?
A bug is a defect: the game fails to implement a rule, behaves inconsistently, or produces an outcome that contradicts its own documentation or a developer-confirmed promise. An intended feature can be surprising, difficult, unpopular, or poorly balanced while still working exactly as designed.
The key question is not “Do I dislike this result?” It is “What should have happened, and what evidence establishes that expectation?” A tutorial, item description, ability tooltip, official manual, patch note, or developer statement can establish an expected result. A community assumption or a mechanic that feels unfair cannot, by itself, prove a defect.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →You also need the exact game, build, platform, mode, settings, and circumstances. Without those details, nobody can reliably classify a particular case because the same symptom may be a cross-platform bug, a server-side issue, a version difference, a compatibility problem, or a deliberate rule.
#1 Best Overall
A practical decision process
1. Describe the behavior precisely
Write down what you did and what the game did in response. Include:
- The character, item, ability, quest, weapon, or system involved.
- Your starting state, location, mission, map, or game mode.
- Every relevant input, timing detail, and sequence of actions.
- The result you observed, including missing effects, unexpected damage, duplicated rewards, freezes, or other symptoms.
- Conditions that may matter, such as low health, a specific difficulty, a party size, a particular server, or an active status effect.
Use neutral language. “The shield did not block the attack while its tooltip says it blocks frontal damage” is more useful than “The shield is broken.” A neutral description keeps a preference, balance complaint, and technical failure from being conflated.
2. Record the build and environment
Capture the game’s version or build number before testing. Also record the platform, operating-system version when relevant, graphics or accessibility settings that affect the mechanic, add-ons or mods, input device, network type, and whether the session is solo, peer-hosted, or on a dedicated server.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsEnvironment information is part of the diagnosis, not administrative detail. Bungie Help and Minecraft’s reporting guidance both ask for platform or system details because a behavior limited to one platform, client version, or configuration can be a technical compatibility issue rather than a design decision. Note whether the behavior occurs in single-player, multiplayer, a specific region, or only on one server.
3. Check official explanations before testing theories
Search the developer’s current patch notes, known-issues page, issue tracker, and support articles. Use the mechanic’s name plus a short symptom, such as “charged attack does no damage after patch” or “quest reward missing in co-op.” Check the version date and platform scope of every result.
Arrowhead Game Studios advises players to check known issues before filing a report, and its guidance was updated on October 6, 2026. Minecraft similarly asks players to search its tracker and avoid creating duplicate reports. Guild Wars 2 Support directs players to known issues and release notes. A listing means the developer recognizes a problem; it does not promise a fix date, a workaround, or that every similar symptom has the same cause.
A patch note can also establish intent. If a note says an ability now consumes stamina before applying its effect, the change is probably deliberate even if it feels worse. If the live behavior differs from the note, document that mismatch as a possible defect.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Reproduce the behavior
Repeat the same sequence from the same starting state. Record whether it happens every time, most times, occasionally, or only once. Then change one condition at a time: switch platforms, disable an add-on, enter a different mode, use another character, change the network, or repeat after restarting the client.
A repeatable result gives quality-assurance staff a direct path to the failure. An intermittent result is still worth reporting; record the number of attempts, approximate frequency, and the conditions present when it occurred. Do not change five variables at once, because you will not know which change affected the outcome.
5. Define the expected result
Write an explicit expected result and identify its basis. Strong bases include:
- An in-game description, tutorial, rule, or objective.
- Official documentation or a developer statement.
- A release note that says existing behavior should continue.
- A clearly reproducible inconsistency, such as an effect working on one identical target but not another when no rule distinguishes them.
Bungie Help’s reporting template uses the labels “ACTUAL RESULT” and “EXPECTED RESULT.” Follow that separation even for a small report: describe what occurred after the steps, then state what should have occurred and why.
6. Decide whether this is a defect or feedback
Use the bug-report route when the implementation appears broken, contradicts documented behavior, fails intermittently, or produces an impossible state. Use design or balance feedback when the mechanic behaves consistently but you want a different rule, lower difficulty, better rewards, or a different feel.
Rank #3
- Brand New in box. The product ships with all relevant accessories
Roberts Space Industries distinguishes suspected defects from intended design feedback through its Issue Council. EVE Frontier’s support guidance likewise separates bug reports from design, balance, and general opinions. Electronic Arts distinguishes bug reports, technical troubleshooting, and feedback. A mechanic can be both unpopular and technically correct; report the defect only when you can identify a behavior that fails a rule or expected result.
7. Search for duplicates and submit one focused report
Search the official tracker using the mechanic, symptom, and version. If an existing report matches, add your platform, reproduction rate, and evidence instead of opening a duplicate. If no matching report exists, file one issue for one underlying problem. Minecraft specifically recommends one issue per report, with a clear title, reproduction steps, environment details, and evidence.
Clues that indicate intent or a defect
| Clue | What it suggests | What to do next |
|---|---|---|
| The behavior is listed in an official known-issue tracker | The developer recognizes it as an issue, although a fix date is not guaranteed. | Read the status, affected versions, and any workaround. Add new evidence only if the report requests it. |
| The behavior is consistent and documented | Consistency plus an official explanation supports intended behavior. | Use design feedback if you want the rule changed. Report a defect if the implementation differs from the documentation. |
| The behavior began after an update | A version-specific regression is possible, but timing alone does not prove the update caused it. | Record the old and new builds, check release notes, and test on the current supported version. |
| Only one platform, mode, setting, add-on, or network condition is affected | A compatibility or technical issue may be involved rather than a universal design rule. | Preserve the condition in the report and compare with a controlled test that changes one variable. |
| The mechanic is merely surprising, hard, or unpopular | That is not evidence of a bug. | Look for a rule or explanation. If the rule is working but undesirable, send design feedback. |
| Identical inputs produce different results without a stated rule | An inconsistency is a stronger defect signal. | Capture both successful and failed attempts, including target state and timing. |
How to test without losing useful evidence
Start with a controlled baseline
Before changing settings, perform the shortest sequence that demonstrates the symptom. Save a clip or screenshot showing the starting state, the input, and the outcome. Note the local time, mission or match identifier if available, and the build shown on the title screen or settings page.
Change one variable per test
- Repeat the sequence on the same account, character, map, and difficulty.
- Repeat after restarting the game client, without changing other settings.
- Test a second target or equivalent item to determine whether the rule is conditional.
- Disable one add-on or change one setting, then repeat.
- Test another mode, platform, or network only when practical and safe.
Stop if the test could consume paid items, delete progress, expose private information, or disrupt other players. A report does not need an elaborate experiment; it needs a safe, repeatable description.
Distinguish client, server, and account effects
If another player sees a different result at the same moment, capture both perspectives. A visual-only error on your client may differ from a server-authoritative rule that affects everyone. Likewise, a problem tied to one account, save, character, or entitlement should be identified as such instead of being described as a universal mechanic.
What to include in a high-quality bug report
Official reporting forms vary, but the following information covers the common requirements from Bungie Help, Arrowhead, Minecraft, and Innersloth:
Rank #4
- Game and exact build: include the full version number, not only “the latest patch.”
- Platform and environment: console or PC model, operating system when requested, relevant settings, add-ons, and input method.
- Short summary: state the mechanic and symptom in one sentence.
- Starting state: identify the mode, location, character, equipment, quest stage, and other conditions needed to begin.
- Numbered reproduction steps: list the inputs in order so another person can follow them.
- Actual result: describe exactly what the game did.
- Expected result: state what should happen and cite the tooltip, rule, documentation, or comparison that supports it.
- Frequency: say whether it happens every attempt, intermittently, or only once, and give an approximate rate when possible.
- Evidence: attach a short video or screenshots that show the relevant state and outcome. Arrowhead says video is especially useful; Bungie and Minecraft also request visual evidence where it clarifies the report.
- Logs or system details: provide them when the form requests them, while removing account identifiers, chat messages, IP addresses, or other private data.
- Related report: include the identifier of a similar issue instead of duplicating it.
A concise report structure
Title: [Mechanic] fails to [expected effect] in [mode/platform] on build [version]
Environment:
- Platform and system:
- Game build:
- Mode, map, or server:
- Settings, add-ons, or network conditions:
Steps to reproduce:
1. Start with ...
2. Equip or activate ...
3. Perform ...
4. Observe ...
ACTUAL RESULT:
The game ...
EXPECTED RESULT:
The game should ... because [documented rule, tooltip, or comparison].
Frequency:
[Every attempt / intermittent / one-time; include approximate rate]
Evidence:
[Video or screenshots, with private information removed]Keep one report focused. If two symptoms might share a cause, file the clearest reproducible failure first and mention the second symptom as related context only when the tracker permits it.
When a mechanic is intended but still deserves feedback
A mechanic can be deliberately harsh, counterintuitive, or unpopular. Examples include a stamina cost that is explained in the ability text, enemies that ignore a familiar tactic by design, or a reward structure that consistently grants fewer items than players want. Those cases belong in a design-feedback channel unless the game contradicts its own description.
Feedback is more actionable when it explains the effect on play rather than simply demanding a change. Describe the rule, the situations in which it creates a problem, the alternatives you tried, and the change you would prefer. Separate “this makes the encounter frustrating” from “the stated resistance is not applied.” The first is a design opinion; the second is a testable defect claim.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common ambiguous cases
It changed after a patch
Check the patch notes for an intentional adjustment, then compare the current behavior with the wording. If the notes announce a change, treat the new rule as intentional unless the live implementation does something different from the announced change. If no note mentions it, report the version transition and avoid claiming that the patch definitely caused the problem.
It happens only in multiplayer
Record host, client, region, latency symptoms, party size, and whether all players see the same result. A desynchronization or server condition can mimic a mechanic change. Do not label it a balance decision until you have ruled out session-specific behavior.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIt works sometimes
Intermittence is a reason to document more conditions, not a reason to dismiss the issue. Record frequency, elapsed play time, target type, animation state, frame or tick timing when visible, and whether restarting clears it. A reliable “one out of ten attempts” report is more useful than “it randomly breaks.”
The game gives an unexpected reward or duplicate item
Check whether the reward is intentionally repeatable, mode-specific, or affected by a stated multiplier. Capture the inventory before and after, the completion screen, and the account or character context without exposing personal identifiers. If the result conflicts with the reward description or creates an impossible inventory state, report it as a defect.
A mod or add-on changes the result
Reproduce once with the add-on enabled and once in the supported unmodified configuration. Include the add-on name and version if the developer’s form requests it. A game may not support third-party modifications, so the correct destination can be the add-on maintainer rather than the game developer.
Where to send the report
Use the channel designated by the developer: an official issue tracker, support form, in-game reporting tool, or a moderated bug forum. Search that channel first and follow its required format. Arrowhead, Minecraft, Bungie, and Guild Wars 2 all direct players toward their own known-issue or reporting systems rather than relying on general discussion posts.
Use a design-feedback forum when the behavior is documented and consistent but you want a balance or usability change. Use technical support when the game will not launch, crashes, loses connection, or shows a device-specific failure without a clear mechanic rule. Some publishers separate these routes; selecting the closest category helps the report reach the team that can act on it.
What not to do
- Do not call every frustrating mechanic a glitch.
- Do not report a whole game as one issue; isolate the smallest reproducible failure.
- Do not omit the build, platform, or mode because the behavior “should be universal.”
- Do not attach unedited footage that exposes account details, private chat, or unrelated players’ information.
- Do not create duplicate tickets across multiple categories with contradictory descriptions.
- Do not promise that a known issue will be fixed on a particular date; an acknowledgment is not a schedule.
A quick classification checklist
- Have you written the exact action, conditions, and outcome?
- Do you know the game build, platform, mode, settings, and network context?
- Did you check current patch notes, known issues, and the official tracker?
- Can another player reproduce the result from your numbered steps?
- Can you state an expected result based on a rule or official explanation?
- Is the complaint about broken behavior, or about balance and enjoyment?
- Did you search for a matching report before filing a new one?
- Does the report include frequency and clear evidence?
Bottom line
Classify the behavior with evidence, not surprise. A documented, consistent rule that you dislike is usually a feedback issue; a repeatable contradiction, failure, or version-specific inconsistency is a stronger bug candidate. When intent remains uncertain, submit the exact build, environment, reproduction steps, actual result, expected result, frequency, and evidence through the game’s official channel so the developer can make the final determination.
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.
