MultiFabricServer
Experimental Fabric mod exploring integrated multi-server orchestration in one JVM.
No ratings yet
Be the first to rate it.
Community listing page
Community listing page, reviews may not be monitored by the author.
Community voices
Reviews
No reviews yet. Be the first to review this project!
Get it on
Available Platforms
Compatibility
Supported Environments
Runs entirely on the server. Also works in singleplayer.
About
Project Details
For authors
Embed Badge
If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.
Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.
Identifiers
Platform IDs
About
Description
MultiFabricServer
Experimental Fabric server-side mod for running multiple lazy-loaded Minecraft server instances, called clusters, inside one JVM.
Players use /cluster travel <target> or /cluster tp <target> to move between the host and cluster nodes. Nodes start on demand and stop after they have been empty for the configured idle delay. Player list, player count, chat, join/leave messages, advancement messages, and command feedback are shared across running clusters.
Velocity And Standalone Modes
The mod can run without Velocity. In standalone mode, use Minecraft transfer packets and, for a public server, the built-in gateway:
{
"enabled": true,
"gatewayEnabled": true,
"transferHost": "play.example.com",
"gatewayBindHost": "0.0.0.0",
"gatewayBindPort": 25565,
"nodeIdleStopSeconds": 300,
"nodes": [
{
"id": "creative",
"worldName": "creativeworld",
"enabled": true
}
]
}
With this setup, the gateway listens on gatewayBindPort and forwards players to the host or their target lazy cluster. The host Minecraft server must listen on a different port, for example 25566, because the gateway owns the public port.
Velocity can still be used for extended behavior such as preserving chat UI/history during switches. Install the companion Velocity plugin built by this repo and Velocity only needs the host server in velocity.toml.
When seamlessProxySwitchEnabled is enabled, the Fabric mod sends the companion plugin a dynamic backend registration immediately before it sends Velocity's normal Connect plugin message. That lets newly-created clusters work without manually adding each cluster to velocity.toml.
Without the companion Velocity plugin, seamlessProxySwitchEnabled still requires each target cluster name to be registered in Velocity. If Velocity only has the host server configured and you do not want the companion plugin, disable seamlessProxySwitchEnabled and use the transfer/gateway path instead.
Config File
On first server start, this file is generated in the active world root:
multifabricserver-cluster.json
Default content is disabled and safe to edit:
{
"enabled": false,
"gatewayEnabled": false,
"seamlessProxySwitchEnabled": false,
"proxyHostServerName": "host",
"transferHost": "127.0.0.1",
"gatewayBindHost": "0.0.0.0",
"gatewayBindPort": 25565,
"nodeIdleStopSeconds": 300,
"nodes": [
{
"id": "creative",
"worldName": "creativeworld",
"enabled": true
}
]
}
proxyServerName is optional per node. If omitted, seamless Velocity mode falls back to the node id as the Velocity server name.
Velocity Companion Plugin
Build both the Fabric mod and Velocity companion plugin:
./gradlew clean build
Install:
build/libs/multifabricserver-mc26.1-1.0.0.jar -> Fabric server mods/
velocity/build/libs/multifabricserver-velocity-1.0.0.jar -> Velocity plugins/
Then keep only the host backend in velocity.toml, for example:
[servers]
host = "127.0.0.1:25566"
try = ["host"]
Cluster nodes can omit proxyServerName; the node id becomes the dynamic Velocity server name.
Commands
/cluster status/cluster players/cluster reload/cluster enable/cluster enable <node>/cluster disable/cluster disable <node>/cluster start <node>/cluster stop <node>/cluster remove <node>/cluster travel <host|node>/cluster tp <host|node>
Admin commands require command-level GAMEMASTERS.
Development
Build:
./gradlew clean build
Current local test loop:
./gradlew clean build && cp build/libs/multifabricserver-mc26.1-1.0.0.jar server-test/mods/ && cp velocity/build/libs/multifabricserver-velocity-1.0.0.jar server-test/velocity/plugins/ && docker compose -f server-test/docker-compose.yml down && docker compose -f server-test/docker-compose.yml up
Screenshots
Gallery
Versions
Files
Relations
Project Relations
More like this
Similar Mods
Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.
Stats
- Downloads
- <1,000
- Used in
- 0 modpacks
- Followers
- 0
- In stacks
- 0
- Created
- Last synced
-
Oct 9, 2026 2:45 AM UTC
New file updates sync automatically.
When ModDex last fully re-synced this project from CurseForge or Modrinth. A new file release triggers a resync usually within minutes, and every project is also re-synced on a schedule. Edits that don't ship a file, such as a new description or screenshots, are checked every few hours and can appear before this date changes.
How syncing works
External Links
Stats
- Downloads
- <1,000
- Used in
- 0 modpacks
- Followers
- 0
- In stacks
- 0
- Created
- Last synced
-
Oct 9, 2026 2:45 AM UTC
New file updates sync automatically.
When ModDex last fully re-synced this project from CurseForge or Modrinth. A new file release triggers a resync usually within minutes, and every project is also re-synced on a schedule. Edits that don't ship a file, such as a new description or screenshots, are checked every few hours and can appear before this date changes.
How syncing works