Anti-Missile Missile (AMM) Defense in Aurora 4X C#

Anti-missile missiles (AMMs) are a core component of point-defense in Aurora 4X (C#). They are designed to intercept hostile anti-ship missiles (ASMs) at long range, reducing the number of incoming weapons that must be handled by close-in beam defenses. Effective AMM systems require coordinated design across sensors, fire controls, launchers, magazines, and missile engineering.

Overview

In C# Aurora, missile interception is governed by the Missile Mechanics system, where hit chance is primarily determined by the **speed ratio** between the AMM and the incoming ASM. Faster AMMs achieve significantly higher hit chances, while slower AMMs may be unable to intercept advanced threats. Because missile movement and weapon cycles occur in 5‑second increments, AMM systems must be designed to fire multiple salvos before impact.

Components of an AMM Defense System

1. Missile Warning Sensor

A dedicated Active Sensor with **Resolution 1** is required to detect incoming missiles at maximum possible range.

Resolution‑1 sensors detect missile‑sized contacts.
Any ship in the fleet with an active sensor will share contacts with all other ships.
Detection range determines how many 5‑second increments are available for AMM launches.

2. Missile Fire Control

Each ship that fires AMMs requires at least one **Resolution‑1 Missile Fire Control**. Key C# requirements:

**Tracking Speed ≥ Target Speed** or the fire control cannot engage.
Fire control range must meet or exceed the warning sensor range.
Each fire control can engage **one hostile salvo per firing cycle**.

3. Launchers

AMMs are almost always **Size‑1 missiles**, requiring **Size‑1 launchers**.

Reload rate is based on launcher size; Size‑1 launchers reload fastest.
Reloads occur in 5‑second increments.
Multiple launchers allow multiple AMMs to be fired per increment.

4. Magazines

Missile storage is measured in **Missile Size Points (MSP)**.

Each Size‑1 launcher contributes 1 MSP of storage.
Additional Magazine components increase total capacity.
AMM doctrine typically requires large magazines to sustain multi‑salvo defense.

5. The AMM Missile

AMMs must be engineered for **maximum speed**, not range or warhead strength. Typical C# AMM design:

**Warhead 1** (enough to kill most ASMs).
**Minimal fuel** (range only needs to match sensor/FC range).
**Agility** adjusted to keep total size at exactly **1 MSP**.
**Engine** with maximum power modifier to maximize speed.

See: Missile Design.

Designing an Effective AMM

In C#, AMM effectiveness is determined by:

**AMM Speed / ASM Speed ratio**
Fire control tracking speed
Number of launchers
Number of salvos available before impact

A typical early‑game AMM may struggle to exceed the speed of advanced ASMs, resulting in low hit chances. As engine technology improves, AMMs can reach 30,000–40,000 km/s, enabling reliable interception.

Engagement Timing

Missile movement and weapon cycles occur every **5 seconds**. Example:

An ASM traveling 20,000 km/s moves 100,000 km per increment.
If detected at 600,000 km, only six increments (30 seconds) are available.
With a 10‑second reload rate, only two AMM salvos can be fired before impact.

This timing determines the number of launchers and fire controls required.

Fire Control Allocation

Because each fire control can engage only one hostile salvo per firing cycle, multiple fire controls are required when facing multiple simultaneous salvos. See: Ship Combat → Fire Control Assignment.

Layered Point Defense

Modern C# doctrine uses **layered defense**:

**Long‑range AMMs** thin incoming salvos.
**Gauss Cannons**, CIWS, and other Beam Weapons handle leakers at close range.
ECM/ECCM and sensor quality further influence interception success.

Notes and Tips

Resolution‑1 sensors are mandatory for early detection.
Fire control tracking speed must match or exceed the ASM’s speed.
Size‑2 AMMs can be used for long‑range “umbrella” defense but reload more slowly.
AMM stockpiles should match fleet size; tech upgrades quickly obsolete old missiles.
Running away reduces closure rate and may allow additional AMM salvos.

Related Pages