Links
Tags
Creators
Details
4.1.0
Compatibility
Changes
Beyond & More 4.1.0 — Wood & Storage Update
Minecraft 26.3 | NeoForge, Forge & Fabric
Wood & Storage
- Expanded wooden storage with 13 wood variants, including Poplar.
- Added matching trapped chests with distinct latch textures and redstone functionality.
- Added new crafting recipes for wood-specific chests and barrels.
- Improved alternative chest crafting recipes.
- Updated Oak Barrel textures to better match vanilla Oak Planks.
Crafting & Recycling
- Expanded armor recycling with material recovery based on item durability.
- Added recipes to recover wooden planks from fences.
- Added additional stonecutting recipes, including Bamboo Planks into Bamboo Slabs.
- Improved existing crafting recipes and removed unnecessary recipe conflicts.
Creative Inventory
- Improved organization of blocks and items.
- Grouped wooden chests, trapped chests, and barrels by wood type.
- Improved item ordering for easier navigation.
Fixes & Improvements
- Fixed missing and invalid block and item models.
- Fixed several missing-texture issues, including pressure plate icons on Fabric.
- Improved chest, trapped chest, and shield rendering compatibility.
- Fixed resource-loading inconsistencies between NeoForge, Forge, and Fabric.
- Improved overall stability and cross-loader consistency.
Localization
- Maintained support for 320 language files.
Compatibility
- Minecraft: 26.3
- NeoForge: 26.3.0.77+
- Forge: 66.0.9+
- Fabric Loader: 0.19.5+ (Fabric API required)
- Java: 25
Thank you for playing Beyond & More!
The upcoming 4.2.0 update will focus on custom creative inventory tabs, improved item organization, and an integrated screenshot gallery.
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:bK2sBOOL:eJ6MmlHq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bK2sBOOL:eJ6MmlHq"
}

