                          BATTLECRUISER GAME BUILDER SYSTEM

Last Updated: 5-19-99

===============================================================================

#1 - These files are copyright 3000AD and ANYONE releasing them will be
     subject to copyright infringement proceedings. Furthermore, I can
     easily invalidate ALL files with a simple patch, rendering any
     released version of these utilities useless with the BC3K runtime
     model.

#2 - There is NO *official* support for for the BC3K Game Builder System. If
     you need assistance, post a message in the COMMLINK section of the website
     and a tester, familiar with the system, will respond. The use of the GBS
     could potential invalidate your BC3K install environment, forcing you to
     re-install the software. Use at your own risk.

#3 - You NEED a working BC3K runtime environment to use these tools. Create
     a folder on your hard drive in the same tree as your BC3K install and copy
     this folder and sub-folders there. So for instance if you installed to
     C:\BC3000AD, you would create C:\BC3000AD\GBS and then copy these files
     there. Do *NOT* try to execute these files from the CD-ROM

#4 - Don't even ask for docs. This is all you're getting. You're on your
     own henceforth.

===============================================================================
                                  DIRECTORIES
===============================================================================

This entire structure contains files required to create objects and missions
for BC3K. Since the file format changes across versions, you have to ensure
that you have the latest versions. Patches can and will cause the internal
file structures to change. If this happens, a patch for the GBS will also be
made available. All user created scripts will need to be re-parsed in order to
be compatible with the new version of the software.

.\        - Contains components used to embed AI and other parameters into
            objects, as well as parse mission and AI scripts to binary format.

3DSOBJ    - contains sample 3DStudio Rel 4 objects to show how these objects
            can be converted to the 3000AD .3D format using the TED2ASC.EXE
            utility. It converts the .ASC file to .3D and converts the .BMP
            texture to .PCX. Run it without parameters to see usage instructions

DOCS      - Various docs (new maps with anomaly links courtesy of
            Mark 'SpcFx Giao)

OBJECTS   - Contains .3D objects in the game. Some were originally .ASC
            files converted to .3D and then manipulated using TED to add
            animation and other AI vectors as well as scaling etc. Building an
            object from scratch in TED is not for the feint at heart. If you
            know how to use 3DStudio.

OBJTEX    - Object textures. Once you've converted a .BMP to .PCX file for a new
            object, copy it here or TED won't find it. You can of course use
            another directory but you have to modify the BCTOOLS.INI file.

PTETEX    - Surface textures. Do not mess around with these!

REGIONS   - World .3D files

ART       - Misc images

SFX       - Soundfx files

FX        - Animation files

BIN       - Tools

===============================================================================
                            LIST OF DOCS
===============================================================================

GBS.PDF      Mission builder docs (work in progress)
OBJECTS.TXT  List of objects in the game that can be used in scripts
REGIONS.TXT  List world regions in the game that can be used in scripts
TRADEITM.TXT List of index trade items that can be used for 'stores' in scripts
SOUNDFX.TXT  List of soundfx in the game that can be used in scripts
TED.TXT      Docs for TED object/world editor
TEDKEYS.TXT  Keyboard commands for TED

  FOR REF, YOU WILL ALSO NEED ALL THE APPENDIX FILES WHICH WERE INSTALLED BY
  BC3K IN THE DOCS FOLDER.

  YOU ARE ADVISED TO PRINT OUT THE NAV MAPS SO THAT YOU KNOW HOW THE WORLD IS
  LAID OUT AND ORGANIZED.

===============================================================================
                                   UTILITIES
===============================================================================

PREPARE.EXE  - Used to parse 3D objects, scripts etc. For now, I'm only
               concentrating on mission scripts because showing how to do
               objects for introduction into BC3K is a whole new ball game.

               This is a DOS program. Execute from a DOS Window.
               Usage : See GBS.TXT

CV3D.EXE     - Used to convert .3D binary files to .3DT text files and vice
               versa

               This is a DOS program. Execute from a DOS Window.
               Usage : Execute without parameters to see the usage

TED.EXE      - Object Editor. See TED.TXT and TEDKEYS.TXT. Modify BCTOOLS.INI
TEDWIN.EXE     before running the WIN9x version. See TED.BAT before running
               the DOS version.

               The DOS version takes .PCX screen shots and the WIN32 takes
               .BMP screen shots. These are now stored in the folder where the
               executable file resides.

               This is DOS/WIN95 program
               Usage: See TED.TXT

TED2ASC.EXE  - Use to convert 3DStudio Rel 4 or 3DStudio MAX .ASC files to
               .3D format and vice versa. Also converts .BMP to .PCX files.

               This is DOS program. Execute from a DOS Window.
               Usage: Execute without parameters to see the usage

PCX2CAF.EXE  - Use to convert .PCX images to .CAF format.

               This is a DOS program. Execute from a DOS FULL-SCREEN session
               Usage: PCX2CAF *.PCX

BUILDLIB.EXE - Use to create resource files

PLAYMOD.EXE  - BC3K cheat utility

FEWIN.EXE    - BC3K Frontend access utility

MAPEDIT.EXE  - Use to create planetary mission zones

MAPMAKE.EXE  - Use to create surface mission zone .PTE maps from .SCR files

===============================================================================
                    HOW TO BUILD A SAMPLE SCRIPT
===============================================================================

Read the GBS.TXT file. It's not quite complete but it contains all the
essential info.

A sample script and description file is provided.

    - Run MAKE.BAT

    - Copy bc3k9800.mis, bc3k9800.dat, bc3k9800.des to your SCRIPTS folder

    - Run BC3K and select the SAMPLE scenario from the list in MISCON

The source script file, bc3k9800.scr is in plain English. Read it!

===============================================================================
                   HOW TO BUILD/IMPORT 3DSTUDIO OBJECTS FOR BC3K
===============================================================================

See the section at the end of TED.TXT file in the DOCS folder

===============================================================================
                   HOW TO REPLACE THE SOUNDFX
===============================================================================

The SOUNDFX.TXT file lists all the sounds in the game.  You can replace each and
every one by recording an 11025hz, 8-bit stereo WAV sample and putting it in the
SFX folder.  As long as the name is the same as the one listed in the
SOUNDFX.TXT file, it will be used instead of the one in the resource file.

So, you could change the BC laser fire by replacing the BAT11.WAV. In this
manner, not only can you replace each and every soundfx in the game, you can
also replace personnel voicefx as well.

All files are in the SFX folder. The original BAT11.WAV and BCV81AFO.WAV
files are included. Use these to get the proper WAV file format.

===============================================================================
                   HOW TO REPLACE THE PERSONNEL IMAGES
===============================================================================

Tactical gets its personnel images from the PILOTS.PCX and OFFICERS.PCX files.
Looking at this file, you can create your own personnel images and copy these
files over to the SCRIPTS folder.

The BC bridge and other cockpits, get personnel and external images from
individual files that are named accordingly. By replacing these files, you
will be able to change the crew, pilots and other persona in the game.

In all cases, you MUST use the same palette, file name and dimensions. So if
you wanted to replace pilot Roamer's image, you would (a) create a PCX image of
the same dimension, palette and file name as ROAMER.PCX (b) make a copy and
shrink it to so that when you paste it, it fits within the allocated space
in PILOTS.PCX. Then, copy the new ROAMER.PCX (the one you didn't shrink) and
PILOTS.PCX images to the SCRIPTS folder.

All files are in the ART folder.

===============================================================================
                   HOW TO REPLACE ANIMATION EFFECTS FILES
===============================================================================

You can also replace animation effects such as jump animation, explosions,
laser fire etc, by simply (a) creating your own in .FLC or .FLI format using
the game palette from any of the images in the ART folder (or from an in-game
screen shot) (b) extracting the frames to sequential individual PCX files
and (c) using the PCX2CAF utility to convert each frame to .CAF format then
(d) copying the files to the SCRIPTS folder.

In the FX folder are sample animations with extracted frames. You will have
to find your own tools with which to create animations and be able to extract
them to individual formats. I use Autodesk Animator Studio but there are
utilities on the web that you can also use.

See the ATABLE.TXT file in the FX folder for more.

===============================================================================
                   HOW TO CREATE A NEW SPACE/PLANET REGION
===============================================================================

I am not getting into any length hand holding exercise. Here are the steps I
used to create a space region containing a planet. The region is located in the
SOL system and accessible via a jump gate. I also used MapEdit to create an area
of interest on the planet. Use a plain text editor to edit the .SCR files!

You can use this method to create regions/planets all over the galaxy.

PRELIMINARY STEPS

1. The following files will be modified. So make backups by copying them
   to the BACKUP folder ie c:\bc3000ad\gbs\backup

                        STATICS.SCR
                        NAVDATA.SCR
                        EARTHZ.3D
                        MIDAEZ.3D
                        BC3LIB4.RES

   The ORIONZ.3D region is already contained in .\GBS\REGIONS though I show
   you how to create it later on in this walkthru.

   You can revert to them by simply copying them over your modified version.
   Generally, all .SCR files go in .\GBS, region files in .\GBS\REGIONS, object
   files in .\GBS\OBJECTS, *.RES files go to the BC3K runtime folder, ie
   C:\BC3000AD, etc.

STEP #1 - Creating the space region definition file

1. Edit the STATICS.SCR file and add the following line in the Earth region
   definition around line 117

   jmp-65,j,orionz:To..Orion

2. Then, go to Midae region definition around line 569 and add

   wrm-27,w,orionz:To..Sol..System

   Our new region, Orion, will be linked to (1) the Earth region (SOL), using
   jump point 65 (there are already 64 jump points in the game) and (2) to the
   Midae region (Omicron Eridani) using a wormhole 27 (there are already 26
   worm holes in the game).

   The trailing z in space region names is very important!

3. Go to the end of the SOL system definition around line 408 and define the
   space & planet regions as indicated below. This puts our space region in the
   SOL system. If you wanted it in another region, say Alpha Centauri, then you
   would locate it within that system's definition block, in which case, within
   the ."ALPHA CENTAURI","alpha" section.

   #
   # User Defined Regions
   #
   :Orion1.3d,p,"ORION-1","SOL","PLANET 1/1"
   :Orionz.3d,s,"TERRAN","SOL","SECTOR D9"
   Orion1,p,earth,ptype3,ptype3,temp,TERRAN,1440
   jmp-65,j,earthz:To..Earth
   wrm-27,w,midaez:To..Omicron-Eridani..System

   If you look closely, you will see that I simply cloned the Earth space/planet
   region and changed the parameters to suit my purpose. This means that this
   planet will have the same terrain, weather and time parameters as Earth. You
   can change it to anything you like (Mars, Mercury, Moon, Jupiter etc) by
   looking at other planet definitions. The 'sector info' is currently unused,
   so you don't even need to change it. Also, the .. in the target names are
   important because the space character is not allowed. Using 'To Earth' would
   produce a parsing error or worse.

   We now have a space region called Orion (orionz.3d) containing a planet
   called Orion1 (orion1.3d), located in the SOL system and linked to Earth by
   jump point 65 and Midae by wormhole 27.

STEP #2 - Creating the space region 3D file

   Note: All of this is being done in the PLAN view (TOP LEFT). If you don't
   want to display all 4 views, press ALT+F1 to zoom this view. To revert to
   viewing all 4 views, select VIEW->WINDOW->ALL FOUR VIEWS

1. Go to the .\GBS\REGIONS folder and copy PLUTOZ.3D to ORIONZ.3D. We
   are going to use this as a template because it contains a jump point and worm
   hole objects. You can use this method any time to want to create a new space
   region. It is easier than starting from scratch as you will see from the next
   step.

2. Open the TED editor.

   With the editor loaded, RIGHT-CLICK in the PLAN view. From the menu, select
   UNIT->TERRAIN MODE TOGGLE. This will set the unit scale to a larger value and
   prevent the region from being cramped.

3. Activate the menu again (or you can use F3) and load up the ORIONZ.3D file by
   typing in the FULL path to it, ie c:\bc3000ad\gbs\scenery\regions\orionz.3d

   NOTE: To prevent having to do this each time, you can RIGHT-CLICK on the
   display and go to FILE->CHANGE DIRECTORY, and type in the full path to where
   the region files reside, ie c:\bc3000ad\gbs\regions and press ENTER.
   This way, you can simply type the name of the file without having to type in
   the full path each time or having to search the entire folder (if you typed
   *.3D and pressed ENTER)

4. Once the file is loaded, you will see the region (an exact copy of
   PLUTOZ.3D) which you are now going to edit.

    - Press SHIFT+Z so that the entire region is fully zoomed.

    - Press SHIFT+e to go into 'erase object' mode. Move the cursor near JMP-03
      and press TAB. The name of the current object, JMP-03, will now appear in
      the TED status bar. Now, DOUBLE-CLICK to delete it. If you can see the
      object, you can simply move the cursor near it to delete it. NOTE: You
      only need the TAB command to snap-to the object if there are too many in
      close proximity and you can't select the desired one easily.

      Repeat the same procedure to delete *all* the objects *except* JMP-18,
      WRM-01 and PLUTO (the planet).

      When you are done, press ESCAPE to get out of this editing mode. You can
      also RIGHT-CLICK on the display to exit this mode. NOTE: If you are using
      the WIN9x version, RIGHT-CLICK (or press ESCAPE) several times in the
      display area (not in the textures screen that will eventually pop-up) to
      exit this mode (the cross-hair cursor will disappear) due to a bug in the
      menu system.

    - Press F4 to save the file.

    - Press i to go into 'identify object' mode.

      Note: You may want to use uppercase character names, for easy reading.

      Type in JMP-65 and press ENTER. Then DOUBLE-CLICK on JMP-18 to rename it.

      Press i again, BACKSPACE to delete the current identifier and type WRM-27,
      then DOUBLE-CLICK on WRM-01 to rename it.

      Press i again, BACKSPACE to delete the current identifier and type
      ORION1, then DOUBLE-CLICK on PLUTO to rename it.

    - Press F4 to save the file.

   You now have the ORIONZ.3D space region, containing the planet, jump point
   and wormhole.

   NOTE: You can ignore the color coding I used in my own file definitions. I do
   that so that I can easily tell what anomalies are in the file. This is why I
   use blue for jump points, brown for fluxfields etc.

5. We are now going to add the 'other end' of the JMP-65 and WRM-27 links in
   the EARTHz and MIDAEz regions. This way, the ORIONz space region, is linked.
   to EARTHz and MIDAEz as per the definition file we created in STEP #1.

    - Press F3 and load the EARTHZ.3D file.

      Be *very* careful in here. If you screw up, you are going to invalidate
      this region. You will then have to copy the backup version over and start
      from scratch. You have been warned.

    - Press c to enter the 'copy structure' mode. LEFT-CLICK *once* on JMP-11.
      Move the cursor to an empty spot. I suggest the half-way point between
      JMP-11 and JMP-01a. LEFT-CLICK *once* to make a copy of JMP-11.

    - Press i to enter the 'identifier name' mode. Use BACKSPACE to remove the
      previous one, if any, and type JMP-65. Press ENTER and then DOUBLE-CLICK
      on the copy of JMP-11 (the green one) to rename it to JMP-65.

      NOTE: If you want to change the color to the default, Cyan, then
      LEFT-CLICK in the Cyan color (index 11) in the palette bar at the bottom
      of the display; press SHIFT+x to enter 'copy attributes' mode; and then
      DOUBLE-CLICK on the copy of JMP-65 (the green one). It will now change to
      Cyan.

    - Press F4 to save the file.

    - Press F3 and load the MIDAEZ.3D file.

    - Repeat the steps above, but this time, make a copy of WRM-05, put it
      anywhere you like and rename the copy to WRM-27

    - Press F4 to save the file.

6. Use F10 or the menu, to exit the editor.

STEP #3 - Creating the planetary region file

   When I have time, I'll document how this is done as well as how to create
   surface areas of interest.

   For now, entering a user defined planet without its own unique terrain
   definition file, will cause the system to use whatever predefined planet/moon
   type you define.

   Remember this line from earlier? That third parameter is what makes your
   ORION1 planet, have the same topology, size, climate zone etc, as EARTH.
   If you change it to, say, mars, you will have a MARS type planet but with
   the EARTH time zone. Try it!

      Orion1,p,earth,ptype3,ptype3,temp,TERRAN,1440

STEP #4 - Making the world interesting

If you want NPCs to know about and visit your region, then you want to make the
AG system aware of it. You can either let the system automatically determine who
visits it or you can use some pre-defined macros to do it for you.

If you want auto-generation to occur in your region, edit the GLOB_AG.SCR file
and include a definition for it. In the case of this excercise, you can go
to line 516 (the end of the AG definition for PLUTO) and add these lines. Do
NOT add asteroid field definitions until you know how to do so!

  :orionz,10,5
  enemy_aggressive();
  random_harmless();
  terran_military();

This uses three macros (you can use as many as you like. Read the file to see
the list of pre-defined macros) to create aggressive enemy units, as well as
a random selection of harmless units and terran military.

STEP #5 - Executing the world

1.  Run the MAKEREG.BAT file. This will make the regions as well as the entire
    object database, creating the .3DC files required by the system.

    Note: This new file set also gives you access to the object class database.
    So, you can go screwing around in the OBJECTS.SCR and OBJCLASS.SCR file
    if you know what you are doing, and just run MAKEREG.BAT to rebuild
    everything.

    It will then use the BUILDLIB utility to create a new BC3LIB4.RES file.
    Copy this new file to the BC3000AD run-time folder (make sure you backup the
    original).

2.  Start a NEW the game and if you did this all correctly, you should be able
    to jump to Orion from Earth and then onto Midae. You can also enter the
    planet.

=============================================================================
                                   NOTES
=============================================================================

- The NAVDATA.SCR file is automatically created when 'prepare regions' is
  executed (see MAKEREG.BAT). It contains identifiers for all the regions and
  links. The reason this region was modified in this exercise, is because of the
  new Orion region and links.

- Saved games across changed BC3LIB4.RES files will NOT work!

- Navitron will not show your new regions because it is a static bitmap

- The HSD will still work

- If you put a starstation in a new space region, not only will you not be able
  to dock with it but Tradcom won't have the proper data either. The data for
  these are embedded in the BC3K kernel and I will extract them later providing
  access to their modifications.

- The info pop-up window for crafts will show the name of the predefined planet
  type. So, above, if you use Earth and you put an IC on Orion, the pop-up tab
  will show its location as Earth etc.

- As indicated above, Tactical may display the wrong deployment location for
  ATVs or mining drones.

- If you are sending a new region as part of a mission script, send the person
  the new BC3LIB4.RES with instructions to backup their default copies or send
  them the changed .SCR and .3D files so that they can rebuild it on their end.

- The creation of new regions does not affect missions. However, if you create
  missions which use those new regions, you must make sure you send the new
  mission data as well as the new .RES file to whoever you are sharing the files
  with.

- The BUILDLIB utility is a one-way process. It uses .IDX files as input and you
  cannot extract files from the resulting .RES file. Do NOT add/remove files
  to/from this resource file's .IDX source file! You have been warned.

- In STEP #2 you used TED to edit the .3D files. If you don't want to do this,
  and you have confidence, you can actually edit the ascii versions of these
  files directly, without ever loading up TED. Here's how.

    1 Copy the following files to a temporary folder
        CV3D.EXE, PLUTOZ.3D, EARTHZ.3D, MIDAEZ.3D

    2 Convert them to .3DT (ascii) by typing 'cv3d *.3d'. This will produce
      .3DT files and remove the original .3D files (unless you use the /k)
      parameter.

    3 Rename PLUTOZ.3DT to ORIONZ.3DT

    4 Load up ORIONZ.3DT in a text editor. The idea is to remove all unwanted
      structures and rename some existing ones, as indicated in STEP #2.

      The file format is fairly straightforward. You will see point ids (pid)
      and structures. They are matched. In this excercise, you would

      A  remove lines with pid/structure numbers 1,2,3,4,5,7,9
      B  rename lines with pid/structure numbers 0,6,8, to 0,1,2
      C  rename the following. Note the pid/struct renumbering!

         [0] col:2 at:0,use:PLANET.3D:PLUTO
         [0] col:15 at:6,use:WORMHOLE.3D:WRM-01
         [0] col:11 at:8,Rx:93, use:JUMP.3D:JMP-12

         to

         [0] col:2 at:0,use:PLANET.3D:ORION1
         [0] col:15 at:1,use:WORMHOLE.3D:WRM-27
         [0] col:11 at:2,Rx:93, use:JUMP.3D:JMP-65

      D Change the following

         points (10):
         structures (10):

         to

         points (3):
         structures (3):

      E Save the file, which should now look like this:

         Ted32 text format file id:191550422,1
         Unit:3 (Km)
          group:MAIN
          size:0,origin:(0,0,0),extents:(0,0,0)(0,0,0)
          (
            points (3):
            pid 0:(-272851,47860,-380645)
            pid 1:(-231704995,355558826,-803912)
            pid 2:(135752609,-112678290,-402371505)
            structures (3):
            [0] col:2 at:0,use:PLANET.3D:PLUTO
            [0] col:15 at:1,use:WORMHOLE.3D:WRM-01
            [0] col:11 at:2,Rx:93, use:JUMP.3D:JMP-12
            subgroups (6):
            include:PLANET.3D
            include:MOON.3D
            include:FLUX.3D
            include:WORMHOLE.3D
            include:JUMP.3D
            include:FLD.3D
          )

      F. Load the MIDAEZ.3DT file

         This is the tricky part because you are not editing an existing entity
         with a known location. You are attempting to locate one within a file,
         not knowing where it is going to be. In this case, I am going to make
         an estimate of the entity's location by modifying the Z co-ordinate.
         The only way to be certain, is to load up the resulting file in TED.

         Here is how the file now looks after adding WRM-27 (our link back to
         ORION). Not the renumbering of the pid/structures. In modifying the
         Z co-ordinate by adding an arbitrary value which I know puts it
         away from the WRM-05 (which I cloned), it is guaranteed that the
         objects
         do not collide within the same space. In case you were wondering, I
         added 1500000 units to the new pid 6 Z value.

         Save the file, which should now look like this:

         Ted32 text format file id:191550422,1
         Unit:3 (Km)
          group:MAIN
          size:0,origin:(0,0,0),extents:(0,0,0)(0,0,0)
          (
            points (7):
            pid 0:(-21905203,-2420297,-347602)
            pid 1:(-423000879,-413298795,-250347602)
            pid 2:(236361281,402588507,124652398)
            pid 3:(-377999901,361500658,-125347602)
            pid 4:(36881042,-324933611,-102795057)
            pid 5:(-413235820,-84722806,-3316351)
            pid 6:(-413235820,-84722806,-4816351)
            structures (7):
            [0] col:2 at:0,use:PLANET.3D:MIDAE
            [0] col:7 at:1,use:MOON.3D:MOON-01
            [0] col:7 at:2,use:MOON.3D:MOON-02
            [0] col:11 at:3,Rx:90, use:JUMP.3D:JMP-33
            [0] col:15 at:4,use:WORMHOLE.3D:WRM-05
            [0] col:4 at:5,use:FLD.3D:FLD-33
            [0] col:15 at:6,use:WORMHOLE.3D:WRM-27
            subgroups (5):
            include:PLANET.3D
            include:MOON.3D
            include:JUMP.3D
            include:WORMHOLE.3D
            include:FLD.3D
           )

      G. Load the EARTHZ.3DT file

         Repeat the similar operation to add the JMP-65 jump point to
         ORION.

         Save the file, which should now look like this:

         Ted32 text format file id:191550422,1
         Unit:3 (Km)
          group:MAIN
          size:0,origin:(0,0,0),extents:(0,0,0)(0,0,0)
          (
            points (12):
            pid 0:(72496,860087,393344)
            pid 1:(-279069551,-249144805,50537362)
            pid 2:(124195955,-287187263,537362)
            pid 3:(-242764523,12603385,85956996)
            pid 4:(243110061,-123920778,100537362)
            pid 5:(-219815577,285570047,475374)
            pid 6:(271811881,392176854,-74462638)
            pid 7:(328552245,108475034,150537362)
            pid 8:(377466352,-308273156,175537362)
            pid 9:(53552245,243475034,150537362)
            pid 10:(280000000,-30000000,125000000)
            pid 11:(204177245,165350034,150537362)
            structures (12):
            [0] col:2 at:0,use:PLANET.3D:EARTH
            [0] col:11 at:1,Rx:85, use:JUMP.3D:JMP-01
            [0] col:11 at:2,Rx:90, use:JUMP.3D:JMP-02
            [0] col:11 at:3,Rx:94, use:JUMP.3D:JMP-05
            [0] col:11 at:4,Rx:94, use:JUMP.3D:JMP-04
            [0] col:11 at:5,Rx:89, use:JUMP.3D:JMP-10
            [0] col:11 at:6,Rx:90, use:JUMP.3D:JMP-12
            [0] col:11 at:7,Rx:89, use:JUMP.3D:JMP-11
            [0] col:11 at:8,Rx:92, use:JUMP.3D:JMP-03
            [0] col:11 at:9,Rx:89, use:JUMP.3D:JMP-01A
            [0] col:4 at:10,use:FLD.3D:FLD-03
            [0] col:11 at:11,Rx:89, use:JUMP.3D:JMP-65
            subgroups (4):
            include:PLANET.3D
            include:MOON.3D
            include:JUMP.3D
            include:FLD.3D
          )

  You now have the modified versions of ORIONZ, EARTHZ and MIDAEZ.

  Now run 'cv3d /k *.3dt' to convert them back to .3D binary files,
  preserving the .3DT originals just in case. Then copy them to the
  \gbs\regions folder and you're all set.

  For peace of mind, I would suggest that you load these files in TED
  and take a look to make sure they are ok.

===============================================================================
                   HOW TO CREATE SURFACE MISSION ZONES
===============================================================================

Read the MAPEDIT.DOC file to start with.

The PTEPROTO.EXE file is what is executed (I think its the 3Dfx  build, not
sure), when you opt to fly over the mission zone from *within* Mapedit. If it
crashes, that means you don't have a 3Dfx card.

First, check the PTETOOLS.IDX file and edit it to so that it gets the .3d files
from your GBS\OBJECTS folder. The other files would already be in the BIN
folder. Then use ptetools.bat to build it. Leave the resulting ptetools.res
file in there. Edit ptetools.bat to reflect the path to buildlib.exe!

To create a new mission zone, you only need to modify the pte.cfg file as per
the walkthru in MAPEDIT.DOC. You then need to build a PTETOOLS.RES file and it
will contain the new pte.cfg file as per your modification. You then fire up
Mapedit as normal.

You can skip the need to always build this .res file each time you edit the
pte.cfg file if you add 'SET USE_MFS=0' in your autoexec.bat file and reboot.
You will then need to add 'SET USE_MFS=1' as the first line in your BC3K.BAT
and BC3K3DFX.BAT files. This command tells all the tools to not use files in
the .res files. This way, Mapedit, when it loads, will read the .cfg files in
its current BIN folder, and ignore the older ones in the ptetools.res file.
Unfortunately, BC3K does the same thing, which is why you need to re-enable
this in its own .bat files. DO NOT MODIFY ANY OTHER .CFG FILES!!!

Once you have built your mission zone, export it to a .SCR file and then use
Mapmake.exe to build the .PTE mission zone from this .SCR file. It will build
them in the .PTE sub-folder of your BC3K runtime folder, so make sure that the
BCTOOLS.INI file is updated! The .SCR file is a text file and you can also
manually edit it. For instance, the default EARTH.SCR file uses MAP0008 for
all areas. If you want to change this, simply edit the file and change it. For
instance, you could edit the MZARC0 mission zone to use MAP0001 by changing it
and then running 'mapmake earth.scr' and all new mission zones defined in that
file will be created in the .PTE folder. These files have the MZ prefix in order
to tell them apart from the default base .PTE files. You can also manually
remove/add compound entities from the .SCR source files.

Do NOT confuse the surface .SCR files with the script .SCR files!!!

In order to get BC3K to read your new PTE.CFG and thus create the new mission
zones, you should build a new BC3LIB3.RES using the BC3LIB3.BAT file. Check
this file and adjust the file paths accordingly. Then copy the resulting
BC3LIB3.RES file to your BC3K runtime folder. Be sure to backup the original!
You can then fly to the planet and view the mission zones from Tacops. If
Mapedit can see them, so can BC3K.

WARNING: Though Mapedit covers other topics related to editing the surface
topology maps, don't even think of trying it!

If you are going to be modifying the default files, be sure to copy the
originals into the BACKUP folder so that you can revert to them.
