Platform

Distribution

Point your Minecraft server at a pack once. From then on everyone who joins gets it — built for the version they are running — and you can see who actually took it.

This is different from testing, which pushes a pack to one player so you can look at it. Distribution is the pack your server runs.

Setting it up#

1. 1

   Serve a pack

   Open Distribution in the sidebar and press Serve a pack, then pick which of your packs the server should hand its players.

2. 2

   Bind your server

   The modal gives you an eight-digit code. On your server, as an operator, with the plugin installed, run:

   /rpai bind 12345678

   Your server remembers this. It picks up everything you publish afterwards on its own, with no restart and nothing to re-upload.

3. 3

   Publish

   Press Publish at the top right, tick the Minecraft versions you want to support, and confirm. Every ticked version is built up front, so a joining player never waits for a zip.

Players get the pack the next time they join.

Versions#

You choose which versions to support; we never guess. Each one is built as its own download with its own hash, because a Minecraft server hands the client a URL and a hash, so one file cannot quietly serve everybody.

Which build each player gets is decided on your server, as they join:

• On an ordinary server, every player is on the server's own version, so there is one answer.
• With ViaVersion installed, players can be on many different versions at once, and each one is matched individually.
• Bedrock players connecting through Geyser get the Bedrock build, if your pack has models in it.

Someone joining on a version you haven't ticked is served nothing, and recorded — they show up in the version breakdown so you can tick that version and publish, rather than never hearing about it.

Publishing again#

There is one live release. Publishing again builds your ticked versions fresh and replaces it, and the previous build is removed.

Your pack in the editor is deliberately not what your players get. Publishing is an explicit act, so saving a half-finished edit can never push a broken pack onto a live server.

What you can see#

The Distribution page shows serves per day over the last 30, which versions your players are on, every recent join, and each bound server with the last time it served somebody.

Declined is worth watching. A player's client can refuse a server pack without ever showing them a prompt — it's a per-server setting called Server Resource Packs, and most people have never heard of it. A high decline rate is usually that, not people saying no.

Player names and UUIDs come from your own server. If it runs in offline mode those UUIDs can be forged, so unique-player counts there are an estimate.

Limits#

Every plan can distribute. The free plan serves up to 50 unique players a month, counted across the packs you own; every paid plan serves unlimited players. Your current usage is on the Distribution page.