Developers Servers and Realms
Versions and stability
Which pack each plugin feature needs, and what we promise not to break.
Which pack each feature needs
A dedicated server runs the BedrockRelay pack; a Realm runs the Realm pack. Owners update either from the dashboard, which says when a plugin needs a newer one.
| Feature | Dedicated server | Realm |
|---|---|---|
Plugins, commands, options, run(), the helpers | v0.3.0 | v1.2.0 |
choices, public, confirm, board | v0.4.0 | v1.2.0 |
context.linkedPlayer, context.live | v0.4.0 | v1.2.0 |
posts, drawn pictures | v0.4.0 | v1.2.0 |
postKinds | v0.4.2 | v1.2.0 |
| Script events | every version | every version |
An older pack ignores what it doesn't know rather than failing: a choices option arrives as plain text, and every kind of post goes. Set minPackVersion (in plugin.json, or in a private plugin's definition) to the newest feature you rely on, and the dashboard asks for a pack update before installing it.
Stability
The plugin definition, the run() contract, the helpers in relay/api.js and the three script events are a published contract. We won't change them in a way that breaks an existing plugin or addon without announcing it in this guide first.
New fields are added alongside the old ones. Since pack v0.4.0 most need no pack update at all, because the pack passes on everything a plugin declares and our service decides what it understands.
Running a Minecraft world rather than building for one? The help covers everything from setup to troubleshooting.
Read the help