MINECRAFTBIBLE
Loading...
Official Identica provider for premium account authentication
Premium Provider is the official Identica provider for players with licensed Minecraft accounts.
It gives eligible premium players a smoother way to move through Identica without being forced into another provider that may require extra commands, credentials, or setup. The provider adds a premium-profile based path for authentication, account migration, and additional verification when your network needs it.
Platform
Premium Provider is currently a Velocity/BungeeCord provider and should be installed on your proxy together with Identica.
Java
The provider works exclusively on Java 21 and higher.
Requires Identica
Premium Provider is not a standalone authentication plugin. It requires the Identica core to be installed and configured.
Capabilities describe which parts of the Identica provider system this resource supports. They help you understand what Premium Provider can participate in when it is installed alongside the Identica core.
Premium Authentication
Premium Provider allows eligible premium players to authenticate through their Minecraft profile and continue through Identica without being sent into another provider flow unnecessarily.
Username Change Safety
The provider keeps the account connected to the player’s premium profile, not only to the visible username they use today. If a player changes their Minecraft username, their Identica account can remain attached to the same identity, helping preserve server progress and account data.
Provider Migration
Premium Provider supports migration from other Identica providers into Premium Provider. It can also participate in migrations away from Premium Provider when your network allows another provider to become the account’s new primary method.
Verification Methods
Premium Provider works with Identica verification methods such as TOTP-based 2FA. This means a premium account can still be protected by additional confirmation, and more verification methods can be added through Identica or separate addons.
Premium Provider can be used in two different ways, depending on whether you want eligible players to be handled automatically or choose the provider themselves.
Seamless
Premium Provider can be tried automatically when a player joins. If the player meets the requirements, they can continue through Identica without manually choosing the provider. This is the smoothest option for networks that want premium players to join as directly as possible.
Interactive
Premium Provider can also be offered as a selectable option. In this flow, the player chooses whether they want to continue with Premium Provider before Identica guides them through the provider’s process.
Premium Provider is useful when you want premium players to have the shortest reasonable path through Identica.
Instead of making every player go through the same provider flow, your network can let eligible premium players authenticate through Premium Provider while still keeping the rest of Identica’s account structure intact. Sessions, provider links, verification, and migrations continue to be handled through Identica, while Premium Provider supplies the premium-profile behavior.
This gives premium players a smoother experience and gives server owners a cleaner identity model for accounts that should be tied to a licensed Minecraft profile.
Premium Provider is a good fit for networks that use Identica and want premium players to be recognized naturally.
It is especially useful if you want premium players to join with fewer steps, preserve accounts through Minecraft username changes, allow players to migrate from another provider to Premium Provider, or protect premium accounts with verification methods such as TOTP.
If your setup uses multiple Identica providers, Premium Provider can work alongside them as the preferred path for players who meet its requirements.
Most networks can start with the default configuration.
Advanced setups can adjust provider behavior, messages, commands, cache lifetimes, profile snapshots, and replication cache namespaces when needed. Full setup details and field-by-field configuration notes are available in the Documentation.
