Tags
Creators
Details
3.1.2
Compatibility
Changes
- Implement MiniMessage formatting across all config.yml messages.
- Add
AllowUnsafeconfig setting for both elevators and teleporters. - Move
WorldguardPermissionandGriefPreventionPermissionmessages to config.yml for customization.
ATTENTION
I have implemented MiniMessage, which means all messages in config.yml must now be converted to the MiniMessage format. This replaces legacy color codes (e.g., &a) with a more powerful and modern syntax (e.g., <green>).
What you need to do
- Update all messages in
config.ymlto use MiniMessage format. - Use the MiniMessage Viewer to test your changes.
Example
Old: &aGoing up!
New: <green>Going up!</green>
For more details, see the Adventure MiniMessage documentation.
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:33qSvL4o:htemxGPY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:33qSvL4o:htemxGPY"
}

