Series name: Decision Drills — Combat Edition
101_Forest signal — trial balloon for the series
Concept
This is a trial mission for the DCS community — a trial balloon for a series of short scenarios focused on practicing decision-making under time pressure and ROE constraints. The plan is that after 1.01 follow 1.02, 1.03, …, and that the pilot, through a series of lessons, builds a personal scheme and decision-protocols. The continuation of the series depends on your likes, comments and downloads.
Series objective
Short, clearly framed missions (10–25 min).
One key question per lesson (e.g., ROE vs package protection, fuel vs commit, risk vs signal).
Standardized debrief and export of “IF–THEN” rules into a personal Decision Protocol (a list of one’s own heuristics).
101_Forest signal (teaser)
Theme: Escort of an F-16 pair for a B-52;
Decision focus: border/ROE, “push or cover”, salvo timing, fuel discipline.
Outcome: quick debrief → 2–3 “IF–THEN” rules the pilot adds to their protocol.
Roadmap (example)
• 102 – Corridor Ambush: CAP/SEAD dilemma with refueling.
• 103 – SAR Under Threat: priorities: time vs threat vs fuel.
• 104 – Intercept Ladder: identification/declare → proportional force.
• 105 – Low-Level Strike: IADS “gates” and abort criteria.
• 106 – Maritime Intercept: ROE, ident, fuel bingo over water.
How you can help
Fly 101_Forest signal, report in the comments:
• what was unclear in the comments,
• which key decision was the hardest,
• which “IF–THEN” rules you wrote into your protocol.
The missions will be enriched with brevity codes and explanations, so that players will simultaneously learn and practice brevity while flying the missions.
________________________________________________________________________________________________________
Player Instructions — Mission Flow
Phase One — Solo Run (Singleplayer)
• Each pilot first plays 101_Forest Signal alone, in Singleplayer mode.
• Purpose: become familiar with procedures, ROE rules, threats, and mission flow without the pressure of coordination.
• During the flight: take notes (what worked, what was confusing, which decisions were hard, what you would do differently).
• After finishing: write a short conclusion — 2–3 “IF–THEN” rules or lessons for your personal “decision protocol.”
________________________________________
Phase Two — Debrief (Individual Reflection)
• Each player writes down:
o The most important decision point from the solo flight,
o One mistake or dilemma,
o One key lesson to pass on to the other pilot.
• Goal: turn individual experience into clear, transferable lessons.
________________________________________
Phase Three — Multiplayer Run (Co-op)
• Now both players fly the mission together in Multiplayer mode: one as lead, the other as wingman.
• Apply the rules and lessons from the solo phase:
o compare decision-making,
o practice brevity calls,
o test coordination under pressure.
• After the flight: debrief together and write 2–3 joint IF–THEN rules that will be part of your shared decision protocol for future lessons.
________________________________________
Core Idea
• Solo runs = develop individual awareness, learn through personal trial and error.
• Multiplayer runs = integrate lessons and test coordination in a team environment.
• Both phases are designed as training for building decision-making protocols that will grow across the series (101 → 102 → 103…).
