Offline Mode

If the Kraken server can't be reached, the launcher and client fall back to the files saved by your last successful launch. You can keep playing with your sideloaded plugins, including plugins you built yourself with the Kraken API, until the server is back.

Requirements

• At least one normal (online) launch on this computer. Every online launch saves a signed copy of the Kraken bootstrap and the Kraken client and API jars to ~/.runelite/kraken/repository2/ (C:\Users\%username%\.runelite\kraken\repository2\ on Windows). Offline mode starts from those files, so don't delete that folder.
• No RuneLite update since that launch. Offline launches run the same RuneLite update safety check as online ones. See RuneLite updated while offline.
• RuneLite's own servers must be reachable. Offline mode covers outages of the Kraken server only. The launcher still downloads RuneLite's bootstrap from RuneLite, and the game still needs Jagex's servers.

What works offline

Feature	Offline?	Notes
Sideloaded plugins	Yes	They load before sign-in and never need a Kraken account or license.
Your own plugins built on the Kraken API	Yes	The Kraken API saved by your last online launch is loaded, so sideloaded API plugins run as usual.
Kraken plugins	No	They need the server to check your licenses. They load after a refresh once the server is back.
External repository plugins	No	External repositories load after the client signs in to Kraken.
Your Discord sign-in	Kept	The client only signs you out when the server rejects your credentials, never because it couldn't reach the server.

Starting the client during an outage

Start RuneLite the same way you normally do. Nothing needs to be turned on.

1. The launcher tries to download the signed Kraken bootstrap. When that fails, it checks the signature of the copy saved by your last online launch and continues in offline mode. launcher.log (in ~/.runelite/kraken/logs/) shows:

   The Kraken server is unreachable. Starting from the Kraken bootstrap and client saved by an earlier launch; Kraken sign-in and plugins may be unavailable, sideloaded plugins still load.

2. Instead of downloading the Kraken client and API, the launcher uses the copies kept by your last online launch.

3. The RuneLite update safety check runs against the saved bootstrap, then the client starts.

4. The client loads everything in ~/.runelite/kraken/sideloaded-plugins. The Kraken Plugins panel shows a warning: "Can't reach the Kraken server, so Kraken plugins aren't loaded. Sideloaded plugins still work. Press Refresh to try again."

When the server comes back

Press Refresh in the Kraken Plugins panel. The client signs you in with your saved credentials and loads your Kraken and external plugins without a restart. If the server is still down, the warning stays and you can try again later.

Troubleshooting

RuneLite updated while offline

Kraken only runs on RuneLite versions the Kraken team has checked. The saved bootstrap records the RuneLite version it was checked against. If RuneLite has updated since your last online launch, the launcher stops with a message like:

The Kraken Client is currently offline. (injected version mismatch)

(RuneLite update detected) means the same thing. You have two options until the Kraken server is back:

• Tick RuneLite Mode in the launcher to play plain RuneLite. This loads no Kraken or sideloaded plugins.
• Tick Skip Update Check to start Kraken anyway, at your own risk. See launcher options.

"Could not fetch RuneLite or Kraken's bootstrap"

The Kraken Client is currently offline. Could not fetch RuneLite or Kraken's bootstrap.

Either no valid saved bootstrap exists (this computer has never completed an online launch, or repository2 was deleted), or RuneLite's servers can't be reached either. Kraken can't start until the server is back. Use RuneLite Mode to play in the meantime.

My sideloaded plugins don't show up

Check that Skip Side Load is not ticked in the Kraken Plugins configuration and that the jars are in ~/.runelite/kraken/sideloaded-plugins. See sideloaded plugins and accessing logs for more help.