Tags
Creators
Details
1.1-RELEASE
Compatibility
Changes
🚀 Highly Customizable Config:
The plugin now uses a more organized, nested navigator.toml file with a custom header.
⚙️ Automatic Config Updater:
The plugin will automatically detect and upgrade old configuration files to the new format, preserving user settings.
💬 Optional Command Aliases:
Server owners can now define which command aliases (like /hub or /spawn) they want to use in the config file.
✨ Reconnect to Spawn:
If a player uses a lobby command while already in a lobby, they are now re-connected to that lobby's spawn instead of just seeing a message.
For the next update, you can focus on the suggestions we just discussed:
- Permission Support.
- Fully Customizable Messages.
- Smart Server Selection.
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:SmagQKli"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2rbkszFo:SmagQKli"
}

