Back to articles

How to Format a Bug Report?

M
mschaudhary
Jun 24, 2026 · EN
20 2 2
Gold earned
0.0022 gold · 0.0001 from the game fund for every read and every like
A bug report is a simple explanation of something that did not work correctly in the game. It does not need to include code, programming terms, or technical details. A player only needs to explain what happened, where it happened, and how the team can check it. Clear bug reports are very important during development and first launch. At this stage, real players may find issues that internal testing did not catch. A useful report helps the developers repeat the same issue, understand the cause, and fix it faster. What Counts as a Bug? A bug is any game action, page, value, or result that does not work as expected. In an online game, this can affect the account, market, inventory, Gold balance, rewards, rankings, login, or page display. Common Issues During Early Deployment Players may face these issues when an online game is still being developed or newly deployed: • Login or registration problems, such as failed sign in, email verification, or password reset. • Pages that load slowly, freeze, refresh incorrectly, or show an error. • Buttons that do not work on desktop, mobile, or a specific browser. • Marketplace issues, such as buying an item for 0.000005 Gold but not receiving it. • Wrong Gold, item, reward, or resource balance after an action. • Inventory, reward, or progress not saving after refresh or logout. • Text, buttons, or menus appearing broken, hidden, or difficult to read. • Old and new versions appearing after a game update. • Security or account issues, such as seeing information that should stay private. What to Include in a Bug Report A good bug report should be short, clear, and complete. The player should try to include these details: 1. Title: One clear line that explains the issue. Example: Marketplace purchase took Gold but item did not appear. 2. Feature or page: Mention where it happened, such as Marketplace, Inventory, Login, Rewards, Profile, or Trade. 3. What you were doing: Explain the action you tried to complete. 4. Steps to repeat: List the actions in order so another person can try the same thing. 5. Expected result: Explain what should have happened. 6. Actual result: Explain what really happened. 7. Amount or item involved: Add the exact Gold amount, item name, reward, or resource. Example: 0.000005 Gold. 8. Device and browser: Mention mobile or desktop, plus browser if known, such as Chrome, Safari, or Firefox. 9. Time and frequency: Mention when it happened and whether it happened once, sometimes, or every time. 10. Proof: Add a screenshot or short video if possible. Do not share passwords or private account details. Simple Bug Report Template Title: Marketplace purchase took Gold but item did not appear Feature: Marketplace and Inventory What I did: I bought an item from the market Steps: Opened Marketplace, selected item, bought it for 0.000005 Gold, checked Inventory Expected result: Gold should be deducted and the item should appear Actual result: Gold was deducted but the item did not appear Device/browser: Desktop, Chrome, Windows How often: Happened 2 times Proof: Screenshot attached How to Decide the Severity of a Bug Severity means how serious the bug is. It helps the team decide how quickly the issue should be checked. A bug is more serious when it affects Gold, items, rewards, login, account safety, game fairness, or many players. Critical Severity Use Critical when the game cannot be used, many players cannot log in, account safety is at risk, Gold or resources can be copied, or many players are losing important progress. High Severity Use High when an important feature is broken. Example: a player buys an item for 0.000005 Gold, the Gold is deducted, but the item does not appear in Inventory. Medium Severity Use Medium when the feature partly works but causes confusion or repeated failed attempts. Example: a reward appears only after refreshing the page. Low Severity Use Low when the issue does not stop gameplay. Example: a spelling mistake, small layout issue, or missing icon where the main action still works. Simple Severity Questions If you are not sure about severity, ask: • Can I still play the game? • Did I lose Gold, items, rewards, resources, or progress? • Can someone get an unfair benefit from this issue? • Does the issue happen again when I repeat the steps? • Is one page affected, or is the whole game affected? • Can I solve it by refreshing, logging in again, or using another browser? Example of a Simple Bug Report Title: Marketplace purchase took Gold but item did not appear Feature: Marketplace and Inventory Description: I bought an item from the market. My Gold balance changed, but the item did not show in my Inventory. Steps: 1. Logged into my account. 2. Opened the Marketplace. 3. Selected an item listed for 0.000005 Gold. 4. Clicked Buy and confirmed the purchase. 5. Opened Inventory after the purchase. 6. Refreshed the Inventory page. Expected result: The item should appear in Inventory after the Gold is deducted. Actual result: The Gold was deducted, but the item did not appear in Inventory. How often it happened: 2 times. Device and browser: Chrome on Windows desktop. Suggested severity: High, because Gold was deducted and the item was not received. Benefits of a Clear Bug Report A clear bug report helps the player explain the issue properly. It also helps the support team and developers understand what happened without asking too many extra questions. When the report includes exact steps, expected result, actual result, Gold amount, device details, and screenshots, the developers can test the same action, check the records, and confirm the fix. This protects player progress, reduces confusion, and helps keep the game fair during launch and future updates. Final Checklist • Clear title • Page or feature name • Steps in order • Expected result and actual result • Exact Gold amount, item, reward, or resource involved • Device and browser • Screenshot or video if possible • Severity based on real impact Conclusion A bug report does not need to be technical. It only needs to be clear, honest, and complete. Players help improve the game when they explain what happened, where it happened, how often it happened, and what proof they can share. Simple and accurate bug reports help developers fix problems faster, protect Gold and item records, and keep the online game stable and fair for everyone.

Ready to Start Earning Real Gold?

Create Free Account
100% Free to Play

Comments (2)

M
Majid126
+7
Jul 1, 2026

این مقاله راهنمایی منظم و بسیار کاربردی برای گزارش خطا در بازی ارائه می‌دهد. به نظر من، نویسنده به‌خوبی توضیح داده که یک گزارش مؤثر نیازی به دانش فنی ندارد و تنها با ارائه اطلاعات دقیق و شفاف می‌تواند به رفع سریع مشکلات کمک کند. دسته‌بندی انواع خطاها، توضیح میزان اهمیت آن‌ها و ارائه نمونه عملی، مطالعه این مطلب را برای همه بازیکنان مفید کرده است. تنها پیشنهاد من افزودن چند تصویر از نمونه گزارش یا صفحه‌های مرتبط است تا درک مطالب آسان‌تر شود. در مجموع، مقاله‌ای آموزشی، روان و ارزشمند برای تمام کاربران محسوب می‌شود.

0
Y
yeethernal
+10
Jul 12, 2026

This is a great reminder that the quality of a bug report often matters more than its length. A concise report with clear reproduction steps, the expected and actual results, and the environment where the issue occurred can save developers a tremendous amount of investigation time. Good bug reports don't just fix individual issues—they help make the game more stable for the entire community.

0

Articles