one dataset · paper, tables, graph, wiki
simgrammar the grammar of simulation

core loop

read the scenario briefing -> set doctrine, emissions control, and weapon release authority -> assign units to patrol, strike, and support missions -> sensors detect and classify contacts -> weapons engage under doctrine -> adjust missions as detections and losses accrue

design notes

CMO simulates the sensor and weapon chain rather than abstract unit strengths: detection depends on radar propagation, terrain, thermal layers, and weather, and engagement depends on database specifications and doctrine. The player works mostly at mission and doctrine level and lets tactical AI fly and fight, so one player can run scenarios from patrol-boat skirmishes to global war. The Command engine also has a Professional Edition with full database editing, umpire-controlled multiplayer, and Monte Carlo analysis, sold to defense organizations.

relations

11 stored edges
uses

Delegation to AI managers

Units are assigned to patrol, strike, and support missions and executed by tactical AI under doctrine settings such as weapon release authority and EMCON.

core
uses

Fog of war

Each side sees only what its sensors detect; emission control (EMCON) policies trade a unit's own detection range against revealing it to enemy passive sensors.

core
uses

Military operations

Every platform's sensors and weapons come from a database of tens of thousands of real systems; radar propagation, sensor degradation, terrain masking, sonar thermal layers, weather, jamming, and anti-radiation strikes are modeled for thousands of active platforms in real time.

core
uses

Content sharing

Scenarios are shared through the Steam Workshop.

supporting
uses

Modding API

A Lua scripting engine and scenario editor let players build custom operations.

supporting
uses

Projectile ballistics

Ballistics are among the modeled effects alongside sensor propagation, so weapon flight and impact follow database specifications.

supporting
uses

Scenario objectives

Over 600 official and community scenarios plus a quick battle generator.

supporting
uses

Scouting knowledge

Contacts begin unidentified and are classified as sensor data accumulates.

supporting
uses

Unit commands

Direct orders override a unit's mission behavior.

supporting
uses

Pause and speed control

Scenarios lasting hours to days of game time run with time acceleration and pause.

supporting
uses

Weather

Weather degrades sensors and affects engagements.

supporting

sources

2
Wikipedia contributors (2026). Command: Modern Operations. Wikipedia

provenance

runs in log/runs
2026-10-24
created2026-10-24-catalog-gicatalog