Project Stardust missiles are delayed team pressure, not a guaranteed damage button. A successful volley needs a suitable target, a usable path, manageable travel time, and a reason the defender cannot devote all point-defense coverage to it. The best launch often begins before the button press, when you choose the angle and wait for friendly pressure.
Exact lock rules, range, speed, reload, ammunition, salvo size, and damage vary by ship and current build. Read the live launcher indicators and observe what happens after every launch.
Community corroborated — checked September 12, 2026: Point defense is widely documented as an automatic answer to missiles in its coverage area. Saturation, mount arcs, damaged systems, overlapping allies, and current balance can change how many threats pass.
Read the launcher first
At spawn start or during a safe moment, identify the missile group, current target requirement, range feedback, reload or ammunition display, and launch arc. Do not assume a launcher behaves like one on another faction’s ship.
Observe whether target movement, line of sight, or your own facing interrupts the current solution. If the interface does not show a valid state, preserve the salvo instead of guessing. A delayed launch is better than a full cycle sent without a path.
Note what the ship must expose to fire. The missile’s delayed damage does not justify leaving the hull under immediate direct pressure.
Choose targets by defensive context
Large isolated ships are often easier to threaten than small agile targets near escorts. A damaged target with reduced defensive coverage can be more efficient than the nearest full-health capital ship. A carrier separated from its screen may deserve attention, but chasing it beyond team support can turn your launcher into bait.
Watch which enemies are already occupied. A target turning to face direct fire, entering an objective lane, or responding to fighter pressure has fewer clean options when missiles arrive.
Avoid sending every volley at the same well-defended target without learning from the interceptions. Change timing, angle, target, or coordinate with teammates.
Time arrival with team pressure
Missiles become stronger when their arrival overlaps another decision. Direct weapons can force a defensive facing. Friendly fighters can occupy coverage. An objective can make the target reluctant to leave. A teammate’s prior volley can reveal how the point defense responds.
Estimate travel rather than firing only because the launcher is ready. If the fight will move behind cover before arrival, select another target or wait. If a push is about to begin, launch so the defender faces the missiles during the push rather than long before it.
Communicate the target when possible. Several coordinated threats are harder to answer than identical pressure spread across multiple ships.
Use approach angles
An approach angle determines which defensive mounts and nearby escorts can respond. Do not assume the shortest straight line is safest. Map structures, target facing, and team positions can create a less protected side, but current path behavior must be observed rather than imagined.
Move enough to change the delivery problem without isolating your own ship. A wide flank that removes all friendly protection may cost more than improved missile access.
After launch, watch the path and interceptions. That observation is the evidence for the next choice. Repeating the same angle without watching wastes both ammunition and learning.
Work with point defense
Point defense creates coverage, not certainty. Defending ships can overlap zones, while damaged mounts or separation may create gaps. Some mounts are described by players as dual-purpose, so anti-ship activity may compete with defensive readiness under current rules.
Do not interpret one successful volley as proof that a ship has no defense. It may have faced another direction, lost mounts, been saturated, or received no escort. Likewise, one intercepted volley does not make the launcher useless.
Read the point-defense guide to understand the defender’s decisions and choose targets with that perspective.
Preserve the launching ship
Missile travel can tempt pilots to watch the volley and ignore the hull. Resume scanning immediately. Check direct threats, range, cover, weapon cycle, and retreat lane. Your ship should still contribute after the missiles resolve.
Do not close into an enemy’s best direct range merely to shorten missile travel unless the team and route justify it. If missiles are the primary system, maintain the envelope that lets repeated useful launches happen.
When the launcher reloads, reposition or support the team instead of idling. The next angle may matter more than the next second of cooldown.
Defend against missiles
Stay near escorts or allies with useful coverage, but leave enough room to maneuver. Present a protected angle when you understand current mount arcs. Move toward friendly coverage rather than away from the team during a long pursuit.
Watch launch warnings and incoming direction. If the map provides cover that safely interrupts or complicates the approach, use it without colliding or exposing a worse side. Preserve dual-purpose defensive attention when a large volley is incoming.
Carrier pilots should use interception roles when current craft can help. Confirm commands and avoid sending every fighter too far away to respond.
Mode-specific missile use
In Deathmatch, missiles should help finish a target without drawing the launcher into a chase. In Fleet Battle, coordinate against valuable exposed ships while protecting your own high-value hull. In Attack and Defend, use arrival timing to disrupt objective pressure or open a route.
In Domination, pressure ships that must remain near a capture area or punish an isolated defender. Do not stay so far from the point that the launcher has no immediate influence.
Map geometry changes all four. Use maps to identify open gaps, cover transitions, and likely defensive formations.
Common missile mistakes
Launching on cooldown, selecting the nearest target, ignoring escorts, using one angle repeatedly, and watching the volley instead of the ship are the most common errors. Another is assuming a damage number predicts real output without accounting for interception.
Avoid old exact ranges and reloads unless the current interface confirms them. Avoid blaming a suspected bug before checking target state, arc, server, and point-defense coverage.
Practice and review
For one match, record target type, launch distance shown by the current UI, defensive context, arrival result, and what happened to your hull. Change one condition next match. This makes missile timing measurable.
Combine that review with combat and weapon types. The goal is to create dilemmas for the defender while keeping the launcher alive for the next cycle.