mirror of
https://github.com/wesnoth/wesnoth
synced 2025-04-28 21:32:01 +00:00
db560619e8
I used "inconsistency" for the actual variable name, because "known" seems more likely to be accidentally reused. I pondered whether to allow the scenario check to go forward, but decided to just make a clean break. Note that this does not prevent any of the information-gathering for the consistency check, just the check itself. Why would you want to use this option? Of course, you should run the consistency check at some point. But if you simply want to recheck if you've fixed all the bugs in your campaign, you might not want to have wmllint slog through data/core again.
The Battle for Wesnoth is a Free, turn-based tactical strategy game with a high
fantasy theme, featuring both single-player, and online/hotseat multiplayer
combat. Fight a desperate battle to reclaim the throne of Wesnoth, or take hand
in any number of other adventures.
The game's source code and artwork, sound, and music assets are provided under
the terms of the GNU General Public License version 2, or (at your option) any
later version. Note that for artwork, sound, and music, we interpret
"preferred form of the work for making modifications" as the modifiable form
that the author chooses to ship us for the source tree. For convenience, a
reference copy of the GNU GPL version 2 is provided in the COPYING file in
this distribution.
Some portions of the source code can be used under different license terms,
whenever stated as such in the source.
See INSTALL for instructions on how to build the game from source code.
A (translated) description of how to play the game can be found in
doc/manual/manual.*.html .
For extensive documentation about all aspects of the game, see the
official Battle for Wesnoth web site:
http://www.wesnoth.org/
The official Battle for Wesnoth Forums (with over 400,000 posts from more than
20,000 registered members) can be found at:
http://forums.wesnoth.org/