Account linking connects a LeavePulse profile to a Minecraft identity. It helps player profiles, whitelist applications, and moderation tools refer to the same player consistently.
Verification code flow
- The player signs in to LeavePulse.
- The player opens the Minecraft account linking flow.
- LeavePulse shows a short verification code.
- The player joins the configured verification server or a connected server that supports verification.
- The player runs the verification command for that runtime:
Use this on Paper, Spigot, Folia, Fabric, or NeoForge server builds.
/leavepulse verify VERIFY_CODEShort alias: /lpa
- LeavePulse confirms the identity and updates the player profile.
Online mode
Online-mode Java servers can verify the Mojang/Microsoft-backed UUID. This is the most reliable identity mode.
Offline mode and proxy networks
Offline-mode servers and mixed Java/Bedrock networks can have local names, Floodgate identities, or proxy-provided UUIDs. LeavePulse can still support these flows, but the result depends on the environment configuration and the identity mode detected by the plugin.
Common failure cases
The code expired. Generate a new code on the website.
The player ran the command from the wrong account. Sign in to the intended LeavePulse profile and generate a new code.
The server gateway is not connected. Ask an owner to run /leavepulse status and /leavepulse diagnostics export with the correct platform command prefix.
The server is offline mode and the nickname changed. Ask a moderator to review the identity shown on the application or profile.