Tags
Creators
Details
All versions
4.1.0
Release
VelocityNavigator 4.1.05 months ago 36
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
Platform
Velocity
Changes
[4.1.0] — 2026-05-26
Added
- Bedrock/Geyser Player Support — Soft-dependency integration with Geyser and Floodgate. Strips advanced Kyori Component formatting (gradients, hover, click actions) to display beautifully on Bedrock clients, and maps authentic Java UUIDs for player affinity tracking.
- First-Run Experience Polish — Beautiful console-printed welcome dashboard on fresh installs. Detects plugin upgrades and showcases a clean release notes changelog digest.
/vn serversDiagnostics Command — Elegant paginated status dashboard for all configured lobbies, complete with player count/max capacity limits, circuit breaker state tracking, and drain statuses.- Configurable Dashboard Colors — Customizable status tags/colors for
/vn serverssupporting full hex, RGB, and MiniMessage styling innavigator.toml. - Typo Auto-Correction & Levenshtein Validation — Dynamic typo detection on config reload/load using Levenshtein distance metrics (e.g., suggesting
"least_players"for"leadt_players"). - Self-Documenting Configuration Keys — The entire
navigator.tomlfile comments are dynamically populated on generation/migration, pointing users to the exact section anchor of the official Wiki page. - Automatic Legacy Color Code Converter — Seamlessly matches and converts all 22 standard
&and§legacy formatting codes to MiniMessage syntax on load (supports"auto"with one-time warnings,"minimessage", or"legacy"modes). - Periodic Update Checker with Backoff — Recurring scheduled task loop to check for updates with exponential backoff on HTTP 429 errors (scales dynamically up to 4 hours).
- Empty Lobby Routing Fallbacks — Customizable degradation strategies (
"disconnect"or"fallback_server") when all primary lobby options are offline or circuit-broken. - Permission Default Change — Standardized
/lobbydefault command permission changed to"none"for immediate out-of-the-box adoption. Existing migration preserves existing admin-defined configurations safely.
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:x0sk0Np9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2rbkszFo:x0sk0Np9"
}

