home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
1,000 Games
/
Disc1.iso
/
ADVEN
/
ADOM0996
/
BUGS.DOC
< prev
next >
Wrap
Text File
|
1997-04-03
|
3KB
|
54 lines
BUGS AND WHAT TO DO ABOUT THEM
------------------------------
ADOM probably contains many bugs (as do most programs of a certain
size). If ADOM somehow crashes you will have to take care of several
things before you can continue to play. You will find the detailed
instructions about how to get ADOM to work once more after a crash
in the readme-file for your system (readme.dos, readme.linux or
readme.amiga).
In case you happen to encounter a bug you probably will have to cope
with one of the following two kinds of bugs:
I) The program exits with an error message (maybe saving your game
before doing so). In this case please note down the _exact_ error
message and describe what you did last, before the program exited.
II) 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-by-
step-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.
After you have collected any 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@saranxis.ruhr.de
Please include the following data (if possible) in the email:
* 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 gam title and the normal version number,
you also need to record the value of 'x':
Alpha Release x
Such a version must not be distributed since it is meant to be used
for alpha testing.
* The system your version is running on
* The bug description (see above)
* Any other comments that you feel would be helpful.
Please do _not_ include any of the following things:
* Binaries of any kind
* Binary patches (rather detail where you believe the mistake to be)
* Flames about this shitty piece of software
* Anything else not specifically requested by the developer
As soon as your bug report arrives, I'll try to do something about
it. Probably you will receive another email requesting more information
or asking specific questions. Should I be able to locate an error
because of your input, your name will be added to the credits and eternal
fame will be yours :-)