Bugs

Reporting bugs is very important so that we can keep Stendhal running smoothly. So, if a bug is worth asking /support or a developer about, it is worth submitting a bug report on.

We have made this page to help you with the process of submitting a bug report, because we find them so helpful.

You can submit a new report in our Codeberg project: Open bug report

Or browse the issue tracker. Or the old trackers at GitHub or SourceForge.

We are more than happy to close reports that are not really bugs, and would prefer you to submit a bug report and us close it, than not submit it and we never find out about it. Having said that, before submitting a bug you should scan over the previously posted bugs summaries so that you don't report an already known bug.

If you need help submitting a bug report feel free to ask the developers and contributors in the development chat channels. These channels are logged, so someone will respond when they are available.

If there are multiple bugs to report, please open an individual report for each.

• Title - This is a short summary of the bug report. Choose a meaningful and brief sentence.
  • Bad title: "there is a bug", "bug found" "error occurred"
  • Good title: "Stendhal 0.67 map wrong at x y in -3_semos_cave" or "Test client: buddies panel does not show buddies online state"
• In the detailed description please include if possible:
• Where were you when the bug happened? (use '/where yourUserName' in game)
• What did you do when the bug happened?
• What did happen, what did you expect to happen
• Is it reproducable? If so: Which steps are needed to reproduce it?
• When talking about map-errors like 'you can walk under a chair' please provide the exact position and if possible a little screenshot.
• If things in client look weird a screenshot says more than 1000 words
• Your email address, if you are not a logged in member (SourceForge only unless you have a good reason to think it's irrelevant)
• Your Operating system
• Whether you are using the web client or downloaded the Java client
• What Java version you have if you are using the Java client (In Linux, type java --version in a command line. Windows users check here)
• Any error logs
• $HOME/.config/stendhal/log/stendhal.txt on Linux
• %USERPROFILE%\stendhal\log\stendhal.txt on Windows
• GitHub optional fields:
• Labels - predefined keywords used to describe what the report is about
• Example: "component: javaclient" means that the issue is directly related to the Java client
• Files can be attached by clicking the line below the description area or by dragging and dropping files directly into the description
• Everything Else - igore, the remaining fields will be filled out by an administrator
• SourceForge optional fields:
• Labels - keywords that can be used to identify this report in searches
• Mark as Private - tick the check box for sensitive or easily abused issues
• Attachments - here is where to attach screenshots or text output of error logs
• Everything Else - igore, the remaining fields will be filled out by an administrator

If you are connecting to the test server using the Java client, please be sure your client is up-to-date with the most recent build.

Please include in the bug report whether the issue occurred on the main or test server. Also include which client (e.g. web client, release Java client, or testing Java client) was being used if it is relevant.

Please confirm that the bug is still relevant by testing if it occurs in build from latest Git master branch.

Remember the importance of 'ant clean' or whatever the equivalent is in your IDE.