Project Stardust ship stats are valuable only when they change a decision. Health does not explain whether you can retreat. Damage does not show whether weapons stay in arc. Range does not guarantee a sightline. Read the panel as a connected system and use the live interface for every exact value.
Current-build rule: Compare ships in the same server and date. Balance, loadouts, interface labels, and derived behavior can change, while community pages and videos may preserve older numbers.
Health, shields, and effective survival
Hull or health is the final damage reserve for many ships. Shields, when present, add a defensive layer or recovery rhythm. Neither number alone represents effective survival. Profile size, acceleration, turn response, coverage, retreat space, and incoming weapon type determine how long the ship remains useful.
A large hull can absorb pressure but may draw focus and struggle to leave. A shielded ship can recover value only after breaking sustained contact. When comparing defenses, ask how the ship creates that break: range, speed, cover, allies, interception, or a decisive counterattack.
Set a retreat trigger based on the defense. A shield-focused ship should leave before recovery becomes impossible. A hull-focused ship should not confuse a large pool with permission to remain under the whole enemy team.
Speed, acceleration, and turning
Top speed describes only part of mobility. Acceleration determines how quickly a ship crosses danger or begins a retreat. Turning affects weapon alignment, profile exposure, obstacle clearance, and the time needed to reverse a bad angle.
Test movement in a safe opening. Observe the time from command to meaningful motion, the space required for a broad turn, and how much aim shifts while maneuvering. Large ships should select lanes with enough clearance before contact.
A slower ship can still control a lane if it arrives early and has support. A fast ship can still fail by reaching an objective alone. Mobility is the ability to be useful at the needed time, not just the maximum displayed speed.
Range and engagement envelope
Range tells you when a weapon can reach, but practical range includes target movement, sightline, travel, lock behavior, accuracy, and the enemy’s return fire. Use the current targeting feedback instead of a number remembered from a guide.
Identify the distance where your main group contributes reliably and the distance where the enemy’s strongest answer becomes dangerous. Your preferred envelope lies between those boundaries. Cover and teammates can widen it; isolation narrows it.
Mixed-range ships require restraint. Closing to use a short secondary group may expose the hull and reduce the value of longer weapons. Decide whether the added output is worth surrendering distance.
Damage, reload, and uptime
Displayed damage may describe a shot, burst, salvo, or another current unit. Reload or recharge determines how often the result can repeat. Uptime adds the portion of a match spent in range, in arc, with a valid target, and alive.
A lower peak weapon with stable arcs can contribute more than a powerful system that rarely aligns. Review one whole cycle: target acquisition, firing, impact, reload, and the position during recovery. If the ship must expose itself throughout the cycle, the defensive cost belongs in the comparison.
Avoid combining old damage and new reload values from different dates. Use one current panel or a controlled current observation.
Weapon arcs and mount placement
Arcs define which facing activates a weapon group. Forward weapons favor pursuit or controlled approach. Broadsides may require side exposure. Spinal weapons make the entire hull aim. Turrets can have wide coverage but may still be blocked by geometry or track poorly under some movement.
At spawn, rotate gently and watch the current aiming indicators. Learn where groups enter and leave the target solution. Then plan an engagement angle that keeps the important group active while preserving an exit.
Mount placement also shapes defense. Damaged or poorly positioned point-defense mounts may leave a side vulnerable. Do not assume a total coverage stat means every angle is equal.
Missiles, point defense, and special systems
Missile stats must be read with travel, targeting, volley pattern, reload, and defensive interception. A high theoretical salvo can disappear into ready point defense. Launch timing and approach angle determine whether the number becomes pressure.
Point defense is area protection against community-documented threats such as missiles and squadrons. Its usefulness depends on range, arcs, surviving mounts, allied overlap, and whether a dual-purpose system is occupied elsewhere. Treat it as coverage, not immunity.
Carrier stats include more than craft count. Consider craft role, travel time, ammunition, command response, docking or recovery, and the safety of the carrier hull. Confirm every command in the current interface.
Compare two ships fairly
Choose the same mode goal and map situation. Write down defense rhythm, usable mobility, main engagement envelope, weapon alignment demand, defensive coverage, and team utility. Do not declare a winner from unrelated peak numbers.
Then compare the cost of failure. Which ship can recover from a missed cycle? Which can leave after committing? Which loses more match value when destroyed? A forgiving ship may be the better progression choice even if an expert can extract more from the specialist.
Use ordinary matches to test one difference at a time. Similar targets, lanes, and team support produce more useful observations.
Common stat-reading mistakes
The first mistake is adding every weapon’s peak output as if all groups fire simultaneously at the same target. The second is ignoring arc and travel. The third is treating shields and hull as identical defense. The fourth is assuming top speed means good rotation. The fifth is comparing screenshots from different versions.
Also avoid treating class names as stat guarantees. Community roles are shorthand. Read the actual current hull with the ship classes guide beside it.
Turn the panel into a battle plan
Before spawning, state one sentence: “I contribute from this distance and leave through this route when this condition occurs.” Identify the weapon group that supports the sentence and the defense that buys time.
After the match, check whether low output came from the stat or your access to it. Time outside range, blocked arcs, premature missile launches, lost craft, and late retreats are execution issues you can correct. If the displayed current behavior truly differs, record the panel and date and consult the updates tracker.