Installation & Setup
The plugin runs on SpigotMC, PaperMC, and Folia servers. Use the build for your platform and follow the steps below.
Steps
Place the plugin JAR in your server's plugins folder.
Start the server once. The plugin writes its default configuration file, config.yml, into its own folder.
-
Choose where identity data is stored (see Data Storage). The default is SQLite, a local file that needs no setup at all, so most servers can skip this step.
MySQL, PostgreSQL, and MongoDB each have their own connection section in the configuration: fill in the host, database name, and login for the one you pick. To share data across a whole network through the MCIdentity Central Server instead, switch the storage type to the central server and give the plugin two things: the address of your deployment and the API token that deployment was started with. An optional timeout controls how long the plugin waits for an answer.
Restart the server. The plugin connects to the selected storage on startup and logs a clear error if it cannot reach it.
Death behaviour
By default a player keeps their equipped identity when they die and continues wearing it after respawning.
Server owners who want death to matter can turn on the drop on death option. The equipped identity key then drops like any other item, and the player falls back to the base Player profession until they pick it up again or equip another. The option is off by default.
With a shared backend (MySQL, PostgreSQL, MongoDB, or the central server), every game server on the network uses the same connection settings, so identities follow players between servers automatically.
Requirements
- Java 25 or newer on the server.
- A SpigotMC, PaperMC, or Folia server on the 26.1 API line.
- MCIdentity is a plugin for those servers, not a standalone application.
- No external database by default. MySQL, PostgreSQL, MongoDB, or a reachable central server are needed only when you choose them as the backend. Every driver the plugin needs is already included, so there is nothing extra to download.
Quality
Every release is built and checked by an automated test suite before it is published. The tests cover the identity manager and the public provider, the connection to the central server (exercised against a stand-in server), and the logic that saves and restores sessions.