Logs & Live Console
Find the right evidence without exposing server secrets or player data.
Which log should you read?
| Log | Useful for |
|---|---|
| Admin Logs | Staff actions, restarts, bans, warnings, settings changes, console input |
| FXServer Console Log | Game-server standard output/error and entered console commands |
| Server Logs | Joins, disconnects, chat, deaths, explosions, menu actions, custom command activity |
Logs are stored under the configured txData profile’s logs folder. Current file location depends on your data path and deployed version.
Use Live Console
Watch a full startup or reproduce one failure. Search for the first error and keep enough lines before and after it to preserve context. Do not execute a suggested command until you know what it does and have the necessary permissions.
console.view allows reading; console.write allows command execution. Give those separately where possible.
Rotation and storage
txAdmin supports persistent logging with rotation. The upstream logging reference documents the per-log defaults and the logger object in the profile’s config.json. Back up the config before manually adjusting rotation. Avoid unlimited retention when the host has limited disk space.
Rotation and deletion affect log files, not the player database’s moderation records. Do not delete logs to try to unban someone.
Share a useful report
Include the artifact/txAdmin version, operating system, exact error, time of occurrence, and relevant surrounding lines. Redact passwords, database connection strings, tokens, registration keys, and private player identifiers. Keep an original private copy for your own investigation.
Read Logging reference for defaults and Custom server logging for client command logging.
Source: txAdmin upstream documentation.