Reporting Bugs

Revision as of 01:36, 20 December 2014 by Madcamel (talk | contribs) (Reverted edits by Arian (talk) to last revision by Wushin)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Check that your problem hasn't been reported already

The only supported client is Manaplus the official client. If you have an issue which involve your client switch first to the official client and check if the problem persists before reporting.

First use the Search feature on the forum to check if the issue you are experiencing was not posted before.:

For server and content bugs, check the Bug Tracking, maybe someone already posted same issue and it is being worked on.

Where to report?

Bug Tracking

Bug tracking is a powerful tool, users need to be a bit aware of the way game works. Anonymous log-in is possible.


If you are not sure that your problem is a bug or you are not sure that you can report it correctly, forum moderators, developers and players will help you or do it for you; report in:

You have strong reasons to suspect the content, the server or the client; report in the appropriate forum:

If you are requesting a feature or improvement or additional content us:


You are not sure that your problem is a bug: IRC #support channel  :

You are almost sure that your problem is a bug: IRC #development channel :

Your problem concerns the Manaplus Client: IRC #ManaPlus channel:


In-game bug reports often if not always get lost due to a developers shear number of highlights and whispers. Please realize this is the more error prone method. Although if a developer PMs you it is however a great way to display the bug.

How to report?

Here again the information that the developers need to solve the problem must be as complete and precise as possible.

In Client issues, specify your system name, version and architecture, and client version. It is very good idea to include the name of your OS in the topic title, for example: Windows XP: Game is crashing when... Be verbose, post backtrace, strace, content of tmw.log, versions of dependent software etc. Make sure that all Dependencies are installed and have correct versions.

Respect the time of developers and helpers - use descriptive topic titles, subjects like "OMFG game isn't working", "WTF HELP!", "GOT PROBLEM!" are not acceptable, and usually indicates that the author is a person not to be treated seriously. Good topic title is eg.: Linux: Can't load map file - unknown error. Posts which contains rude remarks, foul language or are duplicated will be closed without any notice.

Note that in order to fix a bug, a programmer needs an exact way to reproduce the circumstances which lead to it: "I had Item X and later I hadn't had it anymore" isn't enough information to pinpoint an issue. On the other hand "when you do X and Y while W and Z, and then you take a towel our of storage, you always get an orange instead" would be a bug description a programmer can actually use.

If you have a patch, post in Support / Bug Reports

When you use a pastebin, make sure to check the longest possible expiration setting.

Bug Report Templete/Guidelines

Please include as much of the following information when reporting a bug. F10 in Manaplus pulls up a debug window where you can read the map number & game coordinates.

  • Versions
    • Operating System and version
    • Manaplus and version
    • hardware information, if applicable (graphics/sound cards or mobile device)
  • Bug Description
    • A concise description of what the problem is.
    • Pure description, no narrative or conversational language.
    • Please include NPC names, Map Numbers and any related quest info.
    • F10 in Manaplus pulls up a debug window where you can read the map number.
  • Steps to Reproduce
    • Step by step instructions on how to reproduce this bug.
    • Do not assume anything, the more detailed your list of instructions, the easier it is for the developer to track down the problem!
    • Please include NPC names, Map Numbers and any related quest info.
  • Actual Behavior
    • Type what happens when you follow the instructions.
    • This is the manifestation of the bug.
  • Expected Behavior
    • Type what you expected to happen when you followed the instructions.
    • This is important, because you may have misunderstood something or missed a step, and knowing what you expected to see will help the developer recognize that.
  • Troubleshooting/Testing Steps Attempted
    • Describe anything you did to try to fix it on your own.
  • Workaround
    • If you found a way to make the program work in spite of the bug, describe how you did it here.

WIKI errors

Errors on the wiki should be fixed by the one who notices them - that's the point of a wiki. When the documentation is wrong, you should make it correct.


Before developers release game content onto the official server, they'd like feedback from other developers and playtesters. If you are interested in content testing watch the Testing Server page in this wiki.