Change one branch at a time while holding the pilot and wingman constant, then compare completion, score, medal, and newly revealed route evidence.

To map a Wild Blue Skies branch, keep the crew stable and change one mission action. Pilot traits, wingman behavior, upgrades, target choices, and the route can all affect the result. If several change at once, a new medal does not prove which one mattered.
Clean branch test
- Finish the mission once and note the pilot, wingman, visible route landmarks, completion result, score, and medal.
- Identify one suspected branch point—a target group, movement choice, rescue, or timed event that appears to offer an alternative.
- Replay with the same pilot, wingman, and upgrades. Change only the action at that point.
- Confirm the new path by a different landmark or objective, not merely by a score change.
- Repeat the trigger once. A secret route is useful guide evidence only when the same action produces it again.
- After the route is confirmed, test crew or upgrade changes separately for medal improvement.
Steam describes branching paths, secret routes, pilots with different traits, wingmen, upgrades, and high-score medals. Those systems make controlled comparison more reliable than an unverified “shoot everything” instruction. Achievement names can hint that teamwork or decoration matters, but names alone do not establish unlock conditions.
This page will split into mission-specific route notes only when a branch has a reproducible trigger and outcome. Return to the Wild Blue Skies guide for verified platform and feature information.
Save a screenshot of the branch landmark when possible; it makes a later retest easier to compare.
Sources
QUICK ANSWERS
Questions players ask next
How do I test a Wild Blue Skies secret route?
Repeat the mission with the same pilot and wingman, change one action near the suspected branch, and confirm that the route change occurs again.
Does a higher score always mean a different route?
No. Accuracy, targets, survival, or route can all affect results. Keep the loadout stable before attributing a score change to a branch.