Tags
Creators
Details
Bungee-Velo
Compatibility
Changes
š NexCoreBridge 1.0.0 ā Initial Release
The first public release of NexCoreBridge is here!
NexCoreBridge connects NexCore-powered backend servers through Velocity or BungeeCord and extends NexCore with network-wide functionality.
⨠Highlights
- š Velocity and BungeeCord support
- š Cross-server communication between NexCore servers
- š„ Network-wide player presence and player counts
- š¬ Cross-server private messages and
/reply - š”ļø Network-wide StaffChat
- š Cross-server
/tpaand/tpahere - šŖ Server transfers and Server Selector integration
- šØ Network-wide kicks and moderation synchronization
- š Jail synchronization between backend servers
- š§ Maintenance state synchronization
- š° Economy and banking cache synchronization
- š Homes data synchronization
- š¤ Profile and player settings synchronization
- š Punishment synchronization
- šØ Server-switch presentation events
- ā” Automatic backend handshake and reconnect handling
- 𩺠Built-in runtime diagnostics
- š¾ MySQL / MariaDB support for shared network synchronization
š NexCore Integration
NexCoreBridge is designed to work together with NexCore.
Install:
- NexCore.jar on every Spigot/Paper backend server
- NexCoreBridge.jar on your Velocity or BungeeCord proxy
The Bridge handles proxy and network communication while NexCore remains responsible for the actual server features and player data.
š® Compatibility
- Velocity: Supported
- BungeeCord: Supported
- Java: 21+
- Backend: NexCore-powered Spigot/Paper servers
- NexCore backend compatibility: Minecraft 1.20 ā 26.2
ā” Network Reliability
NexCoreBridge includes automatic handshake and connection recovery, request timeouts, server/player presence tracking and shared synchronization support for multi-server environments.
If the shared database temporarily becomes unavailable, the Bridge can fall back to local proxy operation and automatically resume shared synchronization after recovery.
𩺠Diagnostics
Server administrators can inspect the current Bridge status using:
/nexcorebridge status
Aliases:
/ncb status
/ncbridge status
This provides information about connected backends, network players, database connectivity, synchronization and plugin messaging.
š Thank You
Thank you for using the first release of NexCoreBridge!
Feedback, bug reports and suggestions are always appreciated and help improve future versions of the NexCore ecosystem.
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:BVdgzKjn:aSbMcJvl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BVdgzKjn:aSbMcJvl"
}

