Markus Armbruster
4ea4a01fd5
(all): Depend on info. Flatten info directory. This undoes the move to one subdirectory per chapter, which was done during Empire 2. The structure doesn't buy us much, as the info name space is flat, and it complicates makefiles. Overhaul info.pl: - It now wants to run in the root of the build tree. - Information on source files and subjects is now stored in makefiles, thus info.pl no longer picks up random junk from the file system. - Clean up Perl anachronisms, in particular use subroutine arguments and results rather than global variables where convenient. - Change format of diagnostics to the common format used by GNU tools, so that Emacs and the like can parse it. - Catch missing .SA. - When creating a new subject file, cowardly refuse to overwrite an existing file. - Subject files contain topics sorted by chapter, then by name. The order of chapters used to depend on how Perl sorts hash keys. Fix it.
67 lines
2 KiB
Perl
67 lines
2 KiB
Perl
.TH Command PDUMP
|
|
.NA pdump "Dump raw plane information"
|
|
.LV Expert
|
|
.SY "pdump <PLANES> [<fields>]"
|
|
The pdump command displays all information on
|
|
some or all of your planes.
|
|
pdump is a combination of plane and pstat.
|
|
Each plane's information is printed on one very long line.
|
|
Fields are separated by a single space.
|
|
.s1
|
|
This command is designed to be used for input to an empire tool
|
|
such as \*Qve\*U.
|
|
.s1
|
|
In the syntax of the pdump command
|
|
<PLANES> are the planes on which you wish information,
|
|
[<fields>] are the fields you wish to dump.
|
|
If no fields are specified, all fields are printed.
|
|
(see \*Qinfo Syntax\*U).
|
|
.s1
|
|
A pdump command lists all selected planes headed by:
|
|
.NF
|
|
Sun Feb 9 22:16:37 1997
|
|
DUMP PLANES 855544597
|
|
<fields>
|
|
.FI
|
|
The first line is the date. The second line is the
|
|
"DUMP PLANES <timestamp>" where the <timestamp> field is the current
|
|
timestamp. The third line is the columns which are output.
|
|
.s1
|
|
These columns represent the following fields which are also the
|
|
selection criteria for the command.
|
|
.s1
|
|
The following may be used as fields. They must be entered EXACTLY as
|
|
shown here (no partial pattern matching is done.)
|
|
.NF
|
|
type type of plane
|
|
x x location
|
|
y y location
|
|
wing wing
|
|
eff efficiency
|
|
mob mobility
|
|
tech technology level
|
|
att attack value
|
|
def defense value
|
|
acc accuracy
|
|
react current reaction range
|
|
range maximum range
|
|
load load rating
|
|
fuel amount of fuel used in one flight
|
|
hard hardness
|
|
ship ship number the plane is on
|
|
land land unit number the plane is on
|
|
laun launchable?
|
|
orb orbiting synchronously?
|
|
nuke nuke name (if armed)
|
|
grd groundburst? (if armed)
|
|
.FI
|
|
.s1
|
|
A typical usage might be:
|
|
.EX pdump #5
|
|
which would list data for all planes in realm #5.
|
|
.s1
|
|
A pdump lists each of your planes in the specified area.
|
|
The header line is a list of fields that correspond
|
|
to the order that pdump prints the plane info.
|
|
.s1
|
|
.SA "plane, pstat, Clients, Planes"
|