Mini Vault

Mini Vault is an independent, compatibility-focused fork of the Minecraft Vault plugin. It is not the official Vault project and is not affiliated with the original Vault maintainers.

The project keeps the traditional net.milkbowl.vault API namespace so existing Bukkit, Spigot, and Paper plugins can continue using their current Vault imports. The implementation is being reduced and maintained in small, testable stages, with compatibility taking priority over aggressive cleanup.

What Mini Vault provides

Mini Vault exposes the traditional Vault economy, permission, and chat service APIs through Bukkit's ServicesManager. Optional legacy adapters are discovered only when their target plugin is enabled and their marker class is available.

The first implementation stage introduces a central lifecycle registry that:

• Performs discovery once during startup.
• Reacts to provider plugin enable and disable events.
• Reacts to service registration and unregister events.
• Tracks services owned by Mini Vault.
• Unregisters owned services during provider disable and plugin shutdown.
• Avoids adapter-created lifecycle listeners and polling tasks.
• Keeps optional integration failures isolated from the core plugin.

Compatibility

The compatibility reference is VaultAPI 1.7. The following public packages remain unchanged:

• net.milkbowl.vault.economy
• net.milkbowl.vault.permission
• net.milkbowl.vault.chat

Existing plugins should continue compiling against the traditional API. Mini Vault does not intentionally rename or remove the public Vault API classes.

The current source targets the Spigot 1.13.2 API and includes historical adapters for older Bukkit-era plugins. Paper and newer server versions are not yet covered by an automated integration-server matrix. Verify the target server and provider combination before production deployment.