File verification and repair
Use prepare for the launcher’s Verify files or Repair action. It
checks the downloaded client files and the selected server’s resources against
their manifests, then replaces missing or damaged files.
Choose the right check
Section titled “Choose the right check”| Command | Verification |
|---|---|
inspect |
Fetches manifests and checks local paths and file sizes. Use its result to choose the launcher’s main action. |
prepare |
Hashes file contents even when previous verification records exist. Use it for explicit verification and repair. |
launch |
Reuses saved verification results for unchanged files. Changed files, files without a usable verification record and new downloads are hashed before use. |
An inspection result of ready means the files passed the path and size checks.
Damage that leaves the file size unchanged can pass inspection. A repair
checks the contents against their SHA-256 hashes.
Add a repair action
Section titled “Add a repair action”Run this through the same helper process integration as installation:
.\client-helper.exe prepare --join-code YOUR_JOIN_CODEUse the selected server’s join code. Preparation resolves its current requirements, so repair can also install a newer compatible client release or updated server resources.
Show Checking files during status.stage: "checking", then display the
download progress if
files need downloading. Hashing a large installation can take time before
any download begins.
Wait for the terminal ready event and a successful process exit. Inspect
again to refresh the launcher’s state. Start the game with launch when
the player presses Play.
Reuse existing downloads
Section titled “Reuse existing downloads”The helper checks cached files before using them for repair. A damaged installed file can be restored from a valid cached copy without downloading it again. Files shared between resource bundles can also be reused.
Repairs assemble a verified replacement bundle in a separate directory. Use the paths returned by the helper. The storage guide covers disk-space requirements and cleanup of old copies.
After an interrupted download, run prepare again for the same server.
Completed downloads and partial files remain available for reuse. The helper
resumes partial downloads when the host supports range requests, or restarts
them when necessary. Corrupted partial files are discarded and downloaded
again. The pause/resume flow
uses this behavior.
Handle repeated failures
Section titled “Handle repeated failures”Read code, message, retryable and any details from the terminal error.
Offer Retry when retryable is true. The helper already makes bounded
retries during downloads, so keep further attempts under the player’s control.
| Error | What to check |
|---|---|
download_failed |
Check the connection and resource host. An HTTP status may be included in the message. Repeated 404 responses usually require correcting the published file URL or deployment. |
integrity_error |
The downloaded data does not match its expected hash. If retrying keeps failing, check that the published manifest, files and CDN content belong to the same release. |
invalid_manifest |
Check the manifest’s format, version and file entries. Publish a corrected resource package. |
security_blocked |
Review the antivirus detection or protection history for the named file. Include that information in a support report. |
For resource publishing failures, check the packaging and deployment setup. For file locks, permissions or disk-space errors, see Resource storage and disk management.
Keep available error details in the launcher’s diagnostic log, including
path, resource, windowsError or errno when present. They help distinguish
a download failure from a local file-access problem.