Tags
Creators
Details
All versions
4.2.0
Release
VelocityNavigator 4.2.05 months ago 174
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
Platform
Velocity
Changes
Added
- Embedded Prometheus Exporter & Admin Panel — Built-in HTTP server exposing real-time metrics (
/metrics) on routing distributions, pings, CB statuses, and connection events. - Grafana Dashboard Setup Command —
/vn setup grafanaauto-generates a premium, pre-configured Grafana telemetry dashboard configuration JSON file. - Interactive Selector Menus — Native Bedrock Form GUI (via Geyser/Floodgate integration) and clickable Java Chat Selector Menu with hover tooltips displaying health and latencies.
- Ping-Based Routing Strategy (
latency) — Dynamically select the server with the lowest ping latency to optimize player connections.
Fixed
- Hardened Java and Bedrock lobby menu selections so stale or manually forged choices cannot bypass drain mode, circuit breakers, capacity checks, or configured lobby pools.
- Started the Prometheus exporter during initial proxy boot when enabled, not only after
/vn reload. - Restored true consecutive-failure behavior for the circuit breaker.
- Preserved update notification settings during config rewrites and aligned admin join notifications with
[update_checker].notify_admins. - Accepted the documented
latencyrouting mode in config validation and migration normalization. - Normalized contextual group names consistently so mixed-case mappings continue to route.
- Aligned Maven artifact version, Velocity plugin metadata, and user-facing docs for the 4.2.0 release.
Changed
- Config version bumped to 6. The generated
navigator.tomlhas been completely redesigned with section banners, grouped documentation, and a friendlier layout. Existing configs are auto-migrated and backed up.
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:2rbkszFo:kWhgqO0d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2rbkszFo:kWhgqO0d"
}

