Skip to main content

ResourcePackManager Setup

This page covers a single-server (standalone) setup. If you run a BungeeCord / Waterfall / Velocity network, follow Proxy networks instead — you install the same ResourcePackManager.jar on the proxy, but it generates its own config and plays a proxy-side role.

ResourcePackManager 2.x ships as a single universal jar. The exact same ResourcePackManager.jar runs on Bukkit/Paper backends and on Velocity / BungeeCord / Waterfall proxies — it auto-detects the platform from the loader it's running under. There are no longer separate resourcepackmanager-velocity-*.jar / resourcepackmanager-bungee-*.jar files and no bundled "proxy extension" to extract and copy anywhere.

  1. Drop ResourcePackManager.jar into your server's plugins/ folder. (This is the same jar you'd use on a Velocity / BungeeCord proxy — there are no separate proxy jars.)
  2. Start the server once so the config, mixer, blueprint, and output folders are generated.
  3. Decide whether you want:
    • self-hosting (default, on)
    • MagmaGuy's free auto-host fallback (default, on)
    • forced client acceptance
    • manual custom packs in the mixer folder
  4. Run /rspm reload after changing config or after adding custom packs manually.

That's it for the happy path. With default settings RSPM will try self-hosting first and fall back to MagmaGuy's CDN automatically if anything looks off.

Core Commands​

  • /rspm setup — opens an in-game GUI setup menu (plugin update status, recommended plugins, an automatic-updates toggle, and an info button with clickable links to the wiki, Discord, and your Nightbreak account token)
  • /rspm reload — rebuilds and re-hosts the merged pack
  • /rspm status — prints a full diagnostic dump: pack state, hosting mode, network key, integrations
  • /rspm itemsadder configure — auto-configures ItemsAdder for RSPM hosting (see below)
  • /rspm itemsadder dismiss — permanently dismisses the ItemsAdder warning for your player UUID
  • /rspm data_compliance_request — downloads all remotely stored data for this server

The root command is /resourcepackmanager, with /rspm as its alias. RSPM also inherits a few shared MagmaCore/Nightbreak subcommands (e.g. /rspm recommendedplugins, /rspm downloadall) that the setup menu links to.

Permissions:

  • /rspm setup requires resourcepackmanager.setup and is player-only (it opens an inventory GUI, so it can't run from console).
  • /rspm reload, /rspm status, /rspm itemsadder <configure|dismiss>, and /rspm data_compliance_request all require resourcepackmanager.*.

ItemsAdder​

The current preferred ItemsAdder path is no longer manual-only.

Use:

/rspm itemsadder configure

That helper updates the relevant ItemsAdder settings, regenerates ItemsAdder's pack, then reloads ResourcePackManager. Specifically it:

  • sets resource-pack.hosting.no-host.enabled: true
  • disables protection_1, protection_2, and protection_3 in resource-pack.zip.protect-file-from-unzip
  • sets resource-pack.zip.compress-json-files: false (RSPM needs uncompressed, parseable model JSON for the mixer and the Bedrock converter)
  • dispatches /iareload, then /iazip
  • reloads ResourcePackManager about 15 seconds later, after ItemsAdder has had time to reload and regenerate

If ItemsAdder is already configured to host its own pack (self-host, external-host, or lobfile), the helper stops and tells you to disable ItemsAdder hosting manually first.

Bedrock / GeyserMC Support​

RSPM automatically converts the merged Java pack into a Bedrock pack for GeyserMC. Conversion handles any plugin's 1.21.4+ items-definition pack — not just FreeMinecraftModels — including 3D held items, custom armor, and modeled equipment.

bedrockConversionEnabled defaults to true, so a fresh install on a server that has GeyserMC will just work.

For a standalone server, conversion fires when any of these is true: Geyser-Spigot is installed on this server, Floodgate is installed on this server, or RSPM detected proxy mode (see Proxy networks).

See Bedrock / Geyser conversion for the full pipeline, output paths, and display-offset tuning.

Verifying the Setup​

Run /rspm status in console or as an op. The output is split into sections:

  • Plugin meta — version + deploy mode (standalone vs network-backend)
  • Java Pack — mixed yes/no, size, SHA1 prefix
  • Bedrock Pack — converted yes/no, mappings present, with diagnostic hints if conversion was skipped
  • Hosting — which delivery path is active (self-hosted / remote / not yet ready), the URL clients will see, resolved external host, auto-detected public IP
  • Proxy deployment — a reminder that the network proxy jar is the same ResourcePackManager.jar; on a network, copy it to the proxy's plugins/ folder
  • Integrations — Floodgate / Geyser-Spigot detection, online player count

If anything looks wrong, see Troubleshooting.

Where to Go Next​