Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 2 months ago
All versions
1.3.1-beta-bungee
Beta
Domain Router 1.3.1-beta-bungee5 months ago 44
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.x
1.6.4
1.6.1β1.6.2
1.5.x
1.4.4β1.4.7
1.4.2
1.3.x
1.2.x
1.1
1.0
Platform
BungeeCord
Changes
π¨ DomainRouter v1.3.1-beta (BungeeCord)
# π DomainRouter v1.3.1-beta (BungeeCord)
Bringing full parity with the Velocity version! This update introduces high-performance data analytics and stability fixes tailored specifically for BungeeCord proxy networks.
### π New Features & Analytics
* **Asynchronous MySQL Logging:** Tracks every successful network entry via the `PostLoginEvent`. Database operations run completely on background threads using the BungeeCord scheduler to eliminate proxy stuttering.
* **Platform Metrics:** Logs player UUIDs, usernames, IP addresses, exact virtual hosts used, and the connection platform (**JAVA** / **BEDROCK**). Perfect for rendering custom web dashboard statistics!
* **Robust Tab-Completer:** Implemented native `TabExecutor` support for the `/domainrouter` command with live permission checks.
### π§ Bug Fixes & Adjustments
* **Fixed Favicon Crash:** Resolved the `no suitable method found for create(java.io.File)` compilation and runtime issue. The plugin now correctly decodes server icons through `ImageIO` into `BufferedImage` memory structures for seamless BungeeCord API compatibility.
* Standardized `bungee.yml` hooks for clean plugin initialization.
### βοΈ Configuration
The `config.yml` structure remains 100% cross-compatible with the Velocity version. Just drop the new configuration block in, hook it up to your MySQL server, and let the background analytics do the magic!
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:iwxJ6OZA:2JrojiRS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iwxJ6OZA:2JrojiRS"
}

