SuspenseDeveloper Documentation

Suspense developer documentation

Build Suspense plugins without the client source.

Download a standalone IntelliJ and Gradle starter, compile only against the approved public SDK, and hot reload the resulting plugin JAR in the installed Suspense client.

Download plugin starter IDE setup API reference

Standalone development kit

Set up IntelliJ in four steps

The starter produces the same external-plugin JAR format used by the Marketplace, so local testing and review use the same artifact structure.

1. Extract and open

Extract the starter ZIP, open its folder in IntelliJ, and import it as a Gradle project using JDK 11.

2. Rename the starter

Set the plugin ID, display name, version, author, Java package, entry class, and descriptor metadata.

3. Enable local plugins

In Suspense Core settings, enable Plugin development → Enable development plugins.

4. Build and reload

Run installDevPlugin. Suspense watches %USERPROFILE%\.runelite\suspense-dev-plugins and reloads the newest JAR automatically.

SDK Public compile surface only RuneLite API types, plugin lifecycle contracts, configuration annotations, Suspense client API DTOs, automation contracts, and walker contracts. libs/Suspense-Plugin-SDK.jar
BUILD Production-shaped plugin JAR The build verifies that RuneLite, Suspense, Guice, and injection runtime classes were not bundled into the submitted plugin. .\gradlew.bat installDevPlugin
RUNTIME Installed Suspense is the test client The local development loader safely stops the previous plugin instance, closes its class loader, and starts the newest build. ~/.runelite/suspense-dev-plugins
Download IntelliJ starter ZIP Download SDK JAR only Download API source classes

Choose the correct API

Match the API area to the job

Most plugins begin with the Client API. Add the automation runtime for multi-step work and the walker when the player must travel.

How to read Suspense return typesCompletableFuture, Optional, snapshots, interaction results, lists, and coordinates
CompletableFuture<T>

The operation completes asynchronously. Chain work with thenApply, thenCompose, or thenAccept rather than blocking the client thread.

Optional<T>

The requested object may not currently exist. Handle the empty case instead of calling get() without checking.

*Snapshot

A read-only point-in-time view. Request a new snapshot before making a decision that depends on current state.

SuspenseInteractionResult

The outcome of a requested action. Check it before assuming a click, withdrawal, selection, or interaction succeeded.

List<T>

A collection of current matches. An empty list is valid and simply means nothing matched at that moment.

WorldPoint

A world coordinate with X, Y, and plane. The correct plane matters for objects, ground items, and walking destinations.

Minimal example

Read inventory state without blocking

Check for coins and continue only after the asynchronous result is available.

SuspenseClientApi api = /* injected API */;

api.inventoryContains(995)
    .thenAccept(hasCoins -> {
        if (hasCoins) {
            // Continue the workflow.
        }
    });

Searchable Java reference

Types and callable methods

The default view shows callable Client API types. Select another area or disable the callable-method filter to inspect snapshots, requests, results, and enums.