5.0.0
Compatibility
Required content
Changes
Simple Backpacks 5.0.0 for Minecraft 26.1.2
Fabric and NeoForge. Grab simplebackpacks-fabric-26.1.2-5.0.0.jar or
simplebackpacks-neoforge-26.1.2-5.0.0.jar.
New features
- Dyeable backpacks – dye any backpack in the crafting grid, and mix multiple dyes to blend your own colour. The colour is kept when you upgrade the backpack to a larger tier.
- Tier upgrade recipes – craft a small backpack into a medium one, and a medium into a big one, using the matching steel frame plus leather. Stored items and the dyed colour carry over to the upgraded backpack.
- New craftable items – steel ingot, steel stick and small/med steel frames, each with new textures.
- Advancements – a progression line for crafting and upgrading
- Structure loot – backpacks can now be found in desert pyramid and jungle temple chests. A big backpack is a rare find; loot weight whole feature can be turned off in the config.
- Backpacks on death – optional settings to keep your backpack contents) through death, or to spill its contents on the ground.
- Tooltips – backpacks show a description, how full they are, preview of their contents. The number of preview lines is configurable.
- Open / close sounds when using a backpack.
Configuration
Lots of new options, all editable in game through Mod Menu (Fabric mod list config button (NeoForge):
-
Toggle individual recipes on or off.
-
Control what is allowed to be stored inside a backpack.
-
Enable/disable structure loot and tune the drop weights per structure.
-
Tooltip content and length.
-
A Reset to Defaults button.
Recipe and loot changes apply after /reload or rejoining a world
other settings apply immediately.
Fixes
- Fixed the Finnish translation not loading.
- Corrected
pack.mcmetaformat for Minecraft 26.1.2. - Various smaller bug fixes and internal cleanup.
Optional dependencies
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:hZgcSUKC:xeODPCCg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hZgcSUKC:xeODPCCg"
}

