> ## Documentation Index
> Fetch the complete documentation index at: https://runelite.zip/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Install the n3Plugins suite, enable your first plugins, and start an automation run.

This guide takes you from a clean RuneLite install to a running automation plugin. It covers the installer, the two plugins every setup needs, and where to go from there.

## Prerequisites

* Windows with the official [RuneLite](https://runelite.net) launcher installed
* The `n3Plugins-<version>-all.jar` suite artifact
* A plugin suite that is not currently running: close RuneLite before you start

## Install the suite

<Steps>
  <Step title="Run the installer">
    Double-click the suite jar. The installer window opens.

    ```text theme={null}
    java -jar n3Plugins-5.5-all.jar
    ```
  </Step>

  <Step title="Click Enable">
    The installer copies the suite into `.runelite\sideloaded-plugins\`, downloads and verifies the version-pinned navigation resources, and rewrites the launcher configuration for sideloading. Wait for every status row to report ready.

    Every download is SHA-256 checked before it replaces a managed file.
  </Step>

  <Step title="Launch RuneLite">
    Start RuneLite through the launcher as usual. The suite loads from the sideloaded plugins folder.
  </Step>

  <Step title="Enable Packet Utils">
    Open the RuneLite plugin list, search for **Packet Utils**, and enable it. It is the shared runtime every n3 plugin depends on: revision validation, menu dispatch, walker ticking, action pacing, and input locking.

    It ships enabled by default. If you disabled it previously, re-enable it before anything else.
  </Step>

  <Step title="Enable a feature plugin">
    Enable any n3 plugin from the list, for example **Power Skiller** or **Gemstone Crab Killer**. Each plugin adds a tab to the shared n3 sidebar where you configure and start it.
  </Step>
</Steps>

<Warning>
  Close RuneLite before you enable, repair, or disable the suite. The installer replaces files the running client holds open.
</Warning>

<Info>
  The installer's **Repair** option re-runs every check and replaces missing or corrupt resources. **Disable** restores the launcher configuration that existed before the first n3-managed enable and leaves downloaded resources in place for a later re-enable.
</Info>

## Verify it works

1. Open the shared n3 sidebar in RuneLite.
2. Open the **Suite status** tab. It reports revision health, walker state, and pacer status.
3. Start a plugin from its own tab and watch its overlay and status lines react.

## Next steps

* Learn the tick loop and the rules plugins follow in [Core concepts](/getting-started/core-concepts).
* Configure account profiles, proxies, and auto-login in [Profiles](/getting-started/profiles).
* Browse what each plugin does in [Plugin guides](/plugins/overview).

<Tip>
  If a plugin stays blocked, check Suite status first. Most blocked states come from a revision mismatch, a disabled Packet Utils runtime, or an unreachable navigation cache, and the status tab names the exact reason.
</Tip>