Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 3 months ago
All versions
1.0.0
Release
2core 1.0.03 months ago 37
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Dedicated servers only
Required content
Changes
Changelog
1.0.0 — Initial Release
Core
- Launch and manage a second Fabric server as a child JVM process from a single mod
- Automatic role detection — both servers use the same JAR (
primary/secondaryvia system property) - Graceful shutdown of the secondary when the primary stops or crashes
- Primary PID monitoring on the secondary side — secondary exits automatically if the primary dies
Process Management
/2core start/stop/restart— control the secondary server in-game or from console/2core status— shows running state, uptime, PID, IPC connection, and current config/2core cmd <command>— send a command to the secondary server's stdin/2core console on|off— toggle live relay of secondary console output to primaryauto_start— optionally start the secondary automatically on primary startupcopy_mode(none/launcher/full) — automatic copying of server files into2core/- Secondary console output always saved to
2core/logs/console.log
Cross-Server Sync
/listother— show online players on the other server, available to all players on both sides- Chat messages, join/leave notifications, and death messages relayed between servers in real time
/2core chatlink on|off— toggle sync without restarting- Fully configurable message formats with
%player%,%message%placeholders and&color codes
Configuration
- Config file auto-created at
2core/2core.propertieson first start /2core set <key> <value>— change any config value live without editing the file- Secondary reads only its relevant config keys — cannot accidentally trigger server launch logic
- IPC port auto-assigned if not set (
ipc_port=0)
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ps3mtuiR:1Vu0AMQC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ps3mtuiR:1Vu0AMQC"
}


