/faq.txt

https://bitbucket.org/ekolis/jackband · Plain Text · 150 lines · 110 code · 40 blank · 0 comment · 0 complexity · 988cfc351b0b6b03136904a08a9492ec MD5 · raw file

  1. The Angband FAQ
  2. Posted every other month on rec.games.roguelike.angband and kept
  3. up-to-date on the forum [http://angband.oook.cz/forum].
  4. 1. Issues and problems
  5. a. How do I report a bug?
  6. b. I hate the store interface!
  7. c. Dark monsters are hard to see.
  8. d. I want old-school '#'s as wall tiles, not solid blocks!
  9. e. I use Vista and my display is messed up.
  10. f. I play in the console on Linux, and the colours are screwed up.
  11. g. I'm playing in a terminal and the Escape key isn't working as it should
  12. - I have to press it twice, or just wait a while.
  13. h. Is there a way to disable that thing that pops up when you hit the
  14. enter key?
  15. 2. Development
  16. a. What are the current plans for the game?
  17. b. How do I suggesting an idea/feature?
  18. c. How do I get a copy of the source code?
  19. d. How do I compile the game?
  20. e. How do I contribute to the game?
  21. -----------------------------------------------------------------
  22. 1a. How do I report a bug?
  23. First of all, go to http://trac.rephial.org/wiki and use one or more of
  24. the links there to see if your bug has been reported already.
  25. If you can't find it there, you're best off posting on the forum or the
  26. newsgroup; if it's been reported (several) already, you will get replies
  27. sounding more annoyed as the number of times it's been previously
  28. reported goes up, but so life goes.
  29. Bug reports should *always* include your current operating system (e.g.
  30. Windows XP), what version the problem appeared in, and the best steps
  31. you can figure out to reproduce the bug. Savefiles that show the
  32. problem might be requested, because they help tracking bugs down.
  33. 1b. I hate the store interface!
  34. Sorry, but it's staying that way for now. Expect a better one.
  35. 1c. Dark monsters are hard to see.
  36. Fix (reduce) the alpha on your screen, or use the "Interact with colors"
  37. screen under the options ('=') menu. (On older versions, use the '&'
  38. command.) Navigate to the '8' using 'n' and increase the color
  39. intensity with r(ed)g(reen)b(lue).
  40. 1d. I want old-school '#'s as wall tiles, not solid blocks!
  41. 1e. I use Vista and my display is messed up.
  42. Please see http://angband.oook.cz/forum/showthread.php?t=88 and
  43. http://angband.oook.cz/forum/showthread.php?t=26
  44. 1f. I play in the console on Linux, and the colours are screwed up.
  45. Please see http://angband.oook.cz/forum/showthread.php?t=77
  46. 1g. I'm playing in a terminal and the Escape key isn't working as it
  47. should - I have to press it twice, or just wait a while.
  48. This is a feature of terminals to allow you to enter keypresses that
  49. can't be sent directly. Use the backtick '`' key instead - it's
  50. equivalent in every way to Escape. (This doesn't apply in Sangband, or
  51. NPPAngband.)
  52. 1h. Is there a way to disable that thing that pops up when you hit the
  53. enter key?
  54. Go into the options menu, choose "Interact with macros", then "Create a
  55. keymap". Press Enter at the "Keypress" prompt and a single space as the
  56. "Action". In short: `=m8<enter> <enter>`
  57. And then you'll probably want to choose to "Append keymaps to a file" so
  58. that it persists for next time you load the game.
  59. This just replaces the default action of Enter with a "do nothing but
  60. don't tell me about help" action. If you want to keep the menu
  61. available, say on the 'Tab' key, you can also remap the Tab keypress to
  62. the '\n' action.
  63. -----------------------------------------------------------------
  64. 2a. What are the current plans for the game?
  65. Ever-changing and subject to U-turning with public dissent.
  66. 2b. How do I suggest an idea/feature?
  67. Post it on the newsgroup or the forums. If people think it's a good
  68. idea, it will generally get some discussion; if they don't, it won't.
  69. The developers keep an eye on r.g.r.a and the forums, and ideas deemed
  70. OK will get filed for future implementation.
  71. Sometimes a suggestion may not be right for the game, thougn. Some
  72. suggestions would change aspects of Angband that are essential to its
  73. nature; Angband has a long history, and so has developed a certain
  74. character over the years. Some suggestions might make a good game,
  75. perhaps even a better game than Angband, but would make a game that is
  76. not Angband. To some extent, variants exist to address this, but even
  77. so they tend to adhere to the core Angband principles.
  78. 2c. How do I get a copy of the source code?
  79. It depends what you want it for. If you want to start a new variant,
  80. you may want to start with the last stable release of the game (maybe
  81. 3.0.9, for example). If you're more interested in hacking on Vanilla
  82. Angband, then you really want to get hold of the latest development
  83. version. Luckily, both are easy.
  84. The latest version's source is linked to from the page http://rephial.org/.
  85. To get the SVN trunk, get Subversion [http://subversion.tigris.org/] for
  86. your system, and checkout the repository
  87. "http://rephial.org/angband/trunk/". On the commandline, this would be
  88. done like so: "svn co http://rephial.org/angband/trunk". You'd do well
  89. to read a Subversion primer, too.
  90. 2d. How do I compile the game?
  91. Please see http://rephial.org/wiki/Compiling for an up-to-date guide to this.
  92. 2e. How do I contribute to the game?
  93. First, join the mailing list
  94. [http://angband.oook.cz/mailman/listinfo/angband-dev].
  95. If you already have a patch you want to be included, please send it to
  96. the mailing list in the form of a unified diff against either the SVN
  97. trunk (e.g. using svn diff) or the latest public release. Please be
  98. careful to follow the Angband coding guidelines
  99. [http://rephial.org/wiki/CodingGuidelines]. All contributions to
  100. individual files are accepted under the licences used in the file
  101. header. Make sure you're OK with this before sending in patches.
  102. If the patch is a bugfix, then you can reasonably expect it to be
  103. integrated into the development tree. If it's more involved, and the
  104. feature is not one that the next version is planned to have, the patch
  105. may go through several reviews before being incorporated. It may also
  106. just be unsuitable for Angbandâ&#x20AC;&#x201D;in which case, please don't take
  107. rejection badly; you may just be better off writing a variant.
  108. Non-code activites are different. Documentation can be written on the
  109. wiki, or if you're a graphics designer (and they're always welcome) then
  110. please talk on the mailing list about your work.