Campaign Runs: Plan Shade's Climb Through the Galactic League

The solo campaign in STAR WARS: Galactic Racer is described as a runs-based climb through the Galactic League. You play as Shade and aim to unseat the corrupt champion Kestar Bool. Official material also names permanent choices, a fresh run after too many crashes, and Hibi’s workshop as part of the campaign structure.

That is enough to prepare a run notebook, but not enough to publish an exact event map or a guaranteed best build. Use the route below to preserve information between attempts.

What a run means

The official description establishes four useful rules:

• the campaign is runs-based rather than one linear championship;
• choices are permanent within a run;
• crashing out too often starts a fresh run;
• some perks carry over, though the exact list and limits are not fully published.

Do not confuse a fresh run with a total reset. The persistent layer is part of the official pitch, but its exact perks, unlock costs, and event rules need launch testing.

Keep a run card

After each event, record:

Field	Example of what to capture
Branch	Which event or league choice appeared.
Vehicle	Vehicle class and any visible upgrade.
Objective	Win, survive, time target, rival challenge, or other stated goal.
Result	Finish position, crash, reward, and damage state.
Choice	The option selected and whether it was permanent.
Carry-over	Perk, credit, workshop change, or unlock visible afterward.

This is more useful than a simple win/loss count because the campaign’s value is in comparing different paths to Kestar Bool.

Choose the next event by risk

Until the full event map is known, use a simple risk order:

1. Take a route that teaches a new objective while the vehicle is healthy.
2. Test the same vehicle class in an Arcade event if you need handling practice.
3. Spend a limited perk only after writing down its trigger and expected purpose.
4. Avoid stacking an untested branch, a new vehicle, and a rival challenge in the same fragile run.

This is planning advice, not a claim about hidden event weights. The official pages confirm Arcade time trials, precision driving, Scenarios, and multiplayer separately; they do not promise that those modes share campaign progress.

Use Hibi’s workshop as your checkpoint

Hibi’s workshop is part of the campaign framing. Treat every visit as a checkpoint for documenting the garage state: current vehicle, available upgrade, credits, perk, and the next league objective. If an upgrade changes a stat, write the old and new values when the release build displays them. Do not use a generic Star Wars racing assumption to fill a missing number.

Crashes and the next attempt

When a run ends, do not immediately repeat the same branch. First compare:

• which event caused the crash;
• whether the failure was speed, contact, route choice, or an objective mismatch;
• what persistent perk or workshop state survived;
• whether a different vehicle class would test the same challenge more safely.

That makes each fresh run a controlled experiment. It also prevents a single bad event from being mistaken for proof that the entire vehicle is weak.

Unknown until launch

The official material does not yet specify the full event tree, exact perk carry-over, campaign length, restart conditions, upgrade prices, or whether every vehicle class can appear in every branch. The story and campaign page tracks the confirmed structure; this page is the practical notebook version.