Player management
Use player history, warnings, kicks, bans, and notes responsibly.
Find the right player
Use the live player list for someone currently online or player search for stored records. Check the name, persistent identifiers, and relevant history before acting. Names can change and online IDs can be reused after reconnects.
Choose the appropriate action
- Direct message: communicate privately with the player.
- Warning: record a rule issue and make the reason clear.
- Kick: remove the current connection; it is not a persistent ban.
- Ban: block the relevant player identifiers for the selected duration or permanently.
- Notes: keep useful context for other staff members.
Your server’s moderation policy determines when an action is appropriate. txAdmin supplies the tools; it does not decide appeals or server rules for you.
Review and revoke
Use player history to review an action, its reason, and its author. An authorized admin can revoke applicable actions through the panel. Revoking a ban is separate from deleting or rotating a log file.
Permissions are separate: for example, an account that can warn a player does not automatically have players.ban.
Database maintenance
The player database is self-contained and does not require MySQL. Framework character or economy data lives elsewhere. Before using cleanup or optimization tools, make a backup and confirm which player records or actions will be removed. A player database export is not a full server backup.
If a player appeals
Ask for the action ID, approximate time, and server name through your own support process. Never ask the player to publish their private identifiers or credentials in a public channel. See Player support.
Source: txAdmin upstream documentation.