Vault & OlaVault Integration
OlaPermissions natively provides hooks for both the Vault API and the next-generation OlaVault API.
What does this mean?
Plugins like EssentialsX, WorldGuard, or GriefPrevention do not read databases to check permissions or fetch prefixes. Instead, they ask an API: "Does this user have essentials.fly?".
OlaPermissions registers itself as the Provider for these APIs.
OlaVault (Preferred)
If you have OlaVault installed, OlaPermissions injects itself into:
com.olaneria.olavault.api.Permissionscom.olaneria.olavault.api.Chat
This unlocks higher-performance asynchronous methods for modern plugins to manipulate ranks and permissions without lagging the main server thread. We highly recommend using OlaVault over legacy Vault whenever possible.
Legacy Vault
If you have Vault installed, OlaPermissions injects itself into:
net.milkbowl.vault.permission.Permissionnet.milkbowl.vault.chat.Chat
This means any legacy plugin that uses Vault to format chat (fetching prefixes/suffixes) or manipulate groups will still work seamlessly out of the box.
Internal Caching
Whenever a plugin requests a permission check through these APIs, or directly via Player.hasPermission(), it passes through OlaPermissions's internal memory cache. This guarantees O(1) performance and prevents poorly optimized plugins from damaging your server's TPS.