Star Fox Switch 2 Wiki

Start with Fox when learning the campaign flow, because official material frames him as the central pilot.

Track Falco for team banter, pilot roles, and amiibo-linked multiplayer cosmetics.

Use Slippy entries for crew context, engineering notes, and technical dialogue.

Use Peppy entries for tactical advice, team history, and James McCloud context.

Use Andross entries for the main conflict, Venom context, and villain-related route notes.

Use Wolf entries for amiibo Battle Banner backgrounds and emblems.

Use this as the top-level setting when following story and route references.

Expect Corneria references to carry story context beyond a single mission label.

Meteo is the best early hands-on stage to study controls before buying.

Treat Solar as a high-hazard location until route and mission mechanics are fully documented.

Use Sector Y as both a navigation term and a Battle Mode stage reference.

Track Fichina first as a multiplayer stage with its own rules and objectives.

Use Venom for Andross background, story context, and villain-route references.

Begin here for route learning, stage order, and controls.

Start on Normal if you want the default route pressure; use Easy to learn stages before medal attempts.

Record objective triggers, squadmate cues, mission briefing changes, and the next available mission.

Use this mode after a first clear to chase objectives and lore rewards.

Track player counts, banners, and amiibo cosmetics here.

Use stage rules and objectives as the main Battle Mode documentation target once matches can be tested.

Decide early who pilots and who guns, because those roles affect how you learn each mission.

Try this in the demo tutorial before committing to a control scheme.

Use amiibo entries for Battle Banner backgrounds, emblems, and collection notes.

Treat this as a social feature requiring hardware and online requirements, not core campaign progression.