Support

Discord Support Server

Use Discord for support, contact, feature requests, launcher feedback, server-browser reports, bad metadata reports, API questions, and release feedback. Do not post full API keys, payment details, passwords, private server credentials, or other sensitive secrets in public channels.

Check The Status Page First

The status page shows component availability and how fresh each dataset is. If it already reports a degraded component or a stale snapshot, the problem is probably known and a report adds little beyond the timing.

If an endpoint returns 202 Accepted, the API has queued a background refresh job. Wait for the Retry-After value and retry the same URL before opening a support request.

What To Include

Include the request URL, approximate time of the issue, response status, request ID if one was returned, and the API key prefix if the issue involves authenticated access. Do not send full API keys, passwords, payment card numbers, private server credentials, or other sensitive secrets.

Launcher Problems

Include the launcher version shown in settings, your operating system and version, and what you were doing when it went wrong — browsing, viewing a server, measuring ping, or joining. Screenshots of the state you are describing help more than a description of it.

Two things are expected behaviour rather than bugs. Beta builds are not code-signed yet, so Windows SmartScreen warns on first run; you can confirm you have the file we published by checking its SHA-256 against the SHA256SUMS beside it. And mod readiness is reporting only — the launcher says what the game will need and never installs Workshop content, so there is no "prepare mods" button to be missing.

If the launcher shows no servers at all, check the status page before reporting: an unreachable API looks the same as an empty list. Settings, favorites, recents and launch history live in launcher-state.json in the launcher's configuration folder, and deleting that file resets the launcher to a clean state.

Server Listing Corrections

If you operate a server and its listing is wrong or you want it removed from the site, include the server name, its id from the URL of its page here, and what is wrong. Servers are indexed from the official Arma Reforger lobby, so we can change what this site publishes but not what the lobby advertises — a server still publishing itself there may be re-indexed.

API Keys And Billing

For API key or paid-plan issues, include the account email, organization name if applicable, plan or invoice reference, and a short description of what changed or stopped working. Current public paid plans are Developer at $5/month and Pro at $15/month.

For a donation question, include the approximate date, the amount, and the receipt from Stripe. Donations are voluntary and unlock no features, so a donation receipt is not a plan reference and cannot be applied to one.

Abuse And Security

For abuse, automated traffic, exposed API keys, or security concerns, include enough detail to reproduce or verify the issue. Report suspected vulnerabilities to support@reforgermods.net rather than in a public channel, and give us a reasonable window to fix them before disclosing. We may rotate or revoke exposed keys and may limit traffic that threatens service reliability.

Privacy Requests

For privacy questions or account data requests, contact support from the email address associated with the API key or billing account where possible. Some operational, billing, security, tax, or legal records may need to be retained.

The launcher has no accounts, and the install identifier it sends is stored only as an irreversible digest, so we cannot look up or isolate one install's records from an emailed request. Uninstalling the launcher stops it being sent, and deleting the launcher's configuration folder clears what is stored on your device. See the Privacy Policy for what that identifier is and is not.