LiteLoader Bedrock Dedicated Server Hosting

What is LiteLoaderBDS and what is its status today?

LiteLoaderBDS was a loader that added plugin support to Mojang's Bedrock Dedicated Server. The LiteLDev team built it, it hooked into the Windows build of BDS, and people ran it on Linux through Wine. Its strongest feature was language flexibility: alongside C++ plugins, the LiteLoader Script Engine (LLSE) let people write plugins in JavaScript, Lua, Python and Node.js. Plenty of Bedrock communities built their land claims, economies and menu systems on it.

The situation today is clear. The project was archived on GitHub on November 1, 2024, and is now read-only. The developers announced that LiteLoaderBDS had reached end of life, that it is no longer maintained or supported, and pointed everyone to its successor, LeviLamina. LiteLoaderBDS will not be updated for new Minecraft versions and will not receive bug fixes. We recommend choosing the plans on this page with that in mind and for a specific purpose.

Can current Bedrock clients join a LiteLoaderBDS server?

In practice, no. Bedrock only lets a client join a server running exactly the same protocol version. Each LiteLoaderBDS release is tied to a particular BDS version, and its final releases targeted the 1.20 series. Today's phone, tablet and console clients are on far newer versions, so they get a version mismatch error when they try to connect.

Only players who can keep their client on exactly the same old version can join. On consoles and on iOS installs from the App Store, going back to an older client is not realistically possible, so do not count on console or iPhone players at all. Once your server is installed, the console's startup output shows which BDS version is running, and your players need a client that matches it. If you are building a public community aimed at players on current versions, LeviLamina or Vanilla Bedrock is the right choice.

Who should still run LiteLoaderBDS?

Despite its limits, there are a few legitimate reasons to run it. The first is preservation: you might want to open a long-running server's world, land claims and economy data exactly as they were before it shut down, save them, grab screenshots or give the community one last tour.

The second is data recovery. Many LLSE plugins stored their data in JSON, YAML or SQLite files. Exporting that data with the plugin's own commands, or reading it in the right format, is much easier when the plugin is actually running.

The third is testing and migration prep. Developers who want to document exactly how old plugins behaved before moving to LeviLamina, and compare them against LegacyScriptEngine, benefit from a reference setup. Finally, a closed group that deliberately keeps its clients on the old version can use it too, though we advise against exposing unmaintained software as a public server.

How do you migrate from LiteLoaderBDS to LeviLamina?

Start with a complete backup: the world folder, server.properties, the allowlist and all plugin data inside the plugins folder, together in one archive. Bedrock worlds upgrade cleanly to newer versions, so you can open the same world on a current LeviLamina server, but there is no way back, so keep the original copy.

Plugins take different paths depending on their language. On LeviLamina, LegacyScriptEngine can often run LLSE plugins written in JavaScript, Lua, Python or Node.js, and it converts their manifests on its own once they sit in the plugins folder. C++ plugins must be rewritten or rebuilt against LeviLamina's new API, so check whether a current LeviLamina release of each one exists. Scripts calling removed APIs can throw errors, so test plugins one at a time and compare them with the behavior on the old server. When you are ready, our support team can talk you through setting up LeviLamina step by step.

Which plan is enough, and what resources does it need?

An old LiteLoaderBDS setup usually serves a small group or a test, so it rarely needs a big plan. BDS itself is a compiled native program with moderate memory use, while the LLSE script engines, particularly Node.js and Python, and the Wine layer add some overhead on top.

For an archive visit, data recovery or plugin testing, Bronze 4GB is enough in most cases. If you are opening a large, long-played world with many plugins, Silver 6GB is more comfortable. An old-version group of more than 20 players is unusual, but if you need it, Gold 8GB is the sensible ceiling. Larger plans are generally wasted on this software: current clients cannot connect, so there is no large player base to serve. If your community is going to keep growing, that budget is better spent on LeviLamina.