Tags
Creators
Details
1.0.0-beta.1
Compatibility
Changes
This is an early beta release of the 1.0.0 version of ItemSwapper for 26.2. Not all features planned for 1.0.0 are implemented yet and there will be issues, please give feedback on Discord/GitHub. This has been in the works for the past 3 months. Once finished, other versions get the 1.0.0 update too.
What's changed
- Added 26.2 support, Dropped 1.19.4 support
- Full codebase and networking rework, incompatible with any prior version
- Improve Litematica support on >=1.21
- Remove legacy mixins/logic, improving compatibility
- Move any non inventory logic like shulkers to the server side
- New option to keep the last item in shulkers for sorting (see next section)
- Storing away items will not prioritize shulkers with the same item and stack them correctly
- In case no shulker has the exact item, the first palette of the item is used to find a possibly related shulker
- Added setting to use all linked palettes to the held item, this will sort more distant items together
- Instead of swapping the held item with the target, it will now store away the held item and then grab the target
- Added optional restock keybind
- Added optional store away keybind
Known issues/missing features
- Some server behaviors like keeping the last item in the shulker can't be changed client-side
- Bundle support is not yet implemented
- No Spigot/Paper plugin compatible yet
- Add config screen tab to configure items that don't allow pickblock like tools/weapons
- Shulkers get emptied from top to bottom, instead of bottom to top
- The Tools list is broken, use the "show as palette option" as a workaround
- List with enchantments cause a kick
- Unable to view shulker content via click in the inventory
Changes: https://github.com/tr7zw/ItemSwapper/compare/v0.10.1...8d8bd93 (Files changed: 157)
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:RPOSBQgq:qxY4pAn0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RPOSBQgq:qxY4pAn0"
}

