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.
23 lines
938 B
Perl
23 lines
938 B
Perl
.TH Command FOLLOW
|
|
.NA follow "Cause one ship to automatically follow another"
|
|
.LV Expert
|
|
.SY "follow <SHIP/FLEET>"
|
|
You use the \*Qfollow\*U command to get a ship to use the same
|
|
sailing path as another ship.
|
|
At each update, ships with a sailing path \*Qautonavigate\*U along
|
|
the path that was set for them, and ships that are set
|
|
to follow that ship will also be navigated along the same
|
|
path. Telegrams notify you of arrivals
|
|
or problems encountered while attempting to follow the path.
|
|
.s1
|
|
Radar operates continuously as the ship moves along the path, constantly
|
|
adding sector information to the known world map.
|
|
.s1
|
|
Ship movement is performed before mobility is increased.
|
|
This insures that after the update, ships with a sailing path will still
|
|
have some mobility so that you can always manually navigate
|
|
to some extent.
|
|
.s1
|
|
You may follow any ship which is owned by you or a friendly country.
|
|
.s1
|
|
.SA "sail, unsail, mquota, Ships"
|