Skip to main content
The suite jar is both the plugin suite and its Windows installer. The installer manages the sideloaded plugin file, the version-pinned navigation resources, and the launcher configuration that makes sideloading work.

What the installer manages

The installer SHA-256 checks every download before it replaces a managed file. Navigation data extracts into a staging directory, passes validation, and only then swaps into the active cache. Both distributed jars bundle FlatLaf Extras so the Developer Tools inspectors work out of the box. The manifest carries no dependency Class-Path; the launcher classpath stays exactly two entries: the sideload installer jar, then RuneLite.jar.
Close RuneLite before you enable, repair, or disable. The installer replaces files the running client holds open.

Enable

  1. Close RuneLite.
  2. Run the suite jar.
  3. Select Enable.
  4. Wait until every status row reports ready.
The next RuneLite launch loads the suite from the sideloaded plugins folder.

Repair

Repair repeats the enable-time checks and replaces missing, corrupt, or version-mismatched resources before it re-commits the plugin jar and launcher configuration. Use it after an interrupted download, a damaged cache, or a RuneLite update that reset your launcher configuration.

Disable and recovery

Disable restores the launcher mainClass and classPath captured before the first n3-managed enable. It preserves unrelated launcher settings and leaves downloaded resources in place, so a later re-enable does not re-download anything. The installer refuses to silently replace an unknown custom launcher configuration. It shows you the current main class and classpath and asks for confirmation first.

Runtime fallback

Packet Utils keeps an asynchronous navigation-data downloader as a safety net. If the cache is missing or damaged at runtime, Packet Utils downloads, stages, validates, and installs the data again. A complete installer-prepared cache means no download happens.

Java version

The suite targets Java 11. The RuneLite launcher bundles a compatible runtime, so you do not need a separate JDK to run the suite. Building the suite from source requires a JDK 11 toolchain.