home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Merciful 3
/
Merciful_Release_3.bin
/
software
/
b
/
breed96.dms
/
breed96.adf
/
breed6.doc
< prev
next >
Wrap
Text File
|
1980-05-20
|
5KB
|
138 lines
{1} Editing the scenarios
{2} Overview
The scenario file is just a text file which may be editted in a normal
text editor such as MicroEMACS on your workbench disk. You should look at
the Breed disk in the scenarios directory and load up a scenario. It is
easiest just to change an existing file and save it to a new scenario
name. Please note that the Breed program looks for scenario numbers
sequentially and therefore if (say) the last scenario is named
scenario24.scn then you should make your next user defined scenario
called scenario25.scn.
{2} File names
File names are named with this convention
scenario999.scn where 999 is the number of the scenario and must
be the same as in the files scenario number.
{2} Order of file
There are 6 sections of the scenario file that you must have in your
file.
<Scenario> followed on the next line by the scenario number.
<Short> followed on the next line by a sort description of the scenario
(1 line).
<BeginText> Followed on the next lines by a description of what is
required of the user in the scenario. The description must be no longer
than 10 lines and must have columns of no longer that 40 width. You can't
have any commas in the description.
<InitVars> must have the variables P,H,A,D,C as described below.
Each statement occupying one line only.
<WinVars> using the normal variables each occupyin one line only.
<LoseVars> doing the same.
Here is when you need in the file:
<Scenario>
...
<Short>
...
<BeginText>
...
<InitVars>
...
<WinVars>
...
<LoseVars>
...
<End>
{2} Variables used
You can use the planet variable only in the init variables section.
eg P 2 - Which sets your home planet to Lycan.
Planets Units
%%%%%%%%%%% %%%%%%%
1. Sun 1. Commerce centre
2. Lycan 2. Observatory
3. Denari 3. Mining station
4. Holopox 4. Residential Unit
5. Plenus 5. Docking port
6. Uropa 6. Food Generator
7. Eijo 7. Law centre
8. Pesoek 8. Power Station
9. Easma 9. Road
10. Ymeth 10. Disruptor
11. Belgold 11. Droid
12. Quantol 12. Alien
13. Vlech 13. Ore silo
14. Drusul 14. Food silo
15. Tralmath 15. Probe
16. Venitar 16. Cargo Shuttle
17. Battle cruiser
Others Variables for 18. Laser Drone
Win and lose sections 19. Space station
%%%%%%%%%%%%%%%%%%%%% 20. Diplomat vessel
O Ore 21. Weapon update
$ Credits 22. Shield update
T Traffic rate 23. Cargo hold update
R Rating 24. Ship speed update
I Population
F Food
A1 Planets owned by Federation
A2 Planets owned by Tsepan
A3 Planets owned by Seraunde
A4 Planets owned by Mutants
P Planets owned by you
E Energy on home planet
For initialsing the variables
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
P x (where x is a planet number in the above list)
H x (where x is hardness from 0 easy to 3 hard)
A x (where x is the alien you are. 1 = Federation,
2 = Tsepan,
3 = Seraunde,
4 = Mutant)
D x (where x is the date from 2040. eg 000 = 2040.00, 134 = 2041.34)
C x (where x is the amount of credits you begin with)
{2} Operators
The scenario interpreter recognises these symbols
Symbol Meaning
%%%%%% %%%%%%%%%%%%
> greater than
< less than
= equal to
! not equal to
{2} Specifying the number of units
You can specify the number of units in the win and lose sections
using this convention. For example
U13 > 4 means you need more than 4 ore silos. Ore silos is gained
from the table described above with the entry number 13.
{2} Win and lose variable sections
In the winvars and losevars section a strict set of rules apply. For
each line you must specify only 1 rule. For example F < 20 means that
the amount of food on your planet is less than 20.
For the warvars to be satisfied all of the rules must be satisfied in
that section. That means that if you have I > 1000 in your winvars
section then you can only win the scenario if you have more than 1000
people in your population.
{2} Please note
It is not intended that the "average" user will find making new
scenarios very useful. The addition of editable scenario files was made
for the ease of use of the programmer and to allow additional scenario
files to be emailed around. Please note that I may have left out some
variables that have been included in the scenario files.
{EOF}
{EOF}