From The Battle for Wesnoth Wiki
Revision as of 19:22, 22 June 2007 by Alink (talk | contribs) (Who To Bug: add myself as mouse maintainer)

Where to report bugs

The prefered way to report bugs is through our bug tracking system on Gna, but you can also post your problem to the forums.

Needed information

  • What version of the game are you running?
  • Have you built (from sources) the game by yourself? gcc/g++ version? SDL library versions?
  • What operating system are you using? What version/release of that operating system?
  • Can you reproduce the problem? If you can please provide steps to do it.

On special request another note: Use common sense! If you know the information can't be relevant to your report simply omit it. Nevertheless too much information usually doesn't hurt.

Guidelines for reporting bugs

  1. First, please make sure the bug you are reporting has not already been fixed (consult to see the history of changes to the game).
  2. If it hasn't been fixed yet, please check that the bug hasn't already been reported, by [].
  3. If your bug or feature request hasn't been fixed and has not yet been submitted, please go ahead and report it.
  4. Please post only one bug per bug report. If you have multiple bugs that are related, you can cross reference them.

Note that feature requests should usually be discussed on the forums first, or they will generally be ignored until there is evidence that such a feature would be generally liked.

Keep bug reports to the point, and make sure your bug is easily reproducible given the information you provide. Clearly written, reproducible single bug reports will get attention before those reports that mix several different bugs into one report, or that are incomprehensible.

If there is already an existing bug report, do not hesitate to add a comment with your details - this way we know when some bug is getting "popular".

Please login to Gna! before reporting bugs

An account at Gna! is free and takes very little time to set up. You can submit anonymous bug reports, but then you will have to keep an eye on the bug report in case developers ask for clarification, which will delay your bug being fixed. If you login, you will receive notifications of any changes to your bug reports, which speeds things up considerably.

In-play problems

If it is in-play problem that you can reproduce, save the game and send the savegame to us with details how to reproduce the problem from the savegame.

Problems with scenarios

If it is a problem with a contributed scenario (like the ones on the Campaign Server), please report the problem to the maintainer of the scenario, not as a bug in Wesnoth itself. Bugs in the MainlineScenarios should be reported in the bug tracker.

Multiplayer out-of-sync errors

  • We need wesnoth stdout/stderr output from person who got the error (if you started wesnoth in terminal stdout/stderr is in that terminal).
  • We need savegame from person who got the error.
  • Savegame from some other player if possible.
  • The person who got the error should report the bug, other players can then add their savegames to that bug.


  • In Unix follow the instructions at DebuggingWesnoth to generate information to send to a developer.
  • In NT based OS's (including Win2k, XP) you enable/configure core dumps by running 'drwtsn32', the location of the dumps can be changed there.
  • In Mac OS X, you can enable Crash Reporter -- the output is a backtrace. Run Applications -> Utilities -> Console to see log output. See for information on how to enable Crash Reporter.

Sending savegames, screenshots, coredumps, etc

  • Please compress the files (bzip2, gzip, zip).
  • You can attach files if you submit your bug through Gna!, else
  • Put them on some web or ftp server where we can download them.
  • You can attach files to forum posts.
  • As a last resort you can send them via email to: [1]

Bug protocol

  • When adding a new bug, please choose either "Bug" or "Feature Request" as its Category; it may not be noticed if you leave the Category as "None".
  • We use the Status values "None" (awaiting action), "Fixed", "Won't Fix", "Invalid" (not a bug), "Works For Me" (unreproducible), or "Need Info".
  • A bug which is fixed is marked "Fixed" by a developer, probably the one committing the fix or reviewing it.
  • A bug present in a release is marked "Closed" only upon a new release containing the fix.
  • Any bug present only in WesnothSVN is marked "Closed" when it is fixed.

Who To Bug

This list is intended to give guidance on who developers doing bug triage should assign bugs to. Wesnoth developers who have agreed to take responsibility for particular subsystems, campaigns, or topic areas are listed here.

Maintainer of the mouse interface, also like to fix inconsistencies in the UI or add small usability feature.
Maintainer of Python expert.
Maintainer of Descent Into Darkness campaign.
Animation engine guru, can also help with low-level networking and generic map drawing issues. You can also bug him for unassigned patches.
Maintainer of wmllint, wmlscope. Backup autotools expert, after isaac. Python expert. General toolsmith; if you need a development or auditing tool for WML, talk to him. Co-maintainer of the Northern Rebirth campaign. Resident prose fixer and English-usage pedant, refer spelling errors and storyline copy-edit problems to him.
The master of releases. Also the master of translations and gettext-related infrastructure.
Maintainer of the Eastern Invasion and The Rise of Wesnoth campaigns.
Maintainer of the WML interpreter engine and the UI widget set.
Maintainer of Northern Rebirth campaign.
Mainline campaigns maintainer. Our resident WML quality fanatic.