> For the complete documentation index, see [llms.txt](https://siege-of-midgard-ro.gitbook.io/wiki-smro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://siege-of-midgard-ro.gitbook.io/wiki-smro/team-with-us-community/bug-reports.md). # Bug Reports The **Bug Reports** page is where players can learn how to report problems properly in Siege of Midgard RO. Reporting bugs clearly and responsibly helps the staff team fix issues faster, protect the server, and improve the experience for everyone. If you find something broken, unusual, or exploitable, report it through the proper channel instead of ignoring it or abusing it. ### What Counts as a Bug A bug is any unintended problem or incorrect behavior in the game or server. This may include issues such as: * broken NPCs * incorrect item behavior * skill problems * map glitches * quest issues * wrong monster behavior * missing sprites or effects * broken event mechanics * wrong reward behavior * custom system problems * crashes or unusual errors If something clearly does not work the way it should, it may be a bug. ### Why Bug Reporting Matters Bug reporting matters because it helps the server improve. A good bug report can help the staff team: * identify issues faster * reproduce the problem * prevent player frustration * protect server balance * stop exploits before they spread * improve future updates and fixes Even small reports can be valuable if they are clear and accurate. ### Report, Do Not Abuse If you discover a bug, the correct action is to **report it**, not to use it for personal gain. Abusing bugs or exploits may harm: * server balance * economy stability * player fairness * event integrity * trust within the community Using a bug repeatedly for advantage may be treated as **exploit abuse**, which can lead to penalties. If you find a problem, report it immediately. ### What Makes a Good Bug Report A good bug report is clear, specific, and easy to understand. The best reports usually include: * what the problem is * where it happened * when it happened * what you were doing before it happened * what should have happened instead * whether it can be repeated * screenshots or video if available The more useful details you give, the easier it is for staff to investigate. ### Important Details to Include When sending a bug report, try to include as many of these details as possible: #### Character Name Mention which character you were using. #### Location State the map, NPC, event, or system involved. #### Exact Problem Explain clearly what went wrong. #### Steps to Reproduce If possible, explain how the bug happened step by step. #### Screenshots or Video Visual proof is extremely helpful. #### Time or Approximate Time This can help staff check logs if needed. #### Frequency Mention whether it happened once or happens every time. ### Good Example of a Bug Report A simple good report might look like this: > Character Name: SampleName\ > Location: Prontera Tool Dealer / Custom Exchange NPC\ > Issue: When I trade the required materials, the NPC removes my items but does not give the reward.\ > Steps: I clicked the exchange option, confirmed the trade, and the materials disappeared.\ > Expected Result: I should receive the listed reward item.\ > Screenshot: attached This kind of report is much easier to investigate than “NPC broken pls fix.” ### Bad Bug Reports Reports become harder to use when they are too vague. Examples of weak reports include: * “this is broken” * “fix this” * “my game bugged” * “npc no work” * “something wrong in map” These reports do not give enough detail for fast investigation. ### Where to Report Bugs Bug reports should only be sent through the **official server support channels**. This may include: * official Discord support channel * dedicated bug-report channel * support ticket system * direct staff instruction if requested Always use the reporting process preferred by the server team. ### When to Report Immediately Some issues should be reported as soon as possible, especially if they involve: * item duplication * economy abuse * broken reward systems * exploitable map or PvP behavior * broken MVP or event rewards * custom system abuse * any bug that gives unfair progression or combat advantage These types of bugs can damage the server if left unreported. ### Bug vs. Personal Issue Not every problem is automatically a server bug. Sometimes issues come from: * outdated client files * incomplete patching * antivirus interference * mixed files from another server * user-side setup problems If you are unsure, check the **Troubleshooting Guide** first. If the problem still looks like a server issue, then report it properly. ### Why Proof Helps Screenshots and video clips are very useful because they help staff: * see the exact issue * confirm what happened * reduce guesswork * reproduce the bug faster * compare the report with server logs Even a simple screenshot can make a report much more useful. ### What Not to Do If you find a bug, avoid doing the following: * abusing it repeatedly * sharing exploit instructions publicly * using it for profit or advantage * spreading panic without proof * accusing players without evidence * demanding instant fixes aggressively Report the issue calmly and properly instead. ### Why Responsible Reporting Helps Everyone A healthy server depends on players and staff working together. Responsible bug reporting helps: * new players avoid broken systems * the economy stay fair * PvP and events stay balanced * custom systems improve over time * the server become more stable and trustworthy Good reports are part of building a better server. ### Final Advice If you find a bug, report it clearly, honestly, and through the correct channel. You do not need to write a perfect technical report. You just need to provide enough useful information for the staff team to understand the problem. The faster and clearer a report is, the easier it is to fix the issue and protect the server. ### Summary The Bug Reports page helps players understand: * what counts as a bug * why bug reporting matters * why exploit abuse is not allowed * what details to include in a good report * how to report issues properly through official channels Report responsibly, include useful details, and help make Siege of Midgard RO better for everyone. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://siege-of-midgard-ro.gitbook.io/wiki-smro/team-with-us-community/bug-reports.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.