Platform
Distribution
Distribution is how you give your pack to every player on your own server. You connect your server to a pack once. After that, whenever you press Publish in Studio, everyone who joins gets the new version automatically. Studio also shows you who downloaded it.
It's the step after testing. Sync (see The plugin) sends a pack to just you while you build it. Distribution is the finished pack your server runs for everybody.
You need RP Engine, our free plugin, on the server.
Setting it up#
- 1
Choose the pack
In Studio, open Distribution in the sidebar, press Serve a pack, and choose the pack your server should hand its players.
- 2
Connect your server
You get an eight-digit code, good for 30 minutes. On your server, as an operator (or anyone with the
rpengine.distributepermission), run:/rp distribute 12345678This is called binding the server to the pack. The server remembers it, so you do it once. A pack can be bound to up to 10 servers.
- 3
Publish
Press Publish, tick the Minecraft versions your players use, and confirm. Each ticked version is built straight away, so nobody waits when they join.
Players get the pack the next time they join. No restart is needed.
Updating the pack#
Change the pack in Studio as usual, then press New release on its Distribution page. It builds your ticked versions again and replaces what players get. There's one live release at a time, and no rollback.
Players only ever get what you last published, not what's in the editor, so a half-finished edit never reaches your server.
Which Minecraft versions to tick#
Each version you tick is a separate build of the pack.
- On an ordinary server, everybody is on the server's version, so tick that.
- With ViaVersion, players can join on other versions. Tick each one you want to support, and see Players on many versions below.
- Bedrock players joining through Geyser get a Bedrock version of the pack automatically, if the pack has anything Bedrock can show. See Bedrock and Geyser.
The version breakdown on the Distribution page shows which versions your players are really on, so you can tick any you missed and publish again.
Brand-new Minecraft versions
A version we haven't added yet shows as unrecognised. Those players start getting the pack once we add it; you don't need to do anything.
Seeing who got it#
The Distribution page shows downloads per day for the last 30 days, which versions your players are on, recent joins, and each bound server with the last time it served somebody.
Watch the Declined count. Players can turn off server resource packs in their server list settings (Server Resource Packs) and never see a prompt, and most don't know the setting is there. A high decline count is usually that.
Player names and UUIDs come from your server. On an offline-mode server they can be faked, so unique-player counts there are an estimate.
Pausing and stopping#
The Manage card at the bottom of the Distribution page has two buttons:
- Pause stops your servers handing out the pack, and keeps everything else. Resume starts again with no rebuild.
- Stop distributing deletes the release, disconnects every server and clears the numbers. The pack itself is kept, and you can start again from Serve a pack. Only the pack's owner can do this.
To rename a bound server, press the pencil beside its name. To disconnect just one, press the bin beside it.
On your server#
When you publish, RP Engine puts the pack in its content folder (the folder of
packs it builds and sends to players) as
plugins/RPEngine/content/studio-<pack>/. It's merged with anything else you
have there, so players still download one pack. /rp shaders, /rp dialogs
and the rest list what's in it.
Each new release replaces that folder within a minute. Make changes in Studio,
not in the folder: files you edit there by hand are copied to
plugins/RPEngine/studio-backups/ and then replaced.
| Command | What happens |
|---|---|
/rp distribute off | Disconnects the server and removes the folder |
/rp distribute off --keep | Disconnects the server and keeps the folder as your own content, no longer updated |
This needs RP Engine 0.2.49 or newer. Older versions send the published pack to each player separately instead of writing the folder.
Players on many versions#
The folder holds the build for your server's own version (or the nearest one
below it that you published), and that's what every Java player gets. If your
players join on many versions through ViaVersion, set
distribution.mode: cdn in RP Engine's config:
each player is then sent the build for their own version. A player on a version you
didn't tick is then sent nothing, and shows up in the version breakdown.
Shader objects or Dialogs not showing? They need RP Engine 0.2.38 or newer and a release published on or after 29 October 2026. Press New release if yours is older.
Who can publish#
On your own packs, you. A collaborator can see the Distribution numbers if you give them that section, but publishing needs the Publish to servers permission, which you grant separately. On a team, owners and admins can publish; members can't.
Limits#
Every plan can distribute. Starter serves up to 50 different players a month, counted across all the packs you own. Hobby, Creator, Studio and Team are unlimited. Your current usage is on the Distribution page.