Developer docs / Conflict Operations API
Conflict Operations API
A developer guide to the Arma Reforger addon and the Workbench workflows used to build and verify it.
Architecture
Conflict Operations API is an Arma Reforger addon. Its project identifier is ConflictOperationsAPI. It combines Enforce Script policy and diagnostics with serialized mission, prefab, and configuration resources. The project manifest declares dependencies. The shipped package and fresh runtime logs show what the engine actually loads.
AddonRelay is a separate web service and Windows companion for inspecting and troubleshooting a developer’s own project. Its REST API accepts structured diagnostic inputs.
Workbench setup
- Open the addon’s
addon.gprojin the Windows Workbench version matching your intended game build. - Resolve each dependency from that exact checkout’s project manifest. Record the addon GUID, Workbench build, and branch before changing the project.
- Validate scripts with the intended project active. Open Resource Browser to check the exact GUID and path for any resource named in the compile or load log.
Manifest at the reviewed revision
Project ID: ConflictOperationsAPI
Project GUID: CD4A9E3FFE7F4A55
Direct dependency GUIDs: 58D0FB3206B6F859 and 64F10E068D5880A6.
These are the entries in the reviewed addon.gproj, not a claim about every release. The README dependency list differs from the manifest. For your checkout, use its actual manifest and the fresh engine-loaded graph. Do not invent a resource or substitute a similarly named addon.
Extension points
Start with the system that owns the behavior. Use Enforce Script for policy or diagnostics, a prefab for inherited components and defaults, a configuration for data, and the mission or campaign manager for scenario wiring. Extend through your own addon when the relevant classes and resources support it. Verify signatures and resource names against the installed build.
Source map at the reviewed revision
Game scripts are under Scripts/Game/ConflictOperationsAPI/. Start with these local definitions when you have access to that checkout:
ConflictOperationsAPI_ArsenalPolicy.ccontains resource and faction policy checks, includingIsBlockedArsenalResourceForFaction.ConflictOperationsAPI_RuntimeSafety.ccontains guards around native catalog access and diagnostic markers for unsupported operations.ConflictOperationsAPI_RuntimeDiagnostics.cprovides runtime evidence and diagnostic reporting.Scripts/WorkbenchGame/ResourceManager/COAPISeedExporterPlugin.cis version-specific Workbench tooling; inspect its implementation before treating it as a usable export path.
These files describe the reviewed implementation, not a stable, versioned plugin ABI. Do not call a helper solely because its name resembles the behavior you want. Locate the declaration, read its current guards and call sites, then validate the active project.
For example, to add an original training beacon, create its prefab in your project, resolve its current resource identity, and point the consuming configuration at that identity. Validate with the same dependencies a player or server will load.
Local validation
The checkout provides node Tools/validate_conflict_operations_api.js. Inspect the tool and its prerequisites before running it on a different revision. A validator pass supplements compilation and fresh runtime evidence; it does not replace them.
Diagnose a failure
- Read the earliest concrete failure from a fresh run. Record the line and source.
- For a missing symbol, locate its declaration in the active project and installed dependencies. For a resource error, compare the GUID and relative path with the owning project’s metadata.
- For a version mismatch, compare both loaded-addon lists in order. Check configured entries and implicit dependencies before choosing which package to update.
Verify a release
- Record the checked-out revision, project GUID, dependency set, and Workbench version.
- Compile the active source, pack the intended tracked resources, and inspect the staged package before publishing.
- Verify the version and contents of the Workshop download against the candidate package. Boot the exact package and configuration, compare loaded addon graphs, and confirm a clean client join.
The tagged COAPI release documents an external staging and package-verification workflow. The release workflow and Workbench Seed Exporter scaffold are version-specific. This guide makes no claim that the scaffold shipped or that a private release tag matches a live server today.
Source versions reviewed
Architecture and local diagnostics were checked against the laptop checkout at 7d0cc5727416. Release workflow was checked against the private GitHub tag post-233-chatgpt-pro-recovery-007a0e4. GitHub default branch 4e707e8934a3 documents the foundation addon and can differ from later release tooling. Use the manifest and evidence for the version you actually run.