Editting Terminal Screens


Terminal Editor

Terminal files in Forge had to be written using TextEdit or Hex and the resulting files merged.

With Pfhorge much of that work can be done within the map using the Terminal Editor. A number of terminal files can be created within a map, each with a terminal sequence(s) describing the screens to be viewed by the player.

Clicking on the top right section opens a drawer that enables the sequences to be compiled. Add Terminal creates the terminals necessary for each map, the numbers allowing tagging to the terminals you create on the map. Add Terminal Section creates both the individual screens and the "choices" Aleph One makes in which sequence a terminal will show you depending on the progress of the game, e.g., success or failure.


The drop-down menu of Section Type defines the exact sequence that will exist associated with a specific terminal.


Below is a short example sequence from Marathon 2 (Waterloo Waterpark) where Terminal 0 has Unfinished and Success sequences, separated by a Delimiter, each sequence consisting of Log-on, Information, Log-off. Aleph One programming has enabled cameras to be utilised through Pfhortran/Lua.


The text-based sequences can be created and modified in Pfhorge (no spell-checker) while pictures, movies and sounds must be prepared elsewhere. All are stored in a sub-folder to the map, their file names being the Index # required for assembly. This is similar to the way PICT resources in Marathon files being stored and used accordong to their resource ID #.

Importing a Marathon file into a scenario file will automatically extract such resources and store them in a subfolder.



Contents | Introduction | Preferences & Menus | New Map or Scenario | Lines | Polygons | Texturing |
| Lights | Liquids | Sounds | Control Panels | Objects | Visual Mode | Configuration Editor | Inspectors