官方免责声明

• 这是 Mojang 尚未完成的服务器版本（预览版）
• 可能有严重的 bug
• Mojang 随时都可以停止支持它

平台

Linux：

• 将压缩文件解压到一个空文件夹中
• 使用以下命令启动服务器

setsid ./bedrock_server

Windows

• 将压缩文件解压到一个空文件夹中
• 运行 bedrock_server.exe 文件启动服务器
• 在某些系统上，当您希望使用运行在同一台计算机上的客户端连接到服务器时，服务器正在运行，您将需要去除 Minecraft 客户端 的 UWP 环回限制

CheckNetIsolation.exe LoopbackExempt –a –p=S-1-15-2-1958404141-86561845-1752920682-3514627264-368642714-62675701-733520436

配置文件

• 服务器将读取 server.properties 作为服务器的配置文件
• 其中一些选项仅在创建新世界时读取
• 其他一些选项在每次启动时都会读取
• 该文件应包含一个列表，其中的键和值以等号分隔，每行一个
• 可以使用以下选项。 如果值为括号中的数字，则可以使用该数字代替文本值

文件夹

• 解压后，您将看到一些文件夹和二进制可执行文件
• 第一次启动服务器时，将创建一堆新（空）文件夹
• 您应该关注的文件夹如下：

白名单

• 如果在 server.properties 将 white-list 设置为 true
• 服务器将只允许 whitelist.json 列表中的玩家进入服务器
• 允许玩家进入服务器必须知道玩家的 游戏昵称（即登录 Xbox 后显示的名字）
• 添加一名玩家进入白名单只需要执行命令 whitelist add <游戏昵称>
• 从白名单中删除一名玩家只需要执行命令 whitelist remove <游戏昵称>
• 每次修改白名单后都必须执行命令 whitelist reload 才会刷新白名单
• whitelist.json 中参数如下

• whitelist.json 文件示例：

[
    {
        "ignoresPlayerLimit": false,
        "name": "MyPlayer"
    },
    {
        "ignoresPlayerLimit": false,
        "name": "AnotherPlayer",
        "xuid": "274817248"
    }
]

权限组

• 可以通过 permissions.json 给特定玩家分配特定的权限
• 分配权限的玩家必须具有是登录Xbox账号进入服务器的玩家（因为需要他们的 xuid）
• 可以使用 permissions list 命令罗列出所有拥有特殊权限的玩家
• permissions.json 文件示例：

[
    {
        "permission": "operator",
        "xuid": "451298348"
    },
    {
        "permission": "member",
        "xuid": "52819329"
    },
    {
        "permission": "visitor",
        "xuid": "234114123"
    }
]

Commands
You can issue commands to the server by typing in the console. The following commands are available. < > means a parameter is required, [ ] means it's optional and | denotes different allowed values. Strings can be enclosed in double quotes, ", if they contain spaces.

Command syntax Description
kick <player name or xuid> <reason> Immediately kicks a player. The reason will be shown on the kicked players screen.
stop Shuts down the server gracefully.
save <hold | resume | query> Used to make atomic backups while the server is running. See the backup section for more information.
whitelist <on | off | list | reload>
on and off turns the whitelist on and off. Note that this does not change the value in the server.properties file!

list prints the current whitelist used by the server

reload makes the server reload the whitelist from the file.

See the Whitelist section for more information.

whitelist <add | remove> <name> Adds or removes a player from the whitelist file. The name parameter should be the Xbox Gamertag of the player you want to add or remove. You don't need to specify a XUID here, it will be resolved the first time the player connects.

See the Whitelist section for more information.
permissions <list | reload>
list prints the current used operator list.

reload makes the server reload the operator list from the ops file.

See the Permissions section for more information.

op <player>
Promote a player to operator. This will also persist in permissions.json if the player is authenticated to XBL. If permissions.json is missing it will be created. If the player is not connected to XBL, the player is promoted for the current server session and it will not be persisted on disk. Defualt server permission level will be assigned to the player after a server restart.

deop <player>
Demote a player to member. This will also persist in permissions.json if the player is authenticated to XBL. If permissions.json is missing it will be created.

changesetting <setting> <value> Changes a server setting without having to restart the server. Currently only two settings are supported to be changed, allow-cheats (true or false) and difficulty (0, peaceful, 1, easy, 2, normal, 3 or hard). They do not modify the value that's specified in server.properties.
Backups
The server supports taking backups of the world files while the server is running. It's not particularly friendly for taking manual backups, but works better when automated. The backup (from the servers perspective) consists of three commands.

Command Description
save hold This will ask the server to prepare for a backup. It’s asynchronous and will return immediately.
save query After calling save hold you should call this command repeatedly to see if the preparation has finished. When it returns a success it will return a file list (with lengths for each file) of the files you need to copy. The server will not pause while this is happening, so some files can be modified while the backup is taking place. As long as you only copy the files in the given file list and truncate the copied files to the specified lengths, then the backup should be valid.
save resume When you’re finished with copying the files you should call this to tell the server that it’s okay to remove old files again.