empserver/info/range.t
Markus Armbruster 4ea4a01fd5 (info, html): Implement.
(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.
2005-12-22 10:09:17 +00:00

21 lines
724 B
Perl

.TH Command RANGE
.NA range "Edit the range of a plane"
.LV Expert
.SY "range <PLANES> <range-limit>"
The \*Qrange\*U command is used to limit the maximum range of
individual planes. This can be useful in setting up high tech
interceptors (planes, ABMs, SAMs, etc.) to cover only a small
limited area.
.s1
Note that missiles always fly at double range (since they don't need
to fly back), so you should cut the desired range in half before using
the range command.
.s1
For example, if plane 1 were a plane and you wanted to limit its
reaction radius to 6, then you would type:
.EX "range 1 6"
and if plane 2 were a missile and you wanted to limit its reaction
radius to 6, then you would type:
.EX "range 2 3"
.SA "Planes"