Kraken Plugins

Appearance

Troubleshooting ​

Short fixes for the problems the client and launcher are known to hit. If none of these apply, grab your logs and contact support.

The Kraken icon is missing from the sidebar ​

Open RuneLite's plugin list and enable the plugin called Kraken Plugins. If it is not in the list at all, the launcher did not load Kraken: check ~/.runelite/kraken/logs/launcher.log and make sure RuneLite Mode is not ticked in the Kraken launcher window.

"Update check failed" when starting ​

Kraken checks that the RuneLite version you have matches the one Kraken was last verified against. After a RuneLite update this check fails until Kraken developers have reviewed the new client. Wait for the update announcement in Discord, or tick Skip Update Check in the launcher window at your own risk. See launcher options.

The launcher says to re-run the installer ​

On Java 16 or newer the launcher needs the --add-opens/--add-exports entries the installer writes into RuneLite's config.json. If you installed manually or an older installer wrote the file, run the installer again or add the entries shown in manual installation.

Discord sign in never completes ​

The sign in returns to the client through http://localhost:8080. If another program is using port 8080 the browser shows an error instead of returning; close that program and click Sign in with Discord again. The request also expires after two minutes. See client signup.

My plugins do not show up ​

  • Sign in to the client with the same Discord account you bought the plugins with. See account linking.
  • Every purchased plugin needs its license key pasted into its configuration. A plugin showing Invalid License Key or Expired is not started.
  • Run /mine in Discord to confirm the license is still active.

A sideloaded plugin does not load ​

  • Make sure Skip Side Load is not ticked in the Kraken Plugins configuration.
  • The JAR must be in ~/.runelite/kraken/sideloaded-plugins and must bundle its own dependencies. See sideloaded plugins.
  • Look for the plugin's name in client.log; a stack trace there usually names the missing class.

An external repository does not load ​

The client fetches the repository's manifest with a 30 second timeout and rejects any plugin whose SHA-256 does not match the manifest. Make sure Skip External Load is not ticked, then remove and re-add the repository. See external plugins.

The proxy is not being used ​

Check the format rules in proxies. A proxy string the launcher cannot parse is ignored without an error in the window; the warning is written to launcher.log. The Kraken Plugins plugin header shows the proxy the client is actually using.

Windows SmartScreen blocks the installer ​

KrakenInstaller.exe is not code signed. Click More info and then Run anyway. See downloading the client.

"RuneLite (configure)" will not save ​

The Kraken installer marks RuneLite's settings.json read-only. Clear the read-only attribute on %localappdata%\RuneLite\settings.json (right-click → Properties → untick Read-only), make your change, and start RuneLite again.

RuneLite flags like --safe-mode do nothing ​

The Kraken launcher discards arguments passed to RuneLite.exe (other than its own, listed in launcher options). Enter RuneLite flags in the Client Arguments field of "RuneLite (configure)" instead.