Frequently Asked Questions¶
The best way to get answers to your questions is to post them on the Angband forum.
Post on the Angband forum.
Bug reports should include:
your current operating system (e.g. Windows 10)
what version the problem appeared in
the best steps you can figure out to reproduce the bug.
Savefiles that show the problem might be requested, because they help tracking bugs down.
Fix (reduce) the alpha on your screen, or use the “Interact with colors” screen under the options (
=) menu. Navigate to the
n and increase the color intensity with r(ed)/g(reen)/b(lue).
Go into the options menu, choose “Edit keymaps”, then “Create a keymap”. Press Enter at the “Key” prompt and a single space as the “Action”.
And then you’ll probably want to choose to “Append keymaps to a file” so that it persists for next time you load the game.
This just replaces the default action of Enter with a “do nothing but don’t tell me about help” action. If you want to keep the menu available, say on the ‘Tab’ key, you can also remap the Tab keypress to the
Ever-changing and subject to U-turning with public dissent. Discussion typically happens in the Vanilla section of the forums.
Post it on the forums. If people think it’s a good idea, it will generally get some discussion; if they don’t, it won’t. The developers keep an eye on the forums, and ideas deemed OK will get filed for future implementation.
Sometimes a suggestion may not be right for the game, though. Some suggestions would change aspects of Angband that are essential to its nature; Angband has a long history, and so has developed a certain character over the years. Some suggestions might make a good game, perhaps even a better game than Angband, but would make a game that is not Angband. To some extent, variants exist to address this, but even so they tend to adhere to the core Angband principles.
Go to the GitHub page, where you can find the bleeding edge as well as all previous versions.
Please see the compiling section of the manual.
You have two options:
Write your patch and submit it as a pull request on GitHub.
Post about it on the forum.
All contributions are accepted as dual-licenced with both the Angband and GPLv2 licences.
There are contribution guidelines in CONTRIBUTING.md in the top level directory of the source code.
If the patch is a bugfix, then you can reasonably expect it to be integrated into the development tree. If it’s more involved, and the feature is not one that the next version is planned to have, the patch may go through several reviews before being incorporated. It may also just be unsuitable for Angband - in which case, please don’t take rejection badly; you may just be better off writing a variant.
Non-code activities are different. Documentation can be written on the wiki, or if you’re a graphics designer (and they’re always welcome) then please talk on the mailing list about your work.