Commit 2e40a4b
(v4.3.3) changed ndump, but not its info page.
Signed-off-by: Markus Armbruster <armbru@pond.sub.org>
40 lines
1.2 KiB
Perl
40 lines
1.2 KiB
Perl
.TH Command NDUMP
|
|
.NA ndump "Dump raw nuke information"
|
|
.LV Expert
|
|
.SY "ndump <NUKES>"
|
|
The ndump command displays all information on
|
|
some or all of your nuclear devices.
|
|
Each nuke'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 ndump command
|
|
<NUKES> are the ships on which you wish information
|
|
(see \*Qinfo Syntax\*U).
|
|
.s1
|
|
An ndump command lists all selected nuclear devices headed by:
|
|
.NF
|
|
Sun Feb 9 22:16:37 1997
|
|
DUMP NUKES 855544597
|
|
id x y num type
|
|
.FI
|
|
The first line is the date. The second line is the
|
|
"DUMP NUKES <timestamp>" where the <timestamp> field is the current
|
|
timestamp. The third line is the columns which are output.
|
|
.NF
|
|
x x location
|
|
y y location
|
|
num always 1 for backward compatibility
|
|
type type of nuke
|
|
.FI
|
|
A typical usage might be:
|
|
.EX ndump #5
|
|
which would list data for all nukes in realm #5.
|
|
.s1
|
|
A ndump lists each of your nukes in the specified area.
|
|
The header line is a list of fields that correspond
|
|
to the order that ndump prints the nuke info.
|
|
.s1
|
|
.SA "nuke, xdump, Clients, Planes, Nukes"
|