Inspect and manage players

Before you begin

You need a server grant and an agent with player capabilities. Player controls vary by runtime and installed plugins. A proxy and a backend can report different views of the same player's session.

Find a player

1. Open the relevant server's Players panel.
2. Search for the player's name or identifier.
3. Open the profile and confirm the name, UUID, and current server.
4. Review the available session and location details before taking an action.

Offline history depends on what the agent has observed. Missing geographic data does not prove that a player has no location or that lookup failed.

Use an available action

For a kick, enter a clear reason and choose Kick. Confirm the player has left through the roster or console. For a ban, confirm the exact identity and reason before choosing Ban.

Teleport controls depend on the runtime's supported scope. Check the target world and coordinates. Some runtimes only support same-world teleportation.

A displayed player name alone is insufficient when multiple records or identities exist. Recheck the UUID before an action that affects future logins.

Plugin-specific state

Use Permissions for LuckPerms groups and permission nodes. Use EssentialsX for supported utility state, such as homes or mute information. Use Factions for FactionsUUID data.

EnderDash does not install those plugins through player inspection. See plugin requirements and panel availability.

If an action is missing or fails

Check the selected runtime, player online state, supported capability, server access, and plan feature. If live data also fails, check the connection.

For website sign-in using an in-game proof, use Game OAuth. For a custom hosted form, use player verification.