home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Crawly Crypt Collection 2
/
crawlyvol2.bin
/
games
/
wc08h
/
docs
/
read_me.txt
< prev
next >
Wrap
Text File
|
1995-01-05
|
5KB
|
92 lines
Some general notes
******************
* Using NVDI 3.01 you won't be able to use size 18 of the system font
as this version of NVDI doesn't scale it properly when using the V_GTEXT
command (VDI 8).
* Using TT low resolution and possibly other 256color modes the game window
won't show the propper gamemap when NVDI 3.01 is active as obviously
this version of NVDI isn't able to do the V_GET_PIXEL command rightly
(VDI 105), which I use to generate the map.
* If you want to play this game read the files WC_ENG.TXT and WHATSNEW.TXT
first.
* When using other serial ports than 'modem 1' or higher transfer-speed
than 19200 bps, use the cpx-module for setting the serial interface
before attempting to establish a datalink. The game will always
use the port that is indicated in the cpx-module.
* Never use two different game versions to play a datalink mode game.
* When playing datalink games always be sure, that you really have loaded
the same scenario on both computers as the game will sooner or later
crash if only the slightest details differ. Note that the game does
only check if the scenario filenames match on both computers.
* You can only play the game in the modem mode, if you have a modem that
is able to use V42/V42bis protocol.
* When playing WORLD CONQUEST in a MultiTOS environement switch off the
sound and be sure to have the ALERT.ACC switched off.
(Since MultiTOS v1.08 switching of the sound is not necessary any more)
However, because the game is rather slow, it is not advisable to play
it with MultiTOS anyway.
* Save often (use the AutoSave feature) to avoid datalosses as this game
is far from being a perfect program.
* If you find bugs, please do report them. (use the bugreport form)
* In the editor window of the WORLD EDITOR you have to use the right
mousebutton! Sorry, I programmed this when I knew only little about
GEM programming.
* Don't be hasty when playing WORLD CONQUEST on a slow (8 MHZ - no Blitter)
machine, as it can behave strangely when mistreated!
I know this game is slow (sorry for that). Unfortunately I'm more a
gamer than a programmer. It helps much if you use a program to
speed ATARI's VDI up, like NVDI for an example.
* There was a bug in the WORLD EDITOR version 1.1 that allowed city zone
coordinates to exceed the maximum map size. As up to version 0.7g these
values were not verified by the game, crashes could occur when playing
against the computer.
The official scenarios affected are: WORLD_1.SCN and EUROPA.SCN. If you
play these with game versions less than 0.7h be sure to correct the zone
sizes first using the WORLD EDITOR.
Maximum y coordinate is: 107
Maximum x coordinate is: 149
* Never start WORLD CONQUEST after a system crash occured (bombs on the
screen). Be sure to always switch the computer off after such an event
and before trying to play this game.
* Install this game on your hard disk (if you have one) as saving a
game position takes quit some time. There could occur problems, when
trying to run the game from hard disk on a computer with only 1 MB RAM,
as some hard disk drivers use a lot of memory.
* The "mysterious map bug" seems frequently (but not always) to occur
during a datalink game after a saving of the game caused by the remote
computer. If it occurs, just click through the alert boxes, that will
appear, fix the map, as suggested by the last alert box, and wait until it
is again your turn. Then save the game off just once and the "mysterious
map bug" won't bother you again.
The "mysterious map bug" does never occur on a TT or FALCON. Up to now it
is only known to me to have appeared on STf 1040 with 1MB RAM and TOS
versions 1.0 up to 1.2.
* If you experience a deadlock, playing the game with two computers using the
datalink mode, please contact me and send (if possible) a disk
holding the saved game position files of both computers of the game
affected along with a detailed describtion of what moves you carried out
just before the deadlock, as well as what other strange reactions the
program showed (if any) in the whole game before the crash. I know how
frustrating such an event is after hours of playing but nevertheless
please take some extra time to write me a letter as: bugs can only be
mended when reported.