Tags
Creators
Details
All versions
4.6.0
Release
VelocityNavigator 4.6.0last week 118
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Velocity
Changes
Added
- Native Java dialogs for lobby selectors, party management, authentication, and backend YAML menus, including NPC menu entry points. New configurations select dialogs on supported clients and Paper backends, with inventory, sign, and chat or command fallbacks.
- Configurable Java UI modes per feature and per YAML menu. Existing selector choices survive migration; Bedrock forms retain their existing behavior.
- Expiring, single-use dialog actions bound to the player and backend, private authentication input forwarding, and visible-password warnings.
- Cross-proxy language propagation across the UI bridge protocol, dynamically synchronizing proxy player locales to backend native Java dialogs and chest menus without requiring duplicate backend localization configuration.
- Dynamic multi-language localization for native Java dialog controls (
Previous,Next,Refresh,Close) supporting all 15 built-in locales and custom language packs. - Inline
{lang:key}placeholder token resolution in backend custom menu YAML configuration for titles, item display names, and lore lines. - Configurable empty slot filler decoration (
fill_empty_slotsandfiller_material) for backend chest menus. - Tests for UI protocol validation, callback/session binding, configuration migration, and pagination independent of chest dimensions; an optional Paper runtime dialog probe.
Fixed
- Reopening an authentication prompt no longer resets the authentication deadline.
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:jwrnKOTV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2rbkszFo:jwrnKOTV"
}

