Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated last month
All versions
6.0.7
Release
Major bugfixes2 years ago 303
Compatibility
Minecraft: Java Edition
1.20.6
1.20
1.19
1.18
1.17
1.16
1.15
1.14
1.13
1.12
1.11
1.10
1.9
1.8
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added:
Permission-Switchtrigger.- Adding this trigger to a custom item will allow it to be given at the moment the permission is granted to the user.
- If the permission is revoked the custom item will be automatically removed.
Fixed:
- 1.17.0 - 1.17.1 bug with not being able to join the server when defining a custom book item.
- JSON Books being non-functional for Legacy Minecraft versions 1.8 - 1.20.4.
- Menu would break if items are empty or null in the items.yml.
- Menu region-egress trigger being broken.
- Was incorrectly referenced as region-engress instead of region-egress.
- Menu disable triggers not removing all triggers.
- A few new trigger values were missing instead, the list is just cleared rather than being checked.
- Legacy Minecraft animation spam when updating the Player Inventory.
- Even if no action was taken to the player inventory a force update was incorrectly triggered.
- Legacy PotionMeta bug.
- ItemMeta was incorrectly specified in the reflection.
- Another VirusTotal false-flag.
- This is very unlikely to happen again, the method has been entirely rewritten.
commands-costbug.- Users with a balance in the negatives (less than zero) would not be allowed to execute commands regardless of
commands-costbeing specified. commands-costbeing set to zero or not defined now allows the commands to execute properly.
- Users with a balance in the negatives (less than zero) would not be allowed to execute commands regardless of
Changed:
- Dump URL is now interactable.
- Easier to copy the URL.
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:8OiYKudu:pL7vjuIj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8OiYKudu:pL7vjuIj"
}

