Personal vaults your players can make their own, with storage that fits a single server or a connected network. Configure the experience, manage access and keep recovery tools close at hand.

MINECRAFT 26.3+ · CocoVaults Premium 5
MINECRAFT 1.8.8–26.2 · CocoVaults Premium Legacy
Spigot & Paper · Choose the jar for your version · Folia is not supported

01 / THE PLAYER EXPERIENCEMake every vault feel personal.

Open a numbered vault directly or browse the selector. The space is theirs; the experience is yours to configure.

Make it personal
Custom vault names, material or held-item icons, and one-command item sorting.

Make room for your ranks
Permission-based vault counts, sizes and individual unlocks.

Make it feel like your server
A configurable selector with navigation, locked-vault previews and space details.

Set your own rules
Item blacklist or whitelist, world and game-mode restrictions, cooldowns and optional ender chest access.

Customize messages with MiniMessage, color codes and hex colors. Set opening, closing, denied-access and page sounds. Optional PlaceholderAPI support brings vault information into your messages.

A look inside the vaults

Recorded with earlier builds; the version 5 interface may differ.

02 / STORAGE OPTIONSOne server today. A network tomorrow.

LOCAL STORAGE
JSON · YAML · SQLite · H2

SHARED STORAGE
MySQL · MariaDB · Redis

H2 is included and stays local. Use MySQL, MariaDB or Redis to share vaults across servers. Player leases and version-checked saves coordinate access; conflicting copies are retained for investigation.

Recorded with earlier builds; the version 5 interface may differ.

03 / PLAYER DATALook after what players keep.

Owners and authorized staff share one live vault inventory. Backups and clear admin permissions keep recovery and maintenance within reach.

Save with care
Ordered saves, reported and retried failures, and unreadable vaults kept closed. Item metadata is preserved.

Keep a way back
Automatic and manual backups, restore tools, and a backup before destructive admin actions.

Give staff the right tools
Inspect, edit with permission, clear, delete or purge vaults. Audit staff actions and optionally player item movements.

Bring your vaults with you. Import from PlayerVaultsX, AxVaults, EnderVaults, FairyVaults, CocoVaults 3 or CocoVaults Lite. Migrate between supported storage backends with confirmation steps and a destination backup.

04 / COMPARE THE EDITIONSChoose the storage your server needs.

Both editions include personal vaults, permissions, customization, H2, backups, restore and staff tools. Premium adds SQLite, shared MySQL/MariaDB/Redis storage and cross-server vaults.

Ready to give players more room?

Read the guide, set up your vaults and join the FruitForge community.

Read the documentation →

Join our Discord →

Installation, commands & permissions

1. 
   
2. Back up plugins/CocoVaults and your external database, if used.
3. Stop the server, install the jar for your Minecraft version, remove the previous CocoVaults jar, and start the server.
4. Review Settings.yml and choose storage. Follow the documentation when migrating existing data.
5. Grant cocovaults.quantity.<n> or change Default-Vaults. The default vault count is zero. Grant rename and icon permissions if you want players to customize them.

Useful commands

/cv gui                    Browse the vault selector
/cv 1                      Open vault 1
/cv rename 1 Supplies      Name vault 1
/cv icon 1 HAND            Use the held item as its icon
/cv sort 1                 Merge stacks and sort the vault
/cv admin backup           Create a backup (staff permission required)

Starter permissions · three 54-slot vaults

cocovaults.open
cocovaults.quantity.3
cocovaults.size.54
cocovaults.rename
cocovaults.icon

Use a full restart when replacing jars. Server /reload is unsupported; /cv admin reload reloads the plugin configuration.

Updating from an earlier version

Version 5 reads CocoVaults 4 data from JSON, YAML, SQLite, MySQL, MariaDB and Redis. Existing names, icons and settings are retained. Back up the plugin folder and any external database before updating.

Coming from CocoVaults 3? After a backup, use /cv admin import CocoVaults3 to import supported data. Configuration updates keep your values and save the previous file in old-configs/.

Commands & permissions

The normal and Legacy builds use the same commands and permission names. Angle brackets mark required arguments; square brackets mark optional arguments.

Main command: /cv
Aliases: /cocovaults, /vault, /vaults, /cocov, /cocovault, /pv, /pvault, /pvaults

/cv
Show help.
Permission: none

/cv help
Show help.
Permission: none

/cv <vault>
Open your numbered vault.
Permission: cocovaults.open

/cv gui
Open the vault selector.
Permission: cocovaults.open

/cv rename <vault> <name>
Rename an accessible vault.
Permission: cocovaults.rename

/cv icon <vault> <material|HAND>
Set a material icon or use the held item.
Permission: cocovaults.icon

/cv sort <vault>
Merge stacks and sort an accessible vault.
Permission: cocovaults.sort

Players also need access to the chosen vault through their allowance or an individual unlock.

/cv admin
Show administrative help.
Permission: cocovaults.admin

/cv admin reload
Reload configuration; changing storage does not migrate data.
Permission: cocovaults.admin.reload

/cv admin view <player> <vault>
View another player’s vault; editing also needs admin.edit.
Permission: cocovaults.admin.view

/cv <player> <vault>
Shortcut for administrative view.
Permission: cocovaults.admin.view

/cv admin inspect <player> <vault>
Inspect a vault read-only, even if you can edit.
Permission: cocovaults.admin.view

/cv admin forceopen <vault> <player>
Open a vault for an online player.
Permission: cocovaults.admin.forceopen

/cv admin list <player>
List saved vaults and their details.
Permission: cocovaults.admin.list

/cv admin clear <player> <vault>
Empty a vault after confirmation and backup.
Permission: cocovaults.admin.clear

/cv admin delete <player> <vault>
Delete a vault after confirmation and backup.
Permission: cocovaults.admin.delete

/cv admin backup
Back up all vaults now.
Permission: cocovaults.admin.backup

/cv admin restore <file> [player]
Restore a backup, optionally for one player.
Permission: cocovaults.admin.restore

/cv admin purge <empty|inactive> [days]
Remove empty or inactive vaults; inactive defaults to 90 days.
Permission: cocovaults.admin.purge

/cv admin migrate <source> <destination>
Migrate between supported backends with confirmation and a destination backup.
Permission: cocovaults.admin.migrate

/cv admin import <plugin> [option]
Import supported data; without a plugin name, list importers.
Permission: cocovaults.admin.import

/cv admin info
Show storage, serialization, loaded vaults and backup status.
Permission: cocovaults.admin.info

Migration backends: YAML, JSON, SQLite, H2, MySQL, MariaDB and Redis. Importers: PlayerVaultsX, AxVaults, EnderVaults, FairyVaults and CocoVaults3, plus CocoVaultsLite. CocoVaults3 supports files and SQL; use /cv admin import CocoVaults3 DATABASE for its SQL importer configuration.

Player commands, administrative view, inspect and the player/vault shortcut need an in-game player. Other administrative actions can run from the console; forceopen targets an online player.

Follow the confirmation prompts for clear, delete, restore, purge and migration. Migration requires the same command three times within the confirmation window and backs up the destination.

Player permissions

• cocovaults.open — Open vaults and the selector. Everyone.
• cocovaults.rename — Rename vaults. Operators.
• cocovaults.icon — Change vault icons. Operators.
• cocovaults.sort — Sort vault items. Everyone.
• cocovaults.quantity.<n> — Allow vaults 1 through n; up to 999. Default-Vaults is the fallback. Assign a numeric node.
• cocovaults.unlocked.<vault> — Unlock one specific vault in addition to the normal allowance. Assign a numeric node.
• cocovaults.size.<slots> — Set the general size: 9, 18, 27, 36, 45 or 54 slots. Assign a numeric node.
• cocovaults.size.<vault>.<slots> — Set one vault’s size; it takes priority over the general size. Assign a numeric node.
• cocovaults.bypass.blacklist — Allow storage of blacklisted items. Not granted.
• cocovaults.bypass.restrictions — Bypass disabled worlds, blocked game modes and the opening cooldown. Operators.

Staff permissions

• cocovaults.admin — Grant every administrative permission, including editing. Operators.
• cocovaults.admin.reload — Reload the plugin configuration. Admin bundle / individual grant.
• cocovaults.admin.view — Use view, inspect and the player/vault shortcut. Operators.
• cocovaults.admin.edit — Allow editing through administrative view. Inspect stays read-only. Operators.
• cocovaults.admin.forceopen — Open a vault for an online player. Admin bundle / individual grant.
• cocovaults.admin.list — List a player’s vaults. Admin bundle / individual grant.
• cocovaults.admin.clear — Empty a vault. Admin bundle / individual grant.
• cocovaults.admin.delete — Delete a vault. Admin bundle / individual grant.
• cocovaults.admin.backup — Create a backup. Admin bundle / individual grant.
• cocovaults.admin.restore — Restore backup data. Admin bundle / individual grant.
• cocovaults.admin.purge — Purge empty or inactive vaults. Admin bundle / individual grant.
• cocovaults.admin.migrate — Migrate between storage backends. Admin bundle / individual grant.
• cocovaults.admin.import — Import data from supported plugins. Admin bundle / individual grant.
• cocovaults.admin.info — View plugin and storage status. Admin bundle / individual grant.

These are the default permission names. Open, admin, rename, icon, sort and bypass nodes can be changed in the Permissions section of Settings.yml. A blank command permission allows that command for everyone.

The default vault count is zero; the default size is 27 slots. Assign numeric quantity/size nodes or change the defaults. The highest valid numeric grant is used; a per-vault size overrides the general size.

Operators use Op-Vaults for their selector allowance (999 by default), have access to any valid vault number and use 54-slot vaults. Command permission checks accept * and parent wildcards; concrete numeric nodes are still needed for non-operator vault counts and sizes.

plugin.yml declares cocovaults.quantity.*, cocovaults.size.* and cocovaults.unlocked.* as permission families. Use concrete numeric nodes to define counts, sizes and unlocks.

cocovaults.admin grants all staff actions. You can grant individual admin nodes instead. There is no separate cocovaults.admin.inspect node: inspect uses cocovaults.admin.view.

Optional in both editions. Replace n with a vault number. Vault-content values are cached and refreshed in the background, at most every 30 seconds.

• %cocovaults_max_vaults% — The player’s normal vault allowance.
• %cocovaults_available_vaults% — Available vaults, including individual unlocks.
• %cocovaults_used_vaults% — Number of saved vaults.
• %cocovaults_size_<n>% — Configured slot capacity of vault n.
• %cocovaults_items_<n>% — Occupied slots in vault n.
• %cocovaults_free_<n>% — Free slots in vault n.
• %cocovaults_name_<n>% — Custom name of vault n.

OUR PARTNERYour next server starts here.

Teramont · Official hosting partner
Use code Byte for 15% off your first month.

Explore Teramont hosting →

CocoVaults Premium · Made by FruitForge