Links
Tags
Creators
Details
Licensed ARR
Published 8 months ago
Updated 4 months ago
All versions
1.1.0
Release
Chest Sort 1.1.08 months ago 2,181
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Fabric
Supported environments
Client-side
Changes
ChestSort Changelog
v1.0.0 to v1.1.0
FEATURES
- Added slot locking, go into any container and toggle the "Lock Slots" button to lock down slots for your tools & items by clicking in your inventory that you don't want to accidentally move around.
- Added export type "presetList" to export multiple presets in one string, which can be imported by other players. This change did not affect the existing "preset" export format.
- Added
/cs presets exportAllto export all presets in a presetList format. - Added
/cs presets listto list all presets with their names and sizes. - Added
/cs presets exportSelectwith a GUI to select which presets to export. - Added per-container Whitelist/Blacklist filter tabs.
- Added a per-container conflict priority toggle to choose whether whitelist or blacklist wins when both match.
- Added Whitelist/Blacklist tabs to the preset editor (presets now carry their own blacklist rules too).
- Added
/cs blacklist addPreset <name> <blacklist|whitelist|everything>to populate your global blacklist from preset rules.
CHANGES
- Export strings now use
"|"instead of":"to separate fields, to avoid issues with tokens that contain ":" (e.g. item IDs, tag IDs). - Preset export/import strings now support including a preset blacklist section (separated with
~), while remaining compatible with older whitelist-only strings. - Fixed a bug where imported presets would be named "Imported" instead of using the name specified in the export string.
- Made the mod compatible with all versions of Minecraft 1.21.x. The mod should now work on any 1.21 version, but is only tested on 1.21.11.
REMOVED
- Removed back compatibility support for an unused export format that was accidentally included in v1.0.0, which is the base64 JSON format.
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:taG5zlGt:QR6QdpOy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:taG5zlGt:QR6QdpOy"
}

