Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 3 days ago
All versions
1.4+1.21.8
Release
Server Backpacks! 1.4+1.21.8last year 147
Compatibility
Minecraft: Java Edition
1.21.8
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Any compatible version
Changes
BACKUP before updating!
Changelog
Features
- Includes a module system for backpacks.
Available modules:
- Void Module - Voids nearby items matching a specified filter.
- Vacuum Module - Automatically inserts nearby filtered items into the backpack.
- Crafting Module - Opens a crafting menu. (Shift + right-click the backpack when in its inventory, then right-click the Crafting Module.)
- Some massive changes to data system and also the codebase.
- Global backpack now have 57 slots, and can be linked with other global backpacks using a ender pearl dropped on the ground with one other global backpack instead of being one global inventory. (This will erase any inventory previously in global backpack!)
- Recipe changes.
- Some configuration entries were removed in this alpha:
enable_globalpackenable_enderpack
- These has been replaced with:
disabled_backpacks: []- Specify a backpack's ID to disable, e.g. ,["global", "ender"]
- Added new configuration entries:
"enable_upgrades": true"disabled_upgrades": []- Specify a module's ID to disable, e.g. ,["void_upgrade", "magnet_upgrade"]
Notes
- Applying a filter - Surround the module with an item (used as the filter) in a crafting table. (You cannot add or remove an item from a module's filter, you can only replace it.)
- Applying a module - Place a module and a backpack into a smithing table to apply the module.
Optional dependencies
Any compatible version
Any compatible version
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:E7IsBILg:zGC2tor2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E7IsBILg:zGC2tor2"
}

