Project Stardust is a tactical Roblox team PvP game built around massive science-fiction ships. The official experience page highlights ships inspired by Star Wars, Halo, Space Battleship Yamato, and other settings. It also states that normal play requires a mouse and keyboard; unsupported devices may be limited to viewing the tech tree.
Your first goal is not a high-tier ship. It is a repeatable match loop: read the objective, spawn a manageable hull, stay near support, fight inside the ship’s useful range, and leave before focused fire closes the route.
Join the correct experience
Start from the official Project Stardust Roblox page and confirm that the creator shown is Military Flight Simulator Community. Launch through the normal Roblox client.
Do not use outside launchers, unlock tools, currency sellers, browser scripts, or pages requesting a Roblox security cookie. The official description also prohibits farming servers and warns that prohibited farming can result in a progress reset or ban.
Let the main interface load before selecting a ship or changing controls.
Check controls in a safe moment
Use the live hints and settings to verify camera, movement, throttle or thrust, steering, targeting, weapon groups, interface focus, and any ship-specific controls. Current prompts take priority over an old key list.
Move gently at first. Learn acceleration, stopping distance, and turn space before approaching structures. Cycle weapon groups only when it is safe and observe the arcs or target feedback.
If pointer behavior is stuck or the menu captures input, use the mouse lock fix rather than changing random system settings during a match.
Inspect the tech tree
Browse Star Wars, Halo, Space Battleship Yamato, and Mass Effect branches. Community sources document multiple factions beneath them, but the live tree is the authority for current nodes, tiers, costs, prerequisites, and availability.
Pick a starter or accessible ship whose basic role you understand. Inspect health or shields, speed and turning, main range, firing arcs, missiles, point defense, spinal mounts, or carrier craft. Do not choose only by name or size.
The tech tree guide helps compare several nodes before spending.
Read the mode before spawning
Community references describe Deathmatch around eliminations, Fleet Battle around value-weighted ship losses, Attack and Defend around destructible objectives, and Domination around capture control. The current lobby and HUD determine exact rules.
Choose a ship that can help the objective. A slow capital ship needs a relevant supported lane. A fast ship should rotate without arriving alone. A carrier should keep wings close enough to redirect. A long-range ship must influence the actual fight.
Open the modes hub when the win condition is unfamiliar.
Follow the team without stacking
Watch where allies move after spawn. Stay close enough for mutual direct fire, screens, and point-defense coverage, but leave room for large hulls to turn. Do not follow the fastest ship so far that the rest of the team disappears.
If one lane is empty, observe it from safety rather than trying to defeat the entire enemy side. If teammates retreat, create space and cover rather than blocking their path.
Good formation gives you more time to aim and a safer place to recover.
Fight inside your envelope
Use current range and target feedback to find where the main weapon group works reliably. Keep the target inside a useful arc without exposing more of the hull than necessary. Cover should remove enemy firing lines while leaving your intended line open.
Do not close automatically just to use a shorter secondary weapon. Missiles need timing against point defense. Spinal weapons need hull alignment. Brawlers need a protected approach. Carrier craft need commands and manageable travel.
Read weapon types after the first matches reveal which system needs help.
Focus a useful target
Attack enemies that teammates can finish, ships threatening a vulnerable ally, or targets whose removal changes the objective. Avoid spreading damage across several retreating hulls.
Do not chase a low-health ship behind enemy cover. Stop when allies leave, several enemies turn toward you, or the target reaches stronger support. An unfinished enemy is better than donating your own ship.
After an elimination or failed push, reset formation before the next engagement.
Retreat early
Choose a retreat route before firing. Set a trigger such as losing shields, taking focus from several enemies, losing a key weapon, depleting carrier craft, or seeing cover close.
Turn out while defenses remain. Large ships need more warning because they accelerate and rotate slowly. Move toward teammates and defensive coverage, not simply away from the current target.
Survival lets you contribute to another objective cycle and protects the team score.
Understand the result screen
After the match, review objective effect, useful damage or eliminations, interception or support where available, survival, and progression rewards. Exact reward formulas can change, so do not build a permanent rule from one result.
Record the first mistake rather than the final explosion. The first mistake may be an unsupported route, entering outside range, exposing the wrong side, launching into ready defenses, or waiting too long to retreat.
Change one behavior in the next match while keeping the ship familiar.
Spend resources carefully
Community references describe Credits, ship or branch experience, Free XP, Gold, boosters, premium ships, and event access. Read the live resource icon and confirmation dialog before every purchase.
Keep a reserve. Learn a ship before applying valuable boosters. Do not use outside sellers or exploit-based shortcuts. Normal matches combine legitimate progress with the practice required by later tiers.
Use currency and boosters when a target branch becomes clear.
Add specialized roles later
Once direct movement and combat feel predictable, try missiles, spinal ships, screens, or carriers one at a time. Carriers add craft roles, commands, travel, docking, and hull protection; they are a poor first choice when basic controls are still uncertain.
Use a familiar map and ordinary match for each test. Observe what makes the system work and what counters it. Keep older exact values secondary to the current interface.
The carrier guide is ready when you want that extra management layer.
First-session checklist
Confirm the official experience and desktop input, test movement and interface focus, inspect one branch, choose a manageable ship, read the mode, follow support, learn the primary range and arc, retreat early, and review one mistake.
Repeat with the same ship for several matches. Then choose the next page based on a real question: controls, combat, ships, factions, or maps. A deliberate first session builds skills that survive every balance change.