What is txAdmin in FiveM?

When you download a current FXServer artifact and start it, txAdmin is what opens in the browser: it walks a new operator through deploying a server, optionally from a recipe that installs a framework and its dependencies, and from then on it is the control surface for the running process. Scheduled restarts, resource restarts, the console history that shows the same error on every boot, and the ban list all live there.

Its boundary is the process. txAdmin knows the server is running and who is connected; it does not know what happened inside a resource. Staff actions taken through an in-game admin menu — giving money, spawning a vehicle, teleporting — are not txAdmin's records unless the admin resource writes them somewhere, which is why an in-game admin script with an append-only, attributed log is a separate purchase decision and not a duplicate of txAdmin.

For troubleshooting, txAdmin's console history is often the fastest evidence: whether a failure repeats on every restart (deterministic — a load-order or config problem) or appeared once (state-dependent). Its recipe deployer is also the quickest way to stand up a staging server that mirrors production's framework, which is where every new purchase should land first.