Project Stardust Factions

Project Stardust brings ships inspired by Star Wars, Halo, Space Battleship Yamato, and Mass Effect into the same team battles. Each franchise contains factions or branches with different approaches to durability, range, mobility, carriers, missiles, beams, and direct-fire weapons. The right first tree is the one whose repeated decisions match how you want to fight.

This hub compares broad identities without pretending every ship in a franchise behaves the same way. Community terminology is useful for orientation, but the in-game tech tree is the authority for current nodes, prerequisites, prices, and ship statistics. Open it before committing Credits, experience, Gold, or a valuable booster.

Community corroborated — checked September 12, 2026: Current community references document multiple factions beneath all four headline franchises. Individual branches and balance may be revised, and player descriptions such as “brawler” or “artillery” are role shorthand rather than official universal classes.

Choose a franchise with three questions

First, decide how close you want to be. Long-range play rewards aim, sightline selection, and patience but can struggle when cover blocks pressure or an objective demands presence. Close-range play rewards timing and concentrated damage but punishes an exposed approach. Flexible midrange ships often give new pilots more options, though versatility is not the same as immunity to mistakes.

Second, choose a defensive rhythm. Some lines lean on hull strength, some on shields, some on speed or a small exposure window, and some on destroying threats before they arrive. Your preferred rhythm should influence the branch more than a single famous ship.

Third, decide how much interface management you enjoy. Direct-fire ships emphasize positioning and aim. Missile ships add timing and target-defense awareness. Carriers add wing selection, travel planning, commands, rearming, and protection of the carrier itself.

Star Wars tech trees

Community documentation divides Star Wars ships among branches such as Republic, Confederacy of Independent Systems, Empire, Rebel Alliance, New Republic, and First Order. The franchise is often described by players as broad and versatile: it offers line ships, brawlers, carriers, and longer-range choices rather than one single defensive identity.

That breadth makes Star Wars a sensible place to explore roles, but it also means the franchise label alone tells you little about a specific node. Inspect each ship’s weapon arcs, fighter complement, mobility, defenses, and prerequisite path. Use the Star Wars tech tree guide for a branch-planning method that does not depend on a brittle full roster.

Halo tech trees

The principal community-documented Halo paths are UNSC and Covenant. UNSC ships are commonly associated with substantial hulls, direct long-range pressure, missiles, and prominent spinal weapons, while many Covenant ships lean more heavily on shields and plasma-style or missile pressure. These are tendencies, not promises for every node.

Halo is attractive to players who like a clear commitment to firing alignment or defensive cycling. A spinal weapon can deliver meaningful pressure only when the hull’s facing and target movement cooperate. Shields can absorb a mistake only if the ship creates time to recover. The Halo tech tree guide turns those tendencies into practical checks.

Space Battleship Yamato tech trees

Community references group this franchise into UNCF, Garmillas, Gatlantis, and Great Urup Interstellar Alliance paths. Players often discuss these lines in terms of fast movement, aggressive approaches, beam pressure, or hard-hitting weapons, but the exact mixture varies by faction and tier.

This franchise can appeal to pilots who want decisive movement and strong attack windows. It punishes copying a highlight clip without understanding approach timing, turning space, and escape. Read the Space Battleship Yamato tech tree guide before deciding whether a particular branch supports mobility, brawling, sustained beams, or a more specialized role.

Mass Effect tech trees

Community navigation currently documents Systems Alliance, Asari, Migrant Fleet, and Reaper branches. Player descriptions commonly associate Systems Alliance with longer-range spinal pressure, Asari with shield-focused survival, Migrant Fleet with durable or supportive play, and Reapers with dangerous closer-range sustained damage. Current ship panels must confirm how a specific hull actually expresses those traits.

Mass Effect branches suit players who want pronounced defensive or range identities, but they still require objective awareness and team support. A shield-oriented ship cannot recover under uninterrupted focus, and a short-range damage ship needs a viable closing lane. Use the Mass Effect tech tree guide to compare branch commitments safely.

Compare branches instead of final ships

Do not choose a path only because its last visible ship looks powerful. You will spend most of the journey in earlier nodes, and a branch can ask you to repeat a playstyle you do not enjoy. Inspect several consecutive ships and look for a consistent skill that you want to practice: range control, spinal alignment, shield timing, missile sequencing, fighter command, or cover-based approach.

Also check whether a branch splits. A prerequisite may consume a resource pool or require experience earned with a specific ship. The current interface should show that relationship. If it is unclear, earn another match’s worth of resources and verify before buying rather than assuming a community diagram is current.

Create a short comparison note with five lines: preferred distance, main defense, turning or acceleration demand, signature weapon, and team contribution. That is enough to separate branches without relying on a tier list.

Test a tree before using strong boosters

Starter access gives you a low-cost way to feel a franchise. In early matches, record how quickly the ship reaches cover, how much facing matters, whether the weapon cycle fits your attention, and how safely it retreats. Do not judge a complete tree by one bad match, but do not ignore a repeated mismatch between its rhythm and your preferences.

Save high-value boosters until you can contribute consistently. Community players recommend learning a ship first so boosted matches are not spent discovering basic arcs or controls. Normal team play, objective pressure, survival, interception, and support are legitimate ways to improve progress. The official description prohibits farming servers.

Faction choice by player style

If you enjoy adapting between several roles, begin by inspecting Star Wars branches. If you want pronounced hull, shield, missile, or spinal identities, compare UNSC and Covenant. If decisive movement and powerful attack windows appeal to you, inspect Space Battleship Yamato paths. If you want strong distinctions between range, shield, support, and sustained close pressure, inspect Mass Effect.

These are starting directions, not rankings. Current balance, mode, map, and teammates can make any branch feel different. A flexible player can also build experience in two low-tier paths before committing resources deeper into one.

A practical faction checklist

Before purchasing the next node, confirm the ship is on the intended branch, the displayed currency is the one you mean to spend, and the prerequisite is complete. Review its range, defense, mobility, weapon arcs, and special systems. Then decide where it contributes in Deathmatch, Fleet Battle, Attack and Defend, or Domination.

After unlocking it, play enough ordinary matches to learn one safe opening and one retreat route. Review the ship stats guide and weapon types guide when a panel term is unclear. If the ship carries wings, add the carrier guide before risking them across concentrated point defense.

The best faction decision is not permanent allegiance. It is a resource-conscious choice that gives you ships you will actually learn, a role your team can use, and a progression path whose middle steps are as appealing as its final silhouette.