info/lretreat: Resync with retreat.t

Commit 18ee9a2f (v4.2.21) and commit 18ee9a2f (v4.3.16) updated only
info/retreat.t, and missed info/lretreat.t.

Signed-off-by: Markus Armbruster <armbru@pond.sub.org>
This commit is contained in:
Markus Armbruster 2014-12-31 09:55:08 +01:00
parent b4bdd658bd
commit 75a049515b

View file

@ -52,30 +52,31 @@ is Yes, then every ship in that fleet with fleet retreat orders retreats
along the specified path. If it is no, then the retreat orders apply to
that ship only, and only that ship retreats.
.s1
When a ship is added to a fleet, it is given the retreat orders of that
fleet, if any exist.
When a ship is added to a fleet, it is given the retreat orders of the
first ship in that fleet that has fleet retreat orders and is in the
same sector, if any exist.
.s1
Retreat orders are wiped when a ship navigates.
.s1
Retreat conditions at present include:
Retreat conditions are:
.nf
Condition Meaning
I Retreat when the ship is injured,
i.e. whenever the ship is damaged
by fire, bombs, or torping.
T Retreat when a sub torpedos or tries
to torpedo the ship.
B Retreat when a plane bombs or tries
to bomb the ship.
S Retreat when the ship detects a sonar
ping.
D Retreat when the ship is depth-charged.
H Retreat when helpless. A ship is helpless
i.e. whenever the ship is damaged by fire,
bombs, or torping
T Retreat when a sub torpedos or tries to
torpedo the ship
B Retreat when a plane bombs or tries to bomb
the ship
S Retreat when the ship detects a sonar ping
D Retreat when the ship is depth-charged
H Retreat when helpless --- a ship is helpless
when it is fired upon, and no friendly
ships/sectors (including the ship itself)
are able to fire back at the aggressor.
C Clear the flags
ships/sectors (including the ship itself) are
able to fire back at the aggressor
U Retreat upon a failed boarding attempt
C Cancel retreat order
.fi
.s1
For example, if the battleship above was fired at, it would attempt to