The Project Stardust tech tree is a map of future playstyles as well as unlocks. Each connection can commit Credits, ship or branch experience, Free XP, Gold, time, and practice. The safest route is one whose middle ships teach skills you want, not simply the shortest visible line to a famous final hull.
Use the live tree for every current node, prerequisite, tier, resource icon, and availability rule. Community diagrams are orientation aids and can become stale after an update.
Community corroborated — checked September 12, 2026: Progression is organized across franchise and faction branches with normal, premium, event, and other special access appearing in community records. The in-game interface is the final authority for what can be unlocked now.
Start from the role you enjoy
Choose a repeated combat job: line pressure, close brawling, long-range alignment, missile delivery, carrier management, defensive screening, or support. Then inspect which visible branch expresses that job across several nodes.
Do not begin with a ship name alone. A destination can require a path full of systems you dislike. If you enjoy direct weapons but not fighter commands, a carrier-heavy path may become a chore. If you enjoy mobility, a sequence of slow capital hulls may not be worth the endpoint.
Use ship classes to define the role and factions to compare broad tree identities.
Trace prerequisites three nodes ahead
Open the current branch and follow every connection around your ship. Note the next requirement, the node after it, and any split. This reveals whether progress continues through the same experience pool or asks for a different ship, resource, or access type.
At a split, compare both middle nodes. Record preferred range, defense, mobility, weapon alignment, and mode usefulness. A branch decision is easier when the comparison describes actions instead of peak stats.
If a connection is unclear, do not spend flexible currency to test it. Play another normal match and inspect the tree again.
Read resource icons carefully
Community sources describe Credits as a main purchase resource, ship or branch experience as path-specific progress, Free XP as more flexible, and Gold as connected to premium or conversion uses. Current labels and rules may differ.
Before any purchase, read the displayed balance, icon, prerequisite, and resulting item. Confirm whether the action unlocks a ship, researches a node, converts experience, or buys access. Similar buttons can represent different transactions.
The currency guide provides a transaction checklist and explains why a reserve matters.
Evaluate the whole branch
For three consecutive ships, make a compact comparison. Include defense rhythm, acceleration and turning, main engagement envelope, firing arcs, special systems, and retreat demand. Then identify the skill that carries forward.
A spinal line teaches lane selection and hull alignment. A shield line teaches exposure and recovery. A carrier line teaches commands, travel, and protection. A brawling line teaches approach timing. The best branch for growth repeats a useful skill while increasing the consequence of mistakes gradually.
Do not treat tier as a universal power rank. Mode, map, current balance, and execution determine match value.
Test before committing deeper
Use starter access or the nearest affordable ship to sample the branch. Play several ordinary matches and keep the same question: Can you reach the intended range, apply the main cycle, help the objective, and leave?
One bad map is not enough to reject a tree. One exceptional match is not enough to commit all resources. Look for a repeated rhythm that feels understandable and improvable.
Save strong boosters until the route, arcs, and retreat are familiar. The boosters guide helps prepare a focused session.
Plan for branch splits
A split is a decision gate. Compare what the next two paths ask you to do, what currencies they consume, and whether their later ships continue that identity. Keep enough reserve that choosing one does not accidentally prevent a necessary unlock.
If both branches appeal, advance each only to a low-cost test point rather than racing one to the end. Actual match experience resolves uncertainty better than an undated ranking.
Record the check date because a moved prerequisite or rebalanced ship can change the preferred path.
Handle premium and event nodes
A premium ship is not automatically a tech-tree shortcut, and an event entry is not automatically obtainable. Open the current purchase or access prompt and verify cost, permanence, prerequisites, and included benefits.
Do not use outside sellers, scripts, extensions, or “unlock” services. If a limited ship is not offered in the live interface or a creator announcement, wait for legitimate availability.
Use the premium ships guide before spending Gold or Robux.
Progress through legitimate matches
Community references associate progress with match contributions such as damage, eliminations, objectives, interception, and healing where supported. Exact formulas can change, but useful team play is the dependable direction.
The official game description prohibits farming servers and warns they can cause resets or bans. Avoid arranged damage, idle loops, exploits, and automation. Normal matches teach the ship while earning legitimate progress.
Review first useful contact, objective effect, avoidable loss, and retreat after each match. Correct one mistake in the next round.
Common tech-tree mistakes
Do not spend because a button lights up. Do not skip the middle-ship review. Do not use Free XP merely to avoid learning a mechanic required later. Do not activate boosters on an unfamiliar hull. Do not compare nodes with screenshots from different dates.
Another mistake is changing faction after every loss. Hold the ship constant long enough to separate a bad route from a bad fit.
A safe unlock sequence
Choose a role, inspect three nodes, confirm the resource, play the current ship, build a reserve, and purchase only when you can explain the next hull’s battle plan. After unlocking, return to ordinary matches until its controls and retreat are predictable.
For later tiers, use the Tier IV to Tier V guide. Recheck updates whenever a visible node or value no longer matches your notes.