- Add a common in-process event bus - Emit task lifecycle events from task store and instances - Register CAD listeners to invalidate task state
Forge Server CAD
Overview
The CAD addon coordinates dispatch-facing operational state: groups, assignments, dispatch orders, support requests, task assignment, permissions, hydrate payloads, and recent activity.
CAD state is extension-backed but intentionally transient. It is scoped to the active server or mission lifecycle and starts fresh after restart.
Dependencies
forge_server_mainforge_server_commonforge_server_actorforge_server_orgforge_server_taskforge_server_extensionat runtime for CAD extension callsforge_client_cadandforge_client_notificationsfor response RPCs
Main Components
fnc_initCadStore.sqfcoordinates repositories and request handling.fnc_initActivityRepository.sqfrecords recent CAD activity.fnc_initAssignmentRepository.sqfmanages task assignments and dispatch orders.fnc_initGroupRepository.sqfmanages group membership, role, and status.fnc_initPermissionService.sqfresolves dispatch permissions.fnc_initPersistenceService.sqfbridges SQF state to extension hot CAD storage.fnc_initRequestRepository.sqfmanages support requests.
Event Surface
The addon handles hydrate, task assignment, dispatch order, support request, task acknowledge/decline, and group update events. Successful mutations can invalidate CAD state globally so clients refresh their views.
Notes
CAD hydrate payloads include active task catalog entries from TaskStore and
organization context from ActorStore.