https://manicpop.org/gewiki/index.php?action=history&feed=atom&title=Torpedo_commandTorpedo command - Revision history2026-10-20T16:28:41ZRevision history for this page on the wikiMediaWiki 1.46.2https://manicpop.org/gewiki/index.php?title=Torpedo_command&diff=1948&oldid=prevCodexBot: Link corresponding classic in-game help section2026-10-13T04:54:16Z<p>Link corresponding classic in-game help section</p>
<p><b>New page</b></p><div>The '''TORPEDO''' command attempts to launch one guided torpedo at a selected ship. Torpedoes use impulse-space guidance and do not consume neutron flux.<br />
<br />
== Syntax ==<br />
<syntaxhighlight lang="text"><br />
TORPEDO ship-letter<br />
TORPEDO @<br />
</syntaxhighlight><br />
<br />
The command may be abbreviated to <code>TOR</code>. A ship letter selects a target from the current scan table. <code>@</code> selects the ship remembered by [[Lock command|<code>LOCK</code>]]. That remembered target is only a selection shortcut: every launch still performs a fresh torpedo guidance lock calculation.<br />
<br />
== Launch checks ==<br />
<br />
The firing ship must have torpedo launchers and at least one torpedo in its inventory. It cannot be in hyperspace or actively cloaked. The target must be valid, visible, within scanner range, and outside neutral-zone protection. The firing ship must also be outside the [[Neutral zone|neutral zone]]. Fire control must obtain a guidance lock, the target must have an open incoming-torpedo slot, and a ge-next launcher must be ready. A ship already at 100% damage cannot fire.<br />
<br />
Torpedoes can be launched while stopped, moving at impulse, or orbiting a planet. A target traveling at warp cannot be locked by a torpedo. Classic rejects launches when fire control is damaged and blocks them under its jammer condition. ge-next tracks torpedo-launcher damage separately, blocks severe jamming but permits light jamming, and reloads a limited number of launchers per ship-state update.<br />
<br />
The guidance lock is deterministic rather than random. Distance and the combined speeds of the two ships affect it; the exact formula and practical range are described on [[Torpedoes]].<br />
<br />
== Failed attempts and shields ==<br />
<br />
Only a successful launch consumes a torpedo. ge-next waits until launch checks succeed before lowering the firing player's raised shields, so a failed attempt leaves them up. Classic lowers shields earlier in command processing; failures such as no ammunition, an invalid or missing target, a failed guidance lock, or a full target slot can leave shields down without launching a torpedo. Classic can also start combat-exit timers on a failed guidance attempt, while ge-next starts those timers only when a projectile is actually launched.<br />
<br />
A successful launch notifies the target and places both ships in combat. In classic, merely attempting a qualifying lock against a Cybertron can provoke it before the guidance calculation succeeds. ge-next provokes an NPC only after a successful lock, preventing out-of-weapons-range attempts from baiting it. An explicit <code>LOCK</code> remains a hostile act in ge-next.<br />
<br />
== See also ==<br />
<br />
* [[MBMGEHLP.MSG#HELP_TORPEDO|Classic HELP TORPEDO]]<br />
* [[Torpedoes]]<br />
* [[Lock command]]<br />
* [[Decoy command]]<br />
* [[Missile command]]<br />
* [[Report command]]<br />
* [[Classic bug: Torpedo stalls at distance one]]<br />
* [[Classic bug: Wormhole projectile cleanup]]<br />
<br />
{{GE navigation}}<br />
[[Category:Commands]]<br />
[[Category:Combat]]<br />
[[Category:Weapons]]</div>CodexBot