Factions

Project Stardust Space Battleship Yamato Tech Tree

Plan the Project Stardust Space Battleship Yamato tech tree across UNCF, Garmillas, Gatlantis, and GUIA playstyle tendencies.

The Project Stardust Space Battleship Yamato tech tree is documented by the community through UNCF, Garmillas, Gatlantis, and Great Urup Interstellar Alliance branches. Players often discuss this family in terms of mobility, aggressive pressure, powerful beam windows, or hard-hitting specialized ships, but the mix changes across branch and tier.

Choose by the repeated engagement rhythm visible in the current tree. A highlight attack is only useful when the preceding approach and following retreat are both possible.

Community corroborated — checked September 12, 2026: The four faction groupings above are widely referenced. Current ship nodes, access, prerequisites, stats, and exact playstyles must be confirmed in the live interface.

Inspect every visible branch

Open the franchise tree and trace connections from starter access through several future nodes. Record branch splits, currency icons, prerequisites, and any premium or event marking. Do not infer current availability from a community image or lore list.

For three consecutive ships, note preferred range, movement demand, primary defense, weapon alignment, and objective role. A branch that looks similar by silhouette may change dramatically when a later hull adds beams, a spinal system, missiles, or carrier craft.

Choose a near target you can test rather than planning only around the farthest ship.

Treat mobility as timing

Community discussions often associate parts of the Yamato family with fast or decisive movement. Practical mobility is not only top speed. Acceleration, turn radius, profile, stopping distance, and escape geometry determine whether a ship reaches a useful position safely.

Use speed to arrive early, rotate between objectives, or shorten exposure across a gap. Do not use it to enter before teammates. A fast ship with no supported retreat can be focused as quickly as a slow ship.

Test movement during a safe opening and choose cover transitions that match the actual hull, not the franchise reputation.

Build around beam and attack windows

Hard-hitting beams or other concentrated systems reward a clear target window. Identify the range and arc from the current interface, watch the weapon cycle, and avoid exposing the ship throughout a long recovery without support.

If the system requires hull alignment, choose predictable targets and lanes. If it rewards sustained tracking, avoid turns that interrupt your own pressure. In both cases, the attack begins with position.

Keep another option for the target’s response. Missiles, defensive coverage, movement, and allies can protect the recovery rather than being used blindly at the same instant.

Compare the four faction tendencies carefully

Community role descriptions for UNCF, Garmillas, Gatlantis, and GUIA are not always consistent and can become outdated after balance changes. Instead of repeating a rigid label, inspect how each accessible branch solves five problems: reaching range, surviving focus, keeping weapons aligned, helping an objective, and leaving.

Create a one-line summary only after inspecting current ships. For example, describe a branch as “mobile pressure with demanding turns” or “slower beam lane with strong attack windows.” This is more actionable than calling one faction best.

If two branches share a role, prefer the one whose middle-tier ships fit your current skills and resources.

Match the tree to the map

Open areas can reward range and concentrated fire but expose the approach. Dense structures can protect mobile closing routes while limiting the turn of a large hull. Fewer, larger obstacles can create dangerous gaps between cover.

Before spawning, identify the first useful lane and an exit. A decisive ship should not be committed to a corridor that ends against geometry. Spinal or forward systems need room to align; broadside systems need enough cover for the exposed profile.

Review Requiem, Shipyard, and SUS Fortress as tactical identities, then trust the current map layout.

Match the tree to the mode

Deathmatch rewards attacks that secure an elimination without donating the ship. Fleet Battle increases the importance of value trades, making an unsupported capital push especially dangerous. Attack and Defend creates predictable objective lanes that can support powerful attack windows. Domination demands timely presence or pressure on the capture area.

A ship known for dramatic damage still needs to serve the live objective. If it cannot rotate or reach the active lane, select a more suitable accessible hull.

Use the modes hub to build the objective into the branch decision.

Progress through learning stages

Earn ordinary matches until the current ship’s approach, main cycle, and retreat are repeatable. Save stronger boosters for that stable stage. When a new node changes size, speed, defense, or weapon alignment, pause and practice again.

Check whether the purchase consumes Credits, ship or branch experience, Free XP, Gold, or another current resource. Keep a reserve and verify the confirmation dialog. Never use outside unlock services or prohibited farming servers.

Use the currency and boosters pages before a long session.

Common Yamato-tree mistakes

The most common mistake is copying an aggressive clip without the setup. The second is confusing top speed with safe rotation. The third is using every attack system at once and having no response during recovery. The fourth is selecting a large ship on a map lane without turning space.

Avoid treating faction descriptions as permanent statistics. Avoid exact values from undated community pages. Avoid pursuing one target after the objective moves.

If performance differs from a guide, check current range, arc, mode, map, and server before concluding that the ship is broken.

Choose a branch with a trial

Shortlist two paths based on current visible nodes. Play the nearest accessible ship in each and track first-contact timing, useful time in range, ability to recover, and objective impact. Keep ship changes limited so the comparison is meaningful.

Commit when you can explain what the branch asks you to repeat and why you enjoy it. The ships list helps organize candidates, while weapon types clarifies the systems that create each branch’s attack window.

Continue with another focused Project Stardust guide.

Factions

Project Stardust Halo Tech Tree

Compare the Project Stardust Halo tech tree, including broad UNSC and Covenant playstyle tendencies, ship defenses, weapons, and progression.

Factions

Project Stardust Mass Effect Tech Tree

Compare Project Stardust Mass Effect branches for Systems Alliance, Asari, Migrant Fleet, and Reaper roles, defenses, range, and progression.

Factions

Project Stardust Star Wars Tech Tree

Plan a Project Stardust Star Wars tech-tree path across its community-documented factions, roles, ships, weapons, and progression choices.