WebsiteClient area

Bedrock

Managed from the Serv-Minecraft client area. 9 answers, updated October 10, 2026.

Minecraft Bedrock Edition box

Key questions 1

Basic settings for a Bedrock server

The Settings tab of a Bedrock server sets the server name, game mode, difficulty, cheats, world name and version. Everything else (player count, etc.) is changed in server.properties.

In the client area

Settings tabOpen
  1. Settings tab: Server name, Game mode, Difficulty, Cheats (commands), World name (world folder loaded at startup), Bedrock version.

    Settings tab of a Bedrock server: version, server name, game mode, difficulty, cheats, world name
    Settings tab of a Bedrock server: version, server name, game mode, difficulty, cheats, world name
  2. Click Save settings, then restart the server from the Console.

  3. For a setting not in this tab (maximum players max-players, view distance, allowlist), edit server.properties in the Files tab: see edit server.properties.

Bedrock has no server-side plugins or mods: extensions come through addons, see prepare an addon.

Tutorials 7

Update the Bedrock version

By default your Bedrock server updates itself: a simple restart installs Mojang's latest version and keeps your worlds and settings.

In the client area

Console tabRestartOpen
  1. Settings tab: check that Bedrock version is set to latest (the default).

  2. Console tab: click Restart. At startup the server compares its version with Mojang's latest release and installs it if needed ([MAJ auto] lines in the console).

  3. Your worlds, server.properties, permissions.json and allowlist.json are kept.

Bedrock players get game updates automatically: restart the server after a Minecraft update so they don't get an "Outdated server" error.

Install a specific Bedrock version

Type the exact number in Settings > Bedrock version, save, then reinstall the server from the same tab.

In the client area

Settings tabBedrock version, then the Reinstall the server sectionOpen
  1. Make a backup (see backups) or copy the worlds folder to your computer.

  2. Settings tab: in Bedrock version, type the full number, for example 1.21.50.07, then click Save settings.

  3. On the same page, Reinstall the server section: start the reinstall. The server downloads the requested version and keeps your worlds and configuration files, even though the panel warning mentions deletion.

  4. Start the server from the Console.

Common errors

  • Going back to a version older than the one that created the world: Bedrock may refuse to load it. Keep a backup before downgrading.

A pinned version no longer updates on its own. To go back to automatic updates, set Bedrock version to latest, save, then restart.

Restrict access with the allowlist

On Bedrock, add each player with the allowlist add command in the console, then turn on allow-list in server.properties.

In the client area

Console tab, then Files tabserver.propertiesOpen
  1. Console tab: type allowlist add XboxGamertag for each allowed player, including yourself (exact Xbox gamertag, in quotes if it contains spaces).

  2. Files tab: open server.properties and set allow-list=true. A new server starts with allow-list=false.

  3. Save, then restart the server.

allowlist list shows the list, allowlist remove XboxGamertag removes a player. The list is stored in allowlist.json. On Minecraft Java, the equivalent is the whitelist.

Turn on the Beta API (experiments)

Some recent addons need the Beta API: stop the server, then turn it on in the Add-ons tab.

In the client area

Add-ons tabBeta APIs (experiments)Open
  1. The world must exist: start the server once if you haven't yet.

  2. Console tab: click Stop. The setting is refused while the server is running.

  3. Add-ons tab: turn on the Beta APIs (experiments) switch. A copy of the original file is kept in the world folder (level.dat.avant-api-beta): turn the switch off to go back.

  4. Start the server.

An addon whose description mentions scripting, API or experimental almost always needs this option: see troubleshoot an addon if it still has no effect.

Prepare an addon before installing it

Rename the addon to .zip, unzip it, then upload the behavior pack to behavior_packs/ and the resource pack to resource_packs/ via SFTP. Your server's Add-ons tab repeats these steps.

Before you start

An archive manager on your computer (built into Windows and macOS).

  1. Download the addon (a .mcaddon or .mcpack file), for example from CurseForge or MCPEDL. Check that it supports your server's version.

  2. Rename the extension to .zip: a .mcaddon or .mcpack is just a regular zip archive, only the extension changes.

  3. Unzip the archive. A .mcaddon usually contains a behavior pack folder and a resource pack folder; a .mcpack contains only one of them.

  4. Connect via SFTP (credentials in Expert Mode, SFTP page) and upload each unzipped folder to the server root:

    arborescence
    > behavior_packs/PackName/> resource_packs/PackName/
  5. Check that manifest.json is directly inside each of these folders, not in an extra subfolder created by unzipping.

  6. Move on to declare the addon in the world so it's actually picked up.

Common errors

  • Uploading the parent folder from the unzip (which itself contains behavior_packs and resource_packs) instead of its contents: the pack ends up one level too deep and isn't detected.
Declare an addon in the world

Copy the uuid and version from each pack's manifest.json into world_behavior_packs.json or world_resource_packs.json, at the root of the world.

Before you start

Having prepared the addon in behavior_packs or resource_packs.

  1. Open the pack's manifest.json (in the editor in the Files tab or via WinSCP) and find, in the header block, the uuid and version fields.

    manifest.json:extrait
    > "header": {>   "uuid": "a1b2c3d4-0000-1111-2222-333333333333",>   "version": [1, 0, 0]> }
  2. At the root of the world (worlds/VotreMonde/), open or create world_behavior_packs.json for a behavior pack, world_resource_packs.json for a resource pack.

  3. Add an entry with the same pack_id (the uuid from the manifest) and the same version:

    world_behavior_packs.json
    [  { "pack_id": "a1b2c3d4-0000-1111-2222-333333333333", "version": [1, 0, 0] }]
  4. For a second addon, add another entry in the same array, without removing the first one:

    world_behavior_packs.json:diff
      [    { "pack_id": "a1b2c3d4-0000-1111-2222-333333333333", "version": [1, 0, 0] },+   { "pack_id": "f5e6d7c8-4444-5555-6666-777777777777", "version": [2, 1, 0] }  ]
  5. Restart the server.

Common errors

  • ! A version that doesn't match the manifest (here [1, 0, 0] written while the manifest says [2, 0, 0]): the pack is ignored with no clear error message.
  • ! A truncated or badly copied pack_id (here an incomplete uuid): the pack isn't recognized.
Play together across Java and Bedrock (crossplay)

A Bedrock server only accepts Bedrock players. Crossplay goes through the Geyser plugin on a Java server: an extra port, requested in the Advanced tab, and two plugins.

Before you start

A Java Paper server.

  1. AdvancedExtra ports tab: click Request a port. It shows up a few minutes later.

  2. Install Geyser and Floodgate (Floodgate lets Bedrock players in without a Java account) from the Plugins tab, then restart.

  3. In plugins/Geyser-Spigot/config.yml, put this port on the port line of the bedrock section, then restart. Bedrock players connect with the server address and this port.

A native Bedrock server never accepts Java players: crossplay only works with a Java server running Geyser.

Common problems 1

An addon doesn't show up or doesn't work

The cause is almost always a mistyped uuid or version, a folder nested too deep, or the Beta API not turned on for an addon that needs it.

  1. Check that the pack_id in world_behavior_packs.json or world_resource_packs.json matches the pack's manifest.json uuid exactly, character for character.

  2. Check that the declared version matches the manifest exactly.

  3. Check that manifest.json is directly inside the pack's folder under behavior_packs or resource_packs, not in a subfolder. See prepare an addon.

  4. If the addon uses scripting or describes itself as experimental, check that the Beta API is turned on.

  5. Restart after each fix: packs don't reload on the fly.

Common errors

  • A behavior pack with no matching resource pack (or the other way around) when the addon needs both: check the contents of the original .mcaddon.
  • Two addons that modify the same block or entity can silently conflict: test one addon at a time if you see unexpected behavior.