Tags
Creators
Details
Licensed Apache-2.0
Published 2 years ago
Updated 2 days ago
All versions
1.11.2+neoforge-1.21.1
Release
1.11.2 neoforge 1.21.12 days ago 21
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Mob Loot Bags — Patch Notes
1.11.2
Fixes
- Minecraft 26.1.2 startup crash — block/item registration now sets registry IDs (
Properties.setId) on Fabric and NeoForge, fixingBlock id not set/Item id not set/ unboundResourceKeycrashes. - 26.1.2 datapacks — recipes under
data/.../recipe/with 26.1 ingredient/idresult schema; pickaxe mineable tag undertags/block/. - Opener / recycler break parity (26.1.2) — container contents (and recycler stored XP) drop via block-entity
preRemoveSideEffects, matching vanilla container behavior.
Credits
- Registry ID fix approach contributed by Sami (
0x-sami) in PR #9 (completed for Fabric + common in this release).
Version note
- All workspaces ship as 1.11.2. Code fixes above apply to the 26.1.2 workspace; 1.20.1 and 1.21.1 are version-aligned releases with no registry API change required.
1.11.1
Fixes
- Timed loot bags now open the configured
timed_lt_nameloot table (mob_loot_bags:time_warped_loot_tableby default) instead of running cursed-bag random commands (warden summons, trial spawners, etc.). - Blacklist / whitelist
enableflag is preserved across restarts; config load no longer rewrites user files with default values on every launch. - Mob drops credit the attacking player for projectile kills (bows, tridents, etc.), not only direct melee hits.
- Added
timed_lt_nameto defaultloot_tables.jsonfor configurable timed bag rewards.
Issues addressed
- #7 — Timed bag only spawning wardens
- #6 — blacklist.json
enableresets to false - #4 — Bags not dropping (NeoForge 1.21.1 / projectile attribution)
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:uEntVAnd:PR2W6eWC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uEntVAnd:PR2W6eWC"
}

