Get All Releases

Stable

Getting all releases returns every release registered with the Daemon, each with a derived status computed from live job state and a symlink integrity check, and an overallPercentProgress across all assets.

Property	Value
Applies to	Daemon
Trigger	Client polls for the current state of all releases
Preconditions	None

Inputs

There are no inputs.

Assertions

Assertion	Status
None — the operation always returns a result, even if no releases are registered

Outputs

ModAndReleaseData[] : One entry per registered release. Each entry includes all stored release metadata, the asset list with per-asset statusData, symlink definitions, mission scripts, a derived status, and an overallPercentProgress.

Effects

None. This is a read-only operation. The symlink integrity check reads the filesystem but does not modify it.

Status derivation

Release status is computed in two layers.

Layer 1 — per-asset status (`inferAssetStatusFromJobs`)

Each asset's status is derived from its download and extract job states:

Condition	Asset status
Any download or extract job is `Failed`	`ERROR`
All download and extract jobs are `Pending`	`PENDING`
All download and extract jobs are `Success`	`COMPLETED`
Otherwise (mix of states, or jobs running)	`IN_PROGRESS`

If an asset has no job records, its status defaults to PENDING.

Layer 2 — release status (`inferReleaseStatusFromAssets`)

The per-asset statuses and the release's enabled flag are combined:

Condition	Release status
All assets `PENDING` (and list non-empty)	`PENDING`
Any asset `ERROR`	`ERROR`
All assets `COMPLETED`, `enabled=true`, symlinks invalid	`INCONSISTENT`
All assets `COMPLETED`, `enabled=true`	`ENABLED`
All assets `COMPLETED`, `enabled=false`	`DISABLED`
Otherwise	`IN_PROGRESS`

Symlink integrity check

The check only runs when enabled=true and the release has at least one symlink definition. Every symlink must have a non-null installedPath that exists on disk. Any symlink with a null installedPath, or whose path does not exist (including filesystem errors), causes symlinkIntegrityValid=false and the status becomes INCONSISTENT.

This detects mods that were enabled but whose symlinks were subsequently removed externally — for example by a manual cleanup or a DCS World update.

Behavior

mermaid

flowchart TD
    Start([getAllReleasesWithStatus]) --> ForEach[For each release in repository]

    ForEach --> Jobs[Get job progress report<br/>for each asset]

    Jobs --> AssetStatus[Compute per-asset status<br/>via inferAssetStatusFromJobs]

    AssetStatus --> Enabled{release.enabled AND<br/>has symlinks?}

    Enabled -- No --> SkipIntegrity[symlinkIntegrityValid = true]
    Enabled -- Yes --> CheckLinks[For each symlink:<br/>installedPath non-null AND exists on disk?]

    CheckLinks -- All pass --> IntegrityValid[symlinkIntegrityValid = true]
    CheckLinks -- Any fail --> IntegrityInvalid[symlinkIntegrityValid = false]

    SkipIntegrity --> Infer[inferReleaseStatusFromAssets<br/>asset statuses, enabled, symlinkIntegrityValid]
    IntegrityValid --> Infer
    IntegrityInvalid --> Infer

    Infer --> Progress[Compute overallPercentProgress<br/>across all asset progress values]

    Progress --> ForEach

    ForEach -- All releases processed --> Done([Return ModAndReleaseData array])

    style Done fill:#4ade80,color:#000

Get All Releases ​

Inputs ​

Assertions ​

Outputs ​

Effects ​

Status derivation ​

Layer 1 — per-asset status (inferAssetStatusFromJobs) ​

Layer 2 — release status (inferReleaseStatusFromAssets) ​

Symlink integrity check ​

Behavior ​

See Also ​