Tags
Creators
Details
2.1.9
Compatibility
Changes
MC Data Bridge - Release Notes (v2.1.9)
Overview
Version 2.1.9 delivers Proxy Subcommand Auto-Forwarding across proxy platforms (Velocity, BungeeCord, and Waterfall) and Real-Time Online Player Live Inventory Sync & Active Edit Lock Protection.
Key Changes
🔄 Proxy Subcommand Auto-Forwarding (#34)
- Proxy-to-Backend Command Routing: Non-
unlocksubcommands (e.g./databridgeor/dbfollowed byinvsee,endersee,inspect,reload,sync,migrate) executed by players on proxy servers (Velocity, BungeeCord, and Waterfall) are now automatically routed downstream to their connected backend Paper/Spigot server without requiring explicit namespace prefixes (/mc-data-bridge:databridge). - Namespace Interception Fix: Fixes command hijack and usage rejection issues when running shorthand
/databridgesubcommands across proxy setups.
âš¡ Online Player Live Inventory Sync & Active Edit Lock (#31, #32)
- Real-Time In-Memory Update: Edits made to an online player's inventory or ender chest via
/databridge invsee --editor/databridge endersee --editnow immediately update the target player's live, in-memory inventory on their active server instance. - Cross-Server Live Sync: Dispatches a
LiveInventorySyncmessage over themc-data-bridge:mainplugin channel when editing online players on other servers across the proxy network, forcing an instant live memory reload without requiring player relog. - Pre-Fetch Memory Snapshot: Opening an inspection GUI for a locally online player automatically snapshots their live memory state first, preventing recent item pickups or drops from being overwritten by older database data.
- Active Edit Lock Protection: Protects online target players from inventory desync or duplicate item exploits while an admin is actively modifying their inventory in an edit GUI.
For installation instructions and configuration details, please refer to the README.md and config.yml.
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:oYE8njDp:7vCmpybL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oYE8njDp:7vCmpybL"
}

