Black Ops II Strike Force Mission Guide

Treat Strike Force as a hybrid mode

The official Black Ops II manual describes Strike Force as a combination of real-time strategy and first-person shooter play. The player can fight as a soldier, command troops from a battlefield view, or control military drones. Operations connect to the story, and success or failure is reflected in the main campaign.

Begin in the broad command view long enough to identify objectives, friendly assets and likely pressure routes. Give units tasks that cover separate needs instead of moving the entire force as one group. Direct control is most valuable when the AI needs help completing a precise action, clearing a bottleneck or responding to a threat that the overview revealed.

Use a three-layer plan

First, define the mission object: defend, capture, escort or eliminate. Second, allocate forces to the object and to the route that can threaten it. Third, reserve one controllable soldier or drone for intervention.

Do not stay in first-person view simply because it is familiar. While controlling one unit, check whether the unattended objective is collapsing. Return to command view after the immediate task, reassess the whole field, then select the next intervention.

Scout before committing assets

Use drones or a mobile unit to reveal pressure without abandoning the objective. Keep fragile or specialized assets away from an unscouted route. If enemies repeatedly arrive from one direction, assign coverage there and use direct control to remove the highest-impact threat rather than chasing every target.

The manual's campaign section also confirms automatic checkpoint saving and a Save and Quit option. That does not mean every tactical mistake can be erased without consequence; Strike Force outcomes feed the campaign. Enter each operation knowing that a failure may be part of the saved story state.

Recover when the first plan breaks

When an asset falls, return to the mission object. Consolidate remaining units where they can still influence completion, then take direct control for the most time-sensitive action. Avoid spending the final force on a distant elimination while a defense point is being lost.

After the mission, record which overview decision failed: late scouting, poor lane coverage, unnecessary direct control or an unprotected objective. Replay from Mission Select only when you deliberately want to test a different campaign outcome or tactic, not because the guide promises one canonical result.

Keep campaign choices separate

Strike Force operations affect the campaign, but this page does not prescribe one ending. Preserve the result of the current playthrough, note the operation outcome, and use a separate replay if you want to compare branches. This protects the player's intended story while still allowing tactical practice.

Run a short command cycle

Use the same cycle throughout the operation: scan the objective, issue one or two clear orders, observe whether units are moving, take direct control for a precise intervention, and return to overview. Staying in command view without checking execution can leave units blocked; staying in first person too long hides changes elsewhere.

Prioritize information that affects the mission object. Enemy movement toward a defense point matters more than a distant target that is easy to eliminate. When two fronts are active, stabilize the one closest to failure and use remaining assets to delay the other rather than splitting every unit evenly.

If a drone is available, decide whether it is scouting, attacking or holding an angle before taking control. Switching tools without a purpose costs time. After every intervention, confirm that assigned soldiers still have a valid route and that the objective indicator has not changed.

This rhythm makes Strike Force easier to diagnose: a failure can be traced to scouting, orders, execution, direct-control timing or recovery, instead of being dismissed as random AI behavior.