Professional Documents
Culture Documents
===-----------------------------------===
The ADOM Fluff FAQ
An attempt to answer all meta-questions regarding ADOM...
(C) Copyright 1994-2015 by Thomas Biskup.
All Rights Reserved.
===-----------------------------------===
============--------------------------------------------------============
-------------------------------------PREFACE
This document tries to answer all the meta-questions regarding
the distribution of the game called ADOM (shortcut for 'Ancient
Domains Of Mystery).
If you plan to distribute ADOM in some way (be that on disk, CD, in
a magazine or whatever), make sure to read Section I: The ADOM
License.
If you plan to write a review of ADOM, please make sure that you read
Section II: ADOM in the Media.
If you would like to submit ideas to further ADOM's development, make
sure that you have read Section III: ADOM Development.
If you are having problems related to the game itself, you might want
to read section V: Game-Related Questions closely.
If you are experiencing technical problems with ADOM, make sure that
you read Section VI: Technical Problems.
Before reporting a bug you should definitely read Section VII: Bugs.
If you never installed ADOM before, you might want to examine Section
VIII: Installation.
Finally questions regarding the installation of ADOM are addressed in
section VIII: Installation.
Any other questions might be answered in Section IV: Miscellaneous
Stuff.
Questions answered by this text will be ignored if you ask them
by email. RTFM, as they say...
If you feel that this document is incomplete, feel free to email
questions and suggestions to adom@adom.de.
Hearty thanks to Stefanie Woll for proof-reading this text :->
All remaining idiosyncrasies are intended to ensure the Ancardian
feeling of the text ;-)
-- Thomas Biskup
May, 1998
===--------------------------------------------------------------------===
TABLE OF CONTENTS
===--------------------------------------------------------------------===
Section
A.
B.
C.
D.
I
- The ADOM License.
Terms of use.
Distributing ADOM in magazines, on disks, etc.
The Postcard Quest.
Licensing ADOM and other commercial ventures.
Section
A.
B.
C.
D.
E.
F.
G.
IV - Miscellaneous Stuff.
Why aren't my emails answered?
Why is the website for ADOM out of date?
Who is Thomas Biskup?
Why has the savefile of my character disappeared after he died?
Why are requests for advice not answered?
Does Thomas Biskup enjoy receiving binary files?
When will the next version of ADOM be released?
Section
A.
B.
C.
D.
E.
F.
G.
H.
I.
J.
K.
L.
M.
N.
O.
P.
V
- Game-Related Questions.
What's the relation between the Mad Minstrel and the village fool?
How much weight is 'one stone' actually?
Why can't I increase my weapon skills?
All my characters start out cursed. Why?
How can I activate a ring of djinni summoning?
What's a 'si'?
Why does fire damage my character despite immunity to fire?
What about the Red Rooster and associated mysteries?
What's the best class/race combination?
Why is the number of charges for wands I zapped not displayed?
Why are scroll names readable for illiterate characters?
Why are all classes able to learn weapon skills equally well?
I can't use command 'xyz'. Why not?
What do 'scurgari' look like?
Are there any cheat codes in ADOM?
Why are blank scrolls labeled?
Section
A.
B.
C.
D.
VI - Technical Problems.
General troubleshooting.
DOS
Windows 3.x, Windows for Workgroups, OS/2
Windows NT, Windows 95
E. Linux/FreeBSD
Section
A.
B.
C.
VII - Bugs.
How to submit bugs?
Which bugs are known?
Command 'xyz' does not seem to work in my version...
III.A. I have some great ideas concerning ADOM. Are you interested?
====================================================================
Every day I receive about 10 emails concerning ADOM (that's more
than 3000 per year). Many of them contain suggestions and many
of those suggestions have been repeated again and again. Some
of the more common suggestions and my replies to them have been
compiled below:
1. How about a multi-player version of ADOM?
ADOM's source code really is not prepared to handle
multi-player code. It would be possible to add this
feature if either a team of professional programmers
worked on it or someone provided me with a
lot of hardware and a lot more free time than I have
these days. Until then, forget it!
2. How about a graphical version of ADOM?
Graphics would be nice, yes. But they would have to
be done in a very professional way. Adding graphics
like those in Nethack is too much work for too little
gain as far as I am concerned. Again, a professional
team of artists and programmers would be able to do
it, but since neither is available, forget about if for
the time being!
If you feel you could do it, do not contact me about it
before you can show me at least 20 samples of graphical
tiles for the game. There have been too many offers
the one time I tried this without ever getting something
out of it...
3. How about a BBS version of ADOM?
I already talked to someone about this and this topic
might be tackled after 2.0.0 is done.
4. How about an attribute roller?
Maybe at some point, but then in a shareware version of ADOM.
5. How about a cheat mode?
See #4.
6. How about monster inventories?
Being implemented right now. Due to the complexity of this
issue quite a number of versions will go by until this
feature is completed.
7. How about more races?
I'm very hesitant about adding new races to the game, since
ADOM has been designed with a background in mind and is more
than just a collection of everything including the kitchen
sink like Nethack. Thus there won't be races like vampires,
all the secrets right away once a new version is released. The bad
effect (for some people) is that they can't toy around with the sources,
create variants, etc. I can live very well with that and thus it will
happen.
III.F. What about ADOM variants?
================================
There won't be any as far as I am concerned.
My reasoning behind this is two-fold:
1. To me ADOM is more than just an exercise in creating a
tactically interesting game. It's a breathing world and
it's my child. Therefor I'd hate to see others toying
around with it just to turn it into a munchkin-fest.
2. I already receive more than 3000 emails per year concerning
ADOM. Some of those emails come from incredibly stupid
people (luckily most of them do not). Those folks are not
even able to take a quick glance at the manual. They also
refuse to notice that I'm not responsible for whatever
variants there might be. I don't want to receive another
3000 emails per year concerning variants I don't know anything
about and I'm not interested in.
This for sure would happen. If you don't believe me write
a game as successful as ADOM and you'll see. In the heyday
of activity I spent roughly an hour per day on reading ADOM
email and news postings, which is more than I realistically
can afford, because I also love my work, my life and my other
hobbies.
III.G. Will ADOM be ported to 'xyz'?
====================================
Eventually (probably in the 1.x.y release series). Over the past couple of
years there have been volunteers for the following systems:
OS/2
BeBox
Native Windows NT
Nextstep
Archimedes
MacLinux
Unix
Solaris/SPARC
Falcon
Native Windows 95
HPUX/DEC ALPHA Macintosh
SGI
SunOS/Solaris 1.x/2.x
UnixWare
IBM AIX
MVS
AIX 4.1.x, 4.2.x, 4.3
Many of them probably won't be available after all the time that has
passed. Our strategy (read: Jochens and mine) right now is to port
ADOM ourselves to all the systems we would like to support.
If you'd like to port ADOM to a system not yet mentioned in that
list, feel free to contact me at adom@adom.de.
III.H. How about some technical details about ADOM?
===================================================
ADOM is written in C and compiled with the help of GNU make (or any
other make) and one Perl script (to compile the in-game manual). As of
-*- As far as I know the Curses libraries I use at least on some systems
still expect 7-bit ASCII characters -- thus there is no way of using
all those fancy special characters in various languages.
-*- I'm a bit doubtful of the will of
of text in ADOM -- especially all
each version. It's a lot of work
for Canton chinese suddenly drops
don't grow on trees, you know.
===--------------------------------------------------------------------===
Section V: Game-related Problems.
===--------------------------------------------------------------------===
V.A. What's the relation between the Mad Minstrel and the village fool?
=======================================================================
Fnord. You are not cleared for this kind of information.
blades favored by the drakeling people all over Ancardia. The blade
actually runs around the outer bow, while the inner bow has a small
spike protruding from it (roughly in the center).
V.O. Are there any cheat codes in ADOM?
=======================================
All cheat codes may be found in the ADOM General Spoiler FAQ.
V.P. Why are blank scrolls labeled?
===================================
Or: Wouldn't it be more logical to label "blank scrolls" as "blank
scrolls". The idea behind this is taken from the way cursed scrolls
used to work in ancient editions of D&D. The curse would take effect
as soon as you open the scroll to read it. Thus, by default, all
scrolls are potentially dangerous and you need to unbind them and read
them to determine their type. Only then you will see whether the scroll
is blank or not. Thus "blank scrolls" appear to be labelled at first
(meaning that you haven't identified them - and maybe there's even
some kind of label on the outer side).
===--------------------------------------------------------------------===
Section VI: Technical Problems.
===--------------------------------------------------------------------===
VI.A. General troubleshooting.
==============================
Two major sources of problems with ADOM are known:
1. Lack of disk space.
Make sure that you have enough disk space to handle a file
twice the size of your current save file (ADOM creates lots
of temporary files which take up size).
2. Screen resolution.
ADOM is able to work with different screen resolutions. It can
make use of both 80x25, 80x50 (or whatever) screens. Sadly, the
save files can't be exchanged. If you started to play in one
specific resolution, you also have to activate that resolution
before restoring a saved game. Everything else could lead to
disaster.
3. Turning off the computer without quitting ADOM beforehand.
This will prevent ADOM from cleaning up its file structure.
There might be all kinds of problems as a consequence. The
least you can do is to delete 'adom.prc'.
VI.B. DOS
=========
* ADOM needs a DPMI host to run. If you don't have installed a DPMI
server you can use the free DPMI server included in the ADOM package.
So far I was able to fix all encountered bugs, but if you notice
strange crashes under Linux, please tell me about your libc version.
* ADOM seems to encounter a variety of problems if your directories are
spread with links across a network -- that's a real problem :-^
* If you experience problems with colors, you might try to use one of
the following termcap entries (version A & B).
If you experience problems with colors, you might need to upgrade
your version of NCurses. After installing the ncurses-base_4.2-1
package (which contains only the "linux" terminfo entry and a few
other common ones like "vt100", and no libraries), ADOM g10 will
correctly display colors under Linux.
If you cannot install the later version of NCurses, you might want
to use either of the following procedures to fix the termcap
entries:
VERSION A:
==========
Erwin Andreasen provided this entry; be warned -- it's just a hack).
This seems to be needed for the latest versions of ADOM (starting with
Gamma 10), which now are compiled with NCurses 3.0, when playing under
Debian.
Here's the workaround:
linux|console|con80x25|dumb,
am, bce, eo, mir, msgr, xenl, xon,
colors#8, cols#80, it#8, lines#25, pairs#64,
bel=^G, blink=\E[5m, bold=\E[1m, civis=\E[?25l,
clear=\E[H\E[J, cnorm=\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub1=^H, cud1=^J, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu1=\E[A, dch=\E[%p1%dP,
dch1=\E[P, dl=\E[%p1%dM, dl1=\E[M, ed=\E[J,
el=\E[K, flash=\E[?5h\E[?5l, home=\E[H, ht=^I,
hts=\EH, ich=\E[%p1%d@, ich1=\E[@, il=\E[%p1%dL,
il1=\E[L, ind=^J, ka1=\E[1~, kb2=\E[5~, kbs=^H,
kc1=\E[4~, kc3=\E[6~, kcub1=\E[D, kcud1=\E[B,
kcuf1=\E[C, kcuu1=\E[A, kdch1=\E[3~, kend=\E[4~,
kf0=\E[21~, kf1=\E[[A, kf10=\E[21~, kf11=\E[23~,
kf12=\E[24~, kf13=\E[25~, kf14=\E[26~, kf15=\E[28~,
kf16=\E[29~, kf17=\E[31~, kf18=\E[32~, kf19=\E[33~,
kf2=\E[[B, kf20=\E[34~, kf3=\E[[C, kf4=\E[[D,
kf5=\E[[E, kf6=\E[17~, kf7=\E[18~, kf8=\E[19~,
kf9=\E[20~, khome=\E[1~, kich1=\E[2~, kll=\E[4~,
knp=\E[6~, kpp=\E[5~, kspd=^Z, nel=^M^J,
op=\E[37;40m, rc=\E8, rev=\E[7m, ri=\EM,
rmacs=\E[10m, rmir=\E[4l, rmpch=\E[10m, rmso=\E[m,
rmul=\E[24m, rs1=\Ec, sc=\E7, setab=\E[4%p1%dm,
setaf=\E[3%p1%dm, setb=\E[%p1%'('%+%cm,
setf=\E[%p1%{30}%+%cm, sgr0=\E[0;10m, smacs=\E[11m,
smcup=\E[r\E[H, smir=\E[4h, smpch=\E[11m,
smso=\E[7m, smul=\E[4m, tbc=\E[3g,
u6=\E[%p1%d;%p2%dR, u7=\E[6n, u8=\E[?6c, u9=\E[c,
(yes, the trailing comma is correct)
"tic linux.ti", and adom will run with the correct colors.
The recompiled termcap will be placed in /usr/lib/terminfo, or the
place pointed to by the $TERMINFO encironment variable.
A note for FreeBSD users (thanks to Walter Hafner for making this
known to me): FreeBSD usually does not seem to have a terminfo database.
You can create one from termcap by typing
'tconv -c -B /usr/share/misc/termcap'
(at your own risk ;-).
* You want colors under X? This also is possible. Try the following
(thanks to Massimo Campostrini <campo@mailbox.difi.unipi.it> for
providing the information):
Include in your resource file (possibly ~/.Xdefaults)
xadom*color0:
xadom*color1:
xadom*color2:
xadom*color3:
xadom*color4:
xadom*color5:
xadom*color6:
xadom*color7:
xadom*color8:
xadom*color9:
xadom*color10:
xadom*color11:
xadom*color12:
xadom*color13:
xadom*color14:
xadom*color15:
xadom*background:
xadom*foreground:
xadom*cursorColor:
#000000
#ff0000
#00ff00
#ffaa00
#2222ff
#ff00ff
#00ffff
#ffffff
#666666
#ff5555
#00aa00
#ffff00
#8888ff
#ff69b4
#00aaaa
#aaaaaa
#000000
#ffffff
#00ff00
xadom*VT100.Translations:
#override \n\
<Key>R7:
string("7") \n\
<Key>R8:
string("8") \n\
<Key>Up:
string("8") \n\
<Key>R9:
string("9") \n\
<Key>R10:
string("4") \n\
<Key>Left:
string("4") \n\
<Key>R11:
string("5") \n\
<Key>R12:
string("6") \n\
<Key>Right:
string("6") \n\
<Key>R13:
string("1") \n\
<Key>R14:
string("2") \n\
<Key>Down:
string("2") \n\
<Key>R15:
string("3") \n\
None<Key>KP_1: string("1") \n\
None<Key>KP_2: string("2") \n\
None<Key>KP_3: string("3") \n\
None<Key>KP_4: string("4") \n\
None<Key>KP_5: string("5") \n\
None<Key>KP_6: string("6") \n\
None<Key>KP_7: string("7") \n\
None<Key>KP_8: string("8") \n\
None<Key>KP_9: string("9") \n\
before doing so). In this case please note down the _exact_ error
message and describe what you did last before the program exited.
If ADOM dumps some binary data, please also note it down exactly!
2. The program crashed without giving any hints why it would do so.
This is very, very bad... try to remember what you did last. Try to
reproduce the error. If you manage to reproduce it, write a step-bystep description on what one has to do to see the error. If you do
not manage to reproduce it, try to describe what you did last in as
much detail as possible.
Look for a file called 'adom.err' (it should be somewhere on your hard
disk in case of crash type #1). Copy it and send it to me together with
your bug report.
After you have collected all necessary data about the error as described
above, try to make the problem known to the developer. This is possible
if you have access to Internet EMail. If you do have such access, write
an email to the following address:
adom-bugs@adom.de
If you have access to the World Wide Web, you preferrably will use
the automated bug report form at
http://www.adom.de/bugs
which ensures, that all necessary data will be there.
Please include the following data (if possible):
* The version of ADOM you are using; please look carefully at the
title screen of your game version. If your version lists the
following text below the game title and the normal version number,
you also need to record the value of 'x':
Gamma Release x
* The system your version is running on (OS name, OS version).
* The bug description (see above).
* Any other comments that you feel would be helpful.
* Your full real life name (so that I can include you in the credits
section in case you have discovered a new bug).
Please do _not_ include any of the following things:
*
*
*
*
===========================================================
You probably copied ADOM over an older installation. ADOM's keyboard
definitions are contained in a file called 'adom.kbd'. Delete that file
and ADOM automatically will create a new file for you.
If you have added customizations of your own to that file you would
like to keep, you also might want to try to type 'adom -k -r'. This
will have ADOM create a file called 'keyref.kbd' which contains all
command definitions for the current version of ADOM.
===--------------------------------------------------------------------===
Section VIII - Installation.
===--------------------------------------------------------------------===
VIII.A. DOS, OS/2, Windows xyz
==============================
Installing ADOM is very simple. This section will tell you how to
install ADOM step by step. An example will explain each step. <ENTER>
means that you have to press the enter key after that command. The '>'
represents the command prompt of the DOS shell.
Let's assume that you want to install ADOM on your hard disc drive C: in
the directory \games\adom. The file ADOM-xxx.ZIP (xxx is normally the
current version number, e.g. 099) for the sake of the example is located
on your floppy drive B:. The directory C:\GAMES already exists. You
need to do the following:
c: <ENTER>
cd \games <ENTER>
mkdir adom <ENTER>
cd adom <ENTER>
copy B:\ADOM-xxx.ZIP <ENTER>
pkunzip ADOM-xxx.ZIP <ENTER>
del ADOM-xxx.ZIP <ENTER>
This will install the archive at the location you intended it to be (in
the example).
Next you will have to set an environment variable which will tell ADOM
where to look for the highscore and where to save games. To do this you
will have to edit the autoexec.bat file in the root directory of your
boot drive (C: in most cases). Add the following line at the end of the
autoexec.bat and then save the file:
SET ADOM_HOME=C:\GAMES\ADOM
It is important to use the complete path, drive letter included. Finally
you have to add the directory chosen for ADOM_HOME to your path. After
you have done this just reboot the computer. Now you should be able to
play ADOM.
If you don't set the ADOM_HOME environment variable, ADOM will create
all necessary files during the game and the highscore file in the
directory you started ADOM in.
VIII.B. Linux
=============
When installing ADOM you have two choices. If you have access to root
privileges you can install Linux system-wide. If you are just a simple
user, installing ADOM is also possible.
* Uncompressing the package
-------------------------Distributions of ADOM usually consist of one file either called
'adom-xyz-elf.tar.gz' or 'adom-xyz-aout.tar.gz'. The 'xyz'
normally corresponds to the version number contained in the distribution
(e.g. 070 for version 0.7.0). To install the package you need to issue
the following two commands:
gunzip adom-xyz-aout.tar.gz
tar xf adom-xyz-aout.tar
After doing this you should change to the new directory (called 'adom')
and then continue as described below depending on whether you have root
privileges or not.
Installing ADOM globally will be a bit of work so that you should try the
local version if you just want to take a quick look at it. If you
like what you see you can still install it globally.
* If you _do_ have root privileges:
----------------------------------The following description will assume that you want to use the
directory '/var/lib/adom' as your global highscore directory and that
the binary itself will be installed in the directory '/usr/games'.
First of all you will have to create a new user (e.g. named 'adomown')
and a new group (also named 'adomown'). To create the new group you
will have to add the following line to your /etc/group file:
adomown:*:<gid>:adomown
The term <gid> has to be replaced by the smallest number larger than
99 that is not used by any other group. Note the number. You will
need it once more.
To create the new user you will have to add the following line to the
/etc/passwd file:
adomown:*:<uid>:<gid>:adomown:/usr/games:
The <gid> term has to be replaced by the number you used above for the
group entry. The <uid> term has to be replaced by a valid user id.
Next you will need to copy the adom-binary to the /usr/games
directory. Then enter the /usr/games directory and type the following:
chown adomown.adomown adom
chmod +x adom
chmod +s adom
Now we are nearly done. You need to create the highscore directory
/var/lib/adom. The directory has to be owned by 'adomown' (both user
and group ownership). The correct privileges can be set with
to hold
to hold
to hold
to save
for the
for the
for the