Tags
Creators
Details
1.3
Compatibility
Changes
π Major Update 1.3 - Maintenance, MiniMessage & Smart Fallbacks!
We are thrilled to announce Version 1.3, our biggest and most feature-rich update yet! This release completely overhauls how you manage your proxy, adding highly requested network features and stunning visual upgrades.
π What's New in v1.3:
- Advanced Maintenance Mode: You can now lock down the entire proxy with a single config toggle! Includes a custom maintenance MOTD, specific protocol version text (e.g., "Under Maintenance"), and a whitelist bypass system so your staff (via Nickname or UUID) can still join.
- Full MiniMessage Support: Say goodbye to boring texts! You can now use modern MiniMessage tags (
<gradient:#8a2be2:#da70d6>,<bold>,<red>) alongside legacy color codes (&) in all your MOTDs and kick messages. - Smart Server Fallbacks: If a backend server crashes or restarts, players are no longer kicked from the network! DomainRouter will seamlessly redirect them to a designated fallback server (like your main lobby).
- Isolated Player Counters: Domains can now be configured to display online player counts only from specific backend servers, rather than the entire proxy total.
- Automated Localization System: The plugin now features a brand new
languages/folder. It automatically generates nativeen.ymlandcz.ymltranslation files on startup, making custom messages and full proxy translations easier than ever.
β οΈ Important Update Notes:
- Config Version 7: Because the configuration structure has massively changed, we highly recommend deleting your old
plugins/DomainRouterfolder and letting the plugin generate the fresh v1.3 config and language files. - Ensure your proxy is running a recent Velocity version to fully utilize the new MiniMessage components.
Enjoy the new features, and thank you for using DomainRouter! π
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:8jMPZrtJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iwxJ6OZA:8jMPZrtJ"
}

