Compatibility
Minecraft: Java Edition
Platforms
Tags
Creators
Details
AutoOrganize
Storage that sorts itself.
Craftable chests that know what belongs inside them. Link them into a network, and every item finds its place.
Paper 1.21.11 • Java 21 • No dependencies
What it does
AutoOrganize adds the AO Chest. Place a few next to each other and they become a network. Put items into any one of them and each stack moves to the chest that holds its category. Ores go with ores. Food goes with food. Nothing is lost, duplicated, or left in the wrong place.
It was built for survival servers where players share space and still expect their things to stay theirs.
CraftChests, redstone and a lever. Place it anywhere you would place a chest. |
ConnectAO Chests that touch on any of their six faces join one network. Diagonals do not. |
FillClose a chest, or let a hopper feed it. Every stack moves to the right chest, spreading across as many as the category needs. |
DirectHold the AO Wand, sneak, and right-click a chest to manage it. |
Recipes
|
AO Chest
|
AO Wand
|
Categories
Fourteen categories ship by default, assigned by material so results are consistent and predictable.
| Ores & Minerals | Building Blocks | Natural Blocks | Wood & Logs |
| Tools & Weapons | Armor | Food | Farming |
| Mob Drops | Redstone | Brewing | Enchanting |
| Transportation | Miscellaneous |
Names, enchantments, durability, custom model data and every other item property pass through untouched.
Want something different? Create your own. A custom category belongs to you, holds the item types you choose, and overrides the default for your chests only.
Your storage, your rules
Every AO Chest records the player who placed it, and every player keeps a private organization: their own category assignments and their own custom categories.
Two players can build chests that touch. They share a network on the map and nothing else.
Sorting only ever moves items between chests owned by the same person. A neighbor's chest never receives your items, and your layout never changes theirs.
Trust, when you want it
Run /ao trust <player> to let someone manage how your storage is organized.
| They can | They cannot |
|---|---|
| Use the wand on your chests | Open your chests |
| Change category assignments | Break your chests |
| Create, rename and delete your custom categories | Grant trust on your behalf |
| Touch anyone else's storage |
Run /ao untrust <player> and it ends immediately, including any menu they have open. Every action in the wand menu checks permissions again at the moment it happens.
Double chests
Two AO Chests belonging to the same player merge into a double chest exactly as you would expect. The pair behaves as one unit with a single category and a single label.
Chests belonging to different players, and ordinary chests, never merge with an AO Chest. That closes the one loophole that would otherwise let a double chest bridge two owners.
The wand menu
Sneak + Right Click an AO Chest while holding the AO Wand.
- See the chest's category, owner, slot usage and network size
- Assign any default or custom category
- Return the chest to automatic assignment
- Create, rename and delete custom categories
- Add or remove item types from a custom category by holding the item
Menus are locked against shift-clicking, dragging, hotbar swaps and every other way of pulling an item out of an interface.
Everything else
Labels
Each chest displays its category above or beside it as floating text, kept in sync as categories change and removed when the chest is broken. Labels do not block clicks, collide with players, or persist in the world file.
Hoppers
Hoppers can feed AO Chests, and what they deliver is sorted like anything else. Output from AO Chests is off by default and can be enabled in the settings. If nothing in the network has room, the item stays in the hopper.
Protection
AO Chests can only be broken by their owner, resist explosions, and cannot be moved by pistons. Dispensers cannot place them, and an AO Chest cannot be used as an ingredient in other recipes. Each of these is a setting.
Commands
| Command | Description | Permission |
|---|---|---|
/ao info |
Plugin information | autoorganize.use |
/ao category |
Your chests and categories at a glance | autoorganize.use |
/ao trust <player> |
Let a player manage your organization | autoorganize.trust |
/ao untrust <player> |
Revoke that access | autoorganize.trust |
/ao trustlist |
List who you have trusted | autoorganize.trust |
/ao settings |
Edit the configuration in a menu | autoorganize.admin |
/ao reload |
Reload configuration and messages | autoorganize.admin |
/ao debug |
Diagnostics | autoorganize.admin |
/autoorganize works as an alias.
Permissions
| Permission | Default | Grants |
|---|---|---|
autoorganize.use |
Everyone | Place and use AO Chests, basic commands |
autoorganize.wand.use |
Everyone | Use the AO Wand |
autoorganize.category.manage |
Everyone | Change categories and manage custom categories |
autoorganize.trust |
Everyone | Use the trust commands |
autoorganize.admin |
Operators | Everything above, plus reload, debug, settings and optional ownership override |
Ordinary players never receive administrator privileges. Admin override is separate from trust and can be switched off.
Configuration
Every option can be changed in game with /ao settings, or in config.yml. All messages live in messages.yml and support MiniMessage.
Network size, custom category limits, name length, trust limits, hopper behavior, protection rules, label display and menu timeouts are all adjustable.
Built for servers
- SQLite storage, written off the main thread
- Ownership, categories, assignments and trust survive restarts, chunk unloads and reloads
- Networks update when chests are placed or broken, not on a timer
- Unloaded chunks are never force loaded; chests there are skipped and picked up later
- Items are never deleted, duplicated or overwritten. If there is no room, they stay where they were
- No per-tick tasks
FAQ
Can other players see or open my chests? Not unless you allow it. Opening is limited to the owner by default, and trust never grants it.
What happens if I break a chest in the middle of my network? The network splits into whatever is still connected. The broken chest's contents drop as normal.
What happens when a category is deleted? Chests using it return to automatic assignment, and their items are left alone until they are next sorted.
Will it fill my chests with junk? Only if you put junk in. Items that fit no available chest stay where you left them.
Does it work with region protection plugins? AutoOrganize respects cancelled events, so plugins that block building or interaction keep working as usual.
Requires Paper 1.21.11 and Java 21


