foreverworld-resourcepack VS docker-minecraft-bedrock-server

the foreverworld-resourcepack has also been updated to include 1.17 assets (frozen hearts) https://github.com/skztr/foreverworld-resourcepack/releases/tag/v1.3

In terms of deploying the server I'd recommend https://github.com/itzg/docker-minecraft-bedrock-server, it's pretty much state of the art and uses Docker which is industry standard for deploying instances.

I'm working with my friends on opening a Minecraft server as a docker these days.

Here's the minecraft container you would run: https://github.com/itzg/docker-minecraft-bedrock-server

I have a minecraft bedrock server running on a docker container on my NAS, with port forwarding on my router. https://github.com/itzg/docker-minecraft-bedrock-server

I also run a minecraft server or two from time to time, and three separate instances of Foundry Virtual Tabletop for friends.

I found issue #289 of the docker image which appears to be a similar problem, although it might be an issue with the bedrock server itself, not the docker image.

Note that if you have access to a pc or server which can run Docker, it's quite easy to run a server yourself: https://github.com/itzg/docker-Minecraft-bedrock-server

Personally I just use this docker image, that checks the version and grabs the latest version available on their site, at every launch.

Hello everyone, I just recently start my own MineCraft:BE Server using https://github.com/itzg/docker-minecraft-bedrock-server. My configuraion is like this([email protected], according to https://minecraft.fandom.com/wiki/Server.properties#Bedrock_Edition_3):

If using Docker, I highly recommend using this Minecraft server container by itzg, it's highly configurable and has ARM and ARM64 images in addition to the regular x86-64 (Note: itzg also has a Bedrock server container, but that one doesn't have images for ARM).