Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 3 hours ago
All versions
6.0.0-b482-release
Release
Resource Data Pack Loader 6.0.0-b482-release3 hours ago 40
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
Changelog:
- Mixin cleanup pass
- Vanilla client checks logging
- Cross-feature gap fixes
- Leaf and plant render defaults
- Earned hearts and diet extras
- Downed state and revive
- Custom enchantments
- Carrying blocks and mobs
- Food variety
- Sleeping bags
- Vein mining
- Trade conditions and score prices
- Dialogue colors and history
- Villager dialog
- Item affixes and gem sockets
- HOWTO weather table padding
- Pack rain texture crash
- Portway travel blocks
- Entity tank bucket fix
- Anvil and enchanting costs
- Structure map dungeons
- Pack clash rules
- Exposure immunity rules
- Stars behind fixed sky bodies
- Sorted pack file listing
- Ocean fluid key
- Conditional pack lang files
- Fix sky color keys
- HOWTO examples
- Missed HOWTO sections
- Weapon reach and combos
- Stage locks
- More card triggers
- More Baubles/Curios options
- Fix 26.x link
- Boss phases
- Exposure sources
- Mob ranks
- Seasons cycle
- Village plot signs
- Setup item lookups
- Boss bars options
- Environment switches
- Interface naming cleanup
- Stars behind sun
- Work order rewards
- HOWTO doubled tables
- Raid start commands
- Locate command additions
- Crop harvest
- Spawn conditions
- Pack tooltips
- Dice item and roll card trigger
- 26.3 on NeoForge 26.3.0.95
- Gate team and score options
- Raid points and loot
- Gate unlocks by team and score, and team gate scope
- Time and sapling fortune fix
- Howto table updates
- 26.1.2 fix large world reload
- Biome craters keys
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:D4OJ0QwC:NiVVNrmo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:D4OJ0QwC:NiVVNrmo"
}

