Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published last year
Updated 2 weeks ago
All versions
4.263.0.0-rc.1
Beta
Heavy Inventories 4.263.0.0-rc.1 (NeoForge)last month 2
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
4.263.0.0-rc.1
Release candidate for Minecraft 26.3, available for Fabric and NeoForge. Published as Beta on CurseForge and Modrinth, and as a prerelease on GitHub.
Added
- Soaring I-IV for elytra reduces weight-induced lift and rocket penalties by 20% per level, capped at 80%. Obtain enchanted books through the enchanting table and apply them with an anvil.
- Configurable weight penalties for elytra flight. Heavier loads reduce glide lift and rocket thrust, with default maximum reductions of 15% and 25% at 1,000 pounds.
- Flight penalties use actual carried weight, including container contents. Carrying-capacity bonuses do not reduce them. Players can still deploy elytra while overloaded.
- Server operators can configure or disable the penalties under Elytra flight in the server settings screen.
Changed
- Updated to Minecraft 26.3 and its matching loader and Cloth Config dependencies.
- Added weight defaults for poplar logs, leaves and saplings, red shrubs, shelf mushrooms, and explorer maps. Crafted additions, including poplar building blocks, cushions, straw beds, and wool/concrete variants, derive their weights from recipes.
Installation and upgrading
- Requires Minecraft 26.3 and Java 25. Install matching Heavy Inventories versions on clients and servers.
- Use Fabric Loader 0.19.5 with Fabric API 0.160.6+26.3, or NeoForge 26.3.0.3-beta or newer for Minecraft 26.3.
- Requires Cloth Config 26.3.159 for the matching loader. NeoForge dedicated servers can omit it.
- Existing server configurations use the enabled flight defaults. Set
effects.elytra.enabledtofalseto retain vanilla flight behavior. - This begins the
4.263release line. The jars do not support Minecraft 26.2.
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:2xLhHOis:Q7XQHc0i"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2xLhHOis:Q7XQHc0i"
}

