Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 4 years ago
Updated 6 months ago
All versions
1.0.0
Release
Mob Dice Attributes 1.0.06 months ago 24
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
Changelog for Mob Dice Attributes 1.21.1
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[1.0.0] - 2026-04-23
⚙️ Changed
- Platform port: Forge 1.20.1 → NeoForge 1.21.1
- Build system migrated to
net.neoforged.moddev(Gradle plugin) @Modclass now uses constructor injection ofIEventBusandModContainerMod.EventBusSubscriberreplaced with@EventBusSubscriber(bus = Bus.GAME)ForgeConfigSpecreplaced withModConfigSpecthroughoutResourceLocation.fromNamespaceAndPath()API adopted- Attributes API updated:
Attributes.XreturnsHolder<Attribute>;.value()used to reachRangedAttribute - GottschCore package updated:
mod.gottsch.forge.gottschcore.*→mod.gottsch.neo.gottschcore.* - GottschCore artifact updated:
gottschcore→gottschcore-neoforge neoforge.mods.tomlmoved tosrc/main/templates/META-INF/withgenerateModMetadatatask for property substitution- Mod config registered directly via
modContainer.registerConfig()— removed prematureModConfigEventvalidation listener that caused "Cannot get config value before config is loaded" crash isValidEntity()simplified toentity instanceof Monster(Enemy interface removed in 1.21)- Gradle wrapper pinned to 8.12.1 for compatibility with moddev 2.0.78
- All dependencies declared
side = "SERVER"— mod is server-only and clients can connect without it installed
- Build system migrated to
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:i2ECuAXT:pzHhqnvV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:i2ECuAXT:pzHhqnvV"
}

