Tags
Creators
Details
2.1.8
Compatibility
Changes
MC Data Bridge - Release Notes (v2.1.8)
Overview
Version 2.1.8 introduces Item Duplication Exploit Protection, Full Tab Completion, Interactive Inventory & Ender Chest Inspection (invsee & endersee) with read-only and edit modes, Granular Permissions, Database Schema Auto-Migration, and Paper 26.2 Platform Parity.
Key Changes
🛡 Item Duplication Exploit Protection (#30)
- Special Thanks: Special thanks to @AllenLinong for discovering and reporting this critical exploit (#30)!
- Safe Inventory Closure: Open inventory views are automatically closed before player data snapshots are captured during server switches.
- Transfer Lock Enforcement: Cancels item drops, item pickups, container clicks, inventory drags, and block/entity interactions while a player transfer or database save is in progress.
🔍 Interactive Inventory & Ender Chest Inspector (invsee / endersee)
- New Subcommands & Aliases:
/databridge inspect <player> [inventory|enderchest] [--edit]/databridge invsee <player> [--edit]/databridge endersee <player> [--edit]
- Safe View-Only Mode (Default): Inspection GUIs open in read-only mode by default (Left-Click in Overview GUI) to prevent accidental item modifications or unintended edits.
- Interactive Edit Mode (
--editflag or Right-Click): Admins withdatabridge.inspect.editpermission can interactively edit items (Right-Click in Overview GUI or using--editflag) in offline/cross-server player inventories or ender chests directly inside the GUI. - Database Auto-Save: Closing an editable GUI (
InventoryCloseEvent) automatically serializes modified item stacks back to the database so changes apply when the player logs in.
🔑 Granular Permission Nodes
databridge.inspect(ordatabridge.admin): Permission to view player data, inventories, and ender chests in safe read-only mode.databridge.inspect.edit(ordatabridge.admin): Elevated permission required to open interactive edit mode using the--editflag.databridge.admin: Full administrative access to all commands and subcommands.
⌨️ Full Command Tab Completion
- TabExecutor / Brigadier Integration: Added dynamic auto-completion for subcommands (
unlock,inspect,invsee,endersee,migrate), online player names, view types (inventory,enderchest), and the--editflag.
🗄 Database Schema Maintenance & Upgrades
- Auto-Update Schema: Added
auto-update-schemaconfiguration toggle (defaulttrue) to automatically manage table upgrades. - Column Expansion: Upgraded
vanilla_stats_jsoncolumn toLONGTEXT(MySQL/MariaDB) /TEXT(SQLite) to accommodate large recipe books, advancements, and vanilla statistics.
⚡ Paper 26.2 & Dependency Upgrades
- Updated Target API: Compiled and tested against Paper API
26.2and verified on Paper 26.2+ servers. - HikariCP: Upgraded connection pool library to
7.1.0. - Platform Reflection: Retains full backward compatibility for pre-26.2 Spigot/Paper versions via dynamic reflection.
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:zVVJ3ZlZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oYE8njDp:zVVJ3ZlZ"
}

