Use txAdmin’s FXServer console output for resource errors and its administrative action log for staff actions. Record the incident time and active profile first so you search the correct server and log generation.
Find the relevant log
Open the active txAdmin panel using your normal secure administration route. Review the live console for startup and resource errors. Use the player/server event views and action records for their separate purposes; a gameplay event is not necessarily a script exception.
For stored logs, locate the txData directory and the active profile used by your launcher. Log categories, filenames and configuration can change by txAdmin version. Check the official txAdmin documentation/source before relying on an old path or logger JSON snippet.
Search a narrow time window
- Record UTC time, resource name, player action and recent deployment changes. Note the local time zone if the log uses one.
- Search for the first occurrence of the resource or error near that time. Include the preceding lines and full traceback.
- Compare related client F8 output with server output. A missing export may follow an earlier dependency failure.
- Save only the necessary excerpt with credentials and player identifiers redacted before sharing it.
File search example
If ripgrep is installed on the administration host, run this inside the actual log directory. Replace resource_name with the relevant resource:
rg -n -i --glob '*.log' 'resource_name|error|warn' .Inspect the matching file directly around the incident. Archived compressed logs may require separate decompression into a private workspace. Do not search unrelated customer or player data simply because it is nearby.
Use verbose logging temporarily
Enable a documented diagnostic option only for a specific investigation. Record the old setting and turn it off afterward. Verbose logs can contain identifiers and increase storage use; limit access and define retention.
If txAdmin cannot read a profile or configuration, back it up and inspect permissions and JSON validity. Do not delete admins.json or profile files to force regeneration: that can remove operational state.
Verify a fix
Repeat the original action, then reconnect or restart as appropriate. Confirm that the first error disappeared and the intended behavior still works. Keep the exact version and configuration change with the log excerpt.