Repository navigation
Sorting Pins and Layouts
| Rule | Priority |
|---|---|
| Blocks First | Blocks → resources → tools → food → redstone → utility |
| Vanilla Categories | Blocks → tools → food → resources → redstone → utility |
| Resources First | Resources before all other groups |
| Tools First | Tools and equipment before all other groups |
| Food First | Food-component items first |
| Redstone First | Redstone-related items, rails, hoppers, controls, pistons, observers, and torches first |
| Alphabetical | Item identifier and custom name |
| Largest Stacks | Stack amount descending, then stable item and source-slot ordering |
Within a group, item identifier and custom name provide deterministic ordering. Original slot position breaks remaining ties.
Pins reserve exact positions before sorting begins. They are appropriate for maps, tools, emergency food, a deliberately empty pickup position, or a storage display arrangement that must remain fixed.
Pins do not summon a remembered item. They keep whatever is currently in the position—including nothing—where it is.
A saved layout is a set of desired item targets, not a kit.
- Up to five layouts per player
- Up to five layouts per storage coordinate
- Non-empty saved positions become targets
- Empty saved positions remain sortable
- Missing targets remain missing
- Unmatched items continue through ordinary sorting
- Item identifier and custom name are used for target matching
When a layout is active, restacking is skipped. This protects layouts that intentionally spread compatible items across several positions.
- Use pins when exact positions must never move.
- Use a layout when existing matching items should return to familiar positions.
- Use both when a few positions must remain immutable and the rest should follow a reusable template.
- Clear the active layout when maximum consolidation matters more than remembered positions.
Layout matching does not promise to identify every private component used by another add-on. Several items sharing an identifier and custom name may be selected in stable source order even if enchantments or hidden data differ. Items are swapped as complete native stacks, so the contents are preserved even when the chosen copy is not the one expected.