Project Stardust Guides

Project Stardust becomes much easier when you learn it in the right order. Begin with the interface and a forgiving ship, understand how range and firing arcs shape combat, then add specialized systems such as missiles, spinal weapons, or carrier wings. Troubleshoot input separately from strategy so a control problem does not become a bad lesson about the ship.

The official Roblox page describes a tactical team PvP experience featuring massive ships inspired by Star Wars, Halo, Space Battleship Yamato, and other science-fiction settings. It also states that a mouse and keyboard are required for normal play; unsupported devices may be limited to viewing the tech tree. Plan your setup before joining a serious match.

Current scope — checked September 12, 2026: Interface bindings and balance can change. Use the live control hints and settings as the final word, and treat community key descriptions as starting points when the current UI does not explain a function.

Start with the beginner route

The beginner guide takes you from the official experience page through the first tech-tree inspection, ship choice, match objective, engagement, retreat, and post-match review. It emphasizes actions that remain valuable across factions: staying near support, controlling range, reading weapon arcs, and leaving a losing fight early.

Do not rush to a high tier. A starter ship lets you learn acceleration, turning, target selection, and the result screen at low cost. Choose one question per match. Trying to master a new faction, new weapon system, new map, and new mode simultaneously makes it hard to know why an outcome changed.

Confirm controls before combat

Open the controls guide before you need a command under pressure. Test camera movement, thrust, steering, target interaction, weapon groups, interface focus, and any ship-specific panel in a safe opening moment. The visible current prompts take precedence over remembered bindings.

Project Stardust’s desktop requirement matters. A touch-capable Windows device can sometimes complicate pointer behavior at the Roblox level, while keyboard layouts and remapped inputs can change what a community post describes. Verify the action, not just the key name.

If input is stuck, use the mouse lock fix to separate an open Roblox menu, an accidental lock action, touch-input conflict, focus loss, and a temporary client problem.

Learn the combat loop

The combat guide turns a match into a repeatable loop: identify the objective, form near useful allies, enter the intended range, expose only the necessary angle, apply a coordinated weapon cycle, and disengage before the route closes.

Damage alone is not the whole result. A ship that remains alive can keep screening, contesting, intercepting, healing where supported, or threatening a lane. A ship destroyed during an unsupported chase cannot help the next objective.

Use the current range marker and target feedback rather than memorizing old numbers. Exact values can move, while the principle of fighting inside your envelope and outside the enemy’s best answer remains useful.

Add weapons one system at a time

Direct weapons teach range and arcs. Missiles add arrival timing and awareness of point defense. Spinal weapons make the hull part of the aim. Carrier craft add command states, travel time, interception, target roles, docking, and rearming.

Pick one system for a practice session. Observe when it begins contributing, what stops it, and how the ship escapes afterward. Change one variable in the next match. This creates reliable experience faster than switching ships every time a result disappoints you.

The weapons hub provides focused pages for the main systems, and the ship stats guide helps connect the hangar panel to execution.

Operate carriers deliberately

The carrier guide covers community-reported command families such as attacking, healing, pursuing, escorting, guarding, intercepting, scrambling, launching, docking, idling, and spectating. Names and bindings can change, so confirm them in the current carrier interface.

Carrier play is two battles at once. Protect the hull behind the team and suitable cover while sending wings on routes short enough to redirect or recover. Avoid repeatedly crossing the full map through concentrated point defense. Use fighters to intercept or escort when that creates more value than feeding an isolated target attack.

Dock or recover depleted craft when the current system allows it. A wing without useful ammunition or a valid command can appear active while contributing little.

Read modes before selecting a role

Deathmatch favors clean eliminations and survival. Fleet Battle makes ship-value trades important. Attack and Defend concentrates pressure around destructible objectives. Domination rewards capture presence and timely rotations. The current lobby defines exact score, timer, and map conditions.

Your ship choice should answer the mode. A long-range ship still needs to influence the objective. A durable ship should not donate itself alone. A carrier should keep wings relevant to the active lane. A fast ship should rotate before the capture state becomes irreversible.

Open the modes hub and then the current map page when you need a mode-specific plan.

Use a safe progression routine

Inspect multiple nodes ahead before committing to a tech-tree branch. Understand which resource a purchase uses, learn the current ship before applying a valuable booster, and keep a reserve rather than spending every balance immediately.

Community sources describe Credits, ship or branch experience, Free XP, Gold, boosters, premium access, and limited events. Current labels and conversion rules belong to the live interface. Never use outside sellers, scripts, or “unlock” tools.

The official experience description prohibits farming servers and warns that prohibited farming can cause a progress reset or ban. Legitimate team contributions and ordinary matches are the safe progression route. Use the progression hub for a complete plan.

Fix the first recurring mistake

After each match, identify the first moment the plan stopped working. Did you enter outside support, close too far, expose the wrong side, launch into ready defenses, lose fighter control, or wait too long to retreat? That first mistake often creates every later problem.

Choose one correction for the next match. Spawn beside a complementary ship, stop at the previous cover, hold a weapon cycle, guard the carrier, or turn out sooner. Improvement is easier to measure when the ship and role remain the same for several games.

Save screenshots of the current interface when you need help, but remove private account information. Include the ship, mode, map, visible control or message, and date. A precise current observation gets a better answer than an old clip with no context.

Recommended reading order

1. Beginner guide for the complete first-session loop.
2. Controls to verify the current interface and input.
3. Combat to manage range, focus, and retreat.
4. Ships and factions before spending deep into a branch.
5. Carrier guide only when you are ready for command management.
6. Mouse lock fix when pointer behavior prevents normal play.
7. Updates before trusting an old value or roster claim.

This order is not mandatory. It simply keeps foundational decisions ahead of specialized ones, making every new ship and system easier to understand.