Real-time wingman orders are an announced feature of ACE COMBAT 8: WINGS OF THEVE. The useful player question is not “which command is strongest?” before the menu is public; it is “what problem should an order solve, and how can its effect be verified?” Official sources mention the system but do not yet provide a final command list, button map, cooldown, or mission restriction.
Match the order to the objective
Read the Mission Objectives page first. A command that helps focus a threat may be wrong during an escort, while a protective order may be more useful than extra damage during a survival phase. Write the objective, protected asset, and current threat before selecting an order.
Keep the order’s purpose short: focus, protect, support, or reposition. These are planning labels, not official command names. Replace them with the exact menu language when the live build exposes it. A short purpose helps the pilot notice whether the squad actually did the intended work.
Verify the live control and response
Connect the input device and record the order menu, prompt, selected wingman, and visible feedback. Test one command in a low-pressure encounter, then compare the target behavior, ally position, radio text, HUD marker, and mission state. Do not infer an order effect from a voice line alone.
If the command is unavailable, note whether the reason is an objective phase, distance, resource, cooldown, aircraft state, or an unverified condition. Preserve the exact message. A missing command is not proof that the system is broken until the same state is reproduced in a current Windows build.
Test the order in more than one context before writing a recommendation. A command may be available during a normal air battle but unavailable during a cutscene, a scripted superweapon phase, or a protection objective. Record whether the selected ally changes position, attacks the intended target, draws fire, or simply acknowledges the request. If the effect is delayed, capture when the response begins and what event ends it.
Use orders without abandoning control
An order should support the pilot’s plan, not replace flight control. Stabilize the aircraft before opening the command interface, and keep enough awareness to avoid terrain or a missile warning. The Controls and Flight Basics page owns input setup; Chaff, Flares and Evasion owns defensive timing.
After issuing an order, continue to watch the objective. If the squad attacks one target while a timed condition advances, cancel or redirect only when the menu and mission allow it. Record whether the command persists after a phase transition, replay, or cutscene.
When an order fails, compare it with a direct pilot action in the same encounter. This separates a command limitation from a target that cannot currently be attacked. Keep a short callout in the guide—what the player asked for, what the squad did, and what the player should do next—rather than a vague promise that wingmen make every fight easier. This record also makes a future patch comparison possible.
Separate campaign and online coordination
A single-player wingman command is not automatically the same as a co-op or PvP team action. The Multiplayer hub owns online mode evidence. If the live game exposes team commands, record whether they target AI wingmen, human players, or both, and keep the platform and mode in the result.
This distinction matters when a player asks for a team tactic: the command owner, target, network mode, and version must be named before the advice can be reproduced for other pilots in practice with current evidence today.
The same record should state whether the order was available before or after a mission phase changed. Availability is part of the answer, not a minor menu detail.
This page was checked on 2026-08-09 UTC using the official product page, Bandai Namco walkthrough, and Steam listing. Expand it with exact command names and tested effects only after the Windows build provides a reproducible control and response.