---

Technical Information

Ok... heres the fun part. Explorer will be based around a small bootstrap loader which will start up the library code. All the functionality of Explorer, it's gfx routines and so on will be implemented via libraries. This means that it will be easy to produce different versions of the code. As things stand at the moment I am considering writing versions of the libraries for AGA and RTG. (as a combined AGA/RTG lib is too slow on AGA and cumbersome on RTG) However, because of the structure of the libraries it should be possible for 3rd parties to develop ECS routines.

• The engines.
  The 3D engine will be a lightsourced, shaded, texturemapped engine which will include variable lighting, transparency and fog effects (you won't believe how easy fog is once you get your head around it). The user will be able to select the detail levels, rendering method (plain polygon up to full rendering) and rejection systems (I will be using a painter algorithm which automatically adjusts itself, thanks to some tricky queue code, to keep the speed up at the expense of detail, this can be turned off if you don't mind slowdown in complex views.) I will, probably, be using Kalms CPU3BLIT1 c2p routine in the AGA version for best performance.

  The other graphics engines will render onto a normal intuition screen (minus titlebar and gadget of course) for maximum OS compatability.

  Input devices are interpreted by control modules which watch the ports and produce signals which the user can configure in the game controls editors. Each ships will have it's own actions and movement definitions which can be triggered by user defined keys.

  All the systems controls can be defined and each ship's controls can be separately configured (optional). Many ships have preset manoeuvres which will be triggered via a single keypress (like a flip roll).

• The modules.
  Each one of the control modules will monitor a certain port. The modules are specifically written to take certain port states and produce defined results. These results are fed into the control interpreter which maps module outputs to control states using user defined settings.
• The Fleet System.
  This is going to be a nasty one but it should improve the game incredibly. In most other space simulators ships move at random through the universe, rarely having any form of interaction. I will deal with this problem through (drum roll please.. thankyou) The Fleet System. On the most basic level this system will make several ships operate as if they were under coordinated, cooperative control. This will allow me to form escorts and groups of fighters which appear to be under coordinated control from a battleship or command station. How does this work....
  • Fleet Hierarchy
    Fleets are defined in a hierarchy so that lower rank ships get orders from high rank ones.

  • Intelligence systems
    The intelligence systems of the computer craft will be altered by 'orders' sent from a higher rank ships. This is really just the high level intelligence routines affecting the lower level ones.

  • Orders
    The player will receive orders from higher level ships via the communication system. These orders must be followed (as they will set certain rules in the engine which will reduce the player's rating if the orders are not followed.

  • Escort Duty
    In an escort the player must remain within x miles of the escorted ship.

  • Command Orders
    If the player is commanding the fleet, or at least part of it, then a separate screen will be available to give orders to ships under the player's rank.

  A variant of this allows the player to employ others, or to be employed by a company, to follow trade routes or map systems.