PageRenderTime 18ms CodeModel.GetById 16ms app.highlight 1ms RepoModel.GetById 0ms app.codeStats 0ms

/faq.txt

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