Tags
Creators
Details
1.2.5
Compatibility
Changes
Small hotfix update – sorry for the quick second release on the same day.
I found an issue after the previous version and decided to fix it immediately.
Changes in 1.2.5:
- Added new vanilla amount placeholders
- Improved DeluxeMenus support for Vanilla-only sell checks
- Custom ItemCoreX items with the same base material are no longer counted as normal Vanilla items
- This makes Vanilla shop checks much safer when using DeluxeMenus
Example: You can now use DeluxeMenus requirement checks like this:
type: '>=' input: '%itemcorex_vanilla_amount_BONE%' output: 1
This means DeluxeMenus checks the placeholder value from ItemCoreX instead of only checking the material itself.
That way:
- real Vanilla items are counted
- ItemCoreX custom PDC items are ignored
- deny_commands can work again together with safe Vanilla selling
Sorry again for the quick follow-up update, and thanks for the support.
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:aC54VC4N:dlPQjBRj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aC54VC4N:dlPQjBRj"
}

