banned-players.json

Players banned from the server, looked up by name (plus optional UUID / XUID for stable identity). Endstone's ban command writes and reloads the file in place; the file is created on demand when the first player is banned.

Use the ban command instead of editing by hand when possible - it resolves UUID and XUID for you.

Sample

[
  {
    "name": "PlayerName",
    "uuid": "00000000-0000-0000-0000-000000000000",
    "xuid": "2533274912345678",
    "created": "2026-01-15T12:00:00+00:00",
    "source": "Server",
    "expires": "forever",
    "reason": "griefing"
  }
]

Fields

Field	Type	Required	Description
`name`	`string`	Yes	Xbox Live gamertag. Case-insensitive.
`uuid`	`string`	No	Player UUID. Prevents bypass via gamertag rename when available.
`xuid`	`string`	No	Xbox user ID. Also helps with rename-resistant identity.
`created`	`string`	No	ISO 8601 timestamp with timezone offset (`%FT%T%Ez`). When the entry was added.
`source`	`string`	No	Who issued the ban (e.g. `Server`, an operator's name, or a plugin name).
`expires`	`string`	No	ISO 8601 timestamp, or `"forever"` for a permanent ban. Expired entries are pruned on the next ban-list read.
`reason`	`string`	No	Shown to the banned player and written to the server log.

Server commands

Command	Description
`ban <gamertag> [reason]`	Ban a player (resolves UUID / XUID).
`pardon <gamertag>`	Lift a ban.
`banlist players`	List banned players.

banned-players.json

Sample

Fields

Server commands

On this page