Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 2 weeks ago
All versions
3.3.7
Release
CommandBridge 3.3.72 weeks ago 340
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Velocity
Required content
Any compatible version
Changes
CommandBridge 3.3.7
Added
- Live web script editor via
/cb editor, with changes reviewed and confirmed through/cb editor confirm <code>before saving and reloading scripts. - Guided network setup via
/cb setup, with console confirmation before applying configuration changes. - Setup fills the untouched example script with the actual proxy and backend IDs.
- Backend pairing via
/cbc pair, including a destination preview and console confirmation before saving connection settings. - Backend platform information in the proxy's server inventory.
Security and reliability
- End-to-end encryption for browser editor, setup and pairing messages.
- Signed Redis messages with channel binding, expiry and replay checks.
- Authentication gates for incoming connections and size limits for bridge and relay messages.
- Fixes for reconnect/authentication races, stale command registrations, remote-player permissions and dispatch validation.
- Safer script/configuration and scheduled-task persistence, preserving unreadable task data instead of overwriting it.
- Fixes for oversized time arguments, optional numeric arguments, plugin-message queues and diagnostics redaction.
- Empty command synchronizations no longer warn or report registration failure; partial registrations are reported as failures.
Upgrade notes
- Redis networks: update and restart every connected proxy and backend together. Older unsigned Redis messages are rejected by this version. Keep system clocks within two minutes of each other.
- Back up your configuration and scripts before updating. Keep editor/setup links and pairing codes private, and verify the destination before confirming a backend pairing.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:wIuI4ru2:3gJ5nQvC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wIuI4ru2:3gJ5nQvC"
}

