Using the launcher

This page covers day-to-day use of the ArcheAge Origins launcher (current version 0.3.5).

Use Player guide to open these guides in your default browser. The button is also available before sign-in.

Sign-in and sessions

• Use the username and password from your verified Origins account. New accounts are not created from the launcher login form.
• The launcher stays signed out until Login authenticates you.
• After a successful login, a refresh token is stored only in the OS credential store (Linux Secret Service or Windows Credential Manager). Passwords and access tokens are not written to launcher settings.
• Closing and reopening the launcher can restore the session from the credential store without asking for the password again.
• Sign out removes the retained session.

Create your account on the website first — see Accounts. The launcher only signs in existing accounts.

The v0.3.4 rebrand starts a fresh launcher profile. Sign in again, select your existing client folder, and set any custom launcher preferences again. On Linux, select a Steam-installed Proton and allow the launcher to prepare a new managed prefix. Your game files can be reused; the first client check hashes them again.

Client folder

If no client is selected, the managed-release row shows No client selected. Use Select game folder to pick the client root:

• It must contain bin32/archeage.exe (and related game data such as game/db/compact.sqlite3).
• Cancelling the picker changes nothing.
• A rejected path keeps the previously saved root.

On Linux, also choose a Steam-installed Proton under Installation settings (Install on Linux).

Play, Update, Repair, Unsupported

Managed client content is classified against the latest signed release:

Disposition	Meaning
Play	Client matches the current signed release; you can launch.
Update	Controlled base or an older exact signed release; apply the latest content.
Repair	Safely recoverable mismatch; repair toward the current release.
Unsupported	Unknown or unsafe state; primary actions stay disabled.

• Play requests a short-lived, single-use play ticket, then starts the game.
• Update and Repair share the managed installer and show whole-operation progress (0–100).
• Verify all files discards the local archive receipt and forces a full archive hash.

While Update or Repair runs, the button stays labeled Updating or Repairing. Play shows Launching.

Signed client content keeps the native poem splash and skips the 24-second login cinema before the server list.

Launcher self-update

Since launcher v0.3.0, the app checks for a signed launcher update at startup. You can also start a check from Settings.

• The first v0.3.0 (or later baseline) install is manual.
• Later versions can use Update and restart.
• The launcher verifies a signed manifest and archive hash before the updater helper runs.
• The manifest signature is an application trust check. It is not a Windows or Linux OS code signature.

Second instance

Starting a second launcher while one is already open exits with an already-running message. It does not revoke or corrupt the retained session.

Maintenance mode

If the Login API or signed manifest check fails, the launcher enters maintenance:

• Play and Update fail closed.
• For transient Login/network outages, the launcher polls status about every 15 seconds.
• A healthy response can refresh a retained session; a signed-out launcher returns to sign-in.

Uninstall

1. Delete the launcher directory (and any desktop entry you created).
2. Settings, the managed Proton prefix (Linux), and logs remain in the platform application-data directory until you remove them yourself.
3. Retained sessions remain in the OS credential store until you clear them there (or sign out while the launcher still runs).

Need help?

Join Discord or email support@archeageorigins.com. See Troubleshooting for what to include in a support email.