Target and project are two things
A target is a machine — this PC, a VPS, later a second one. A project is a server: resources, config, database, a pinned FXServer build. One project, many targets. Testing locally and then moving to the VPS is a switch in a menu, not a second setup kept in sync by hand.
The panel is not the game server’s parent
txAdmin starts the server as its own child: if the panel dies, the server dies. Here it runs detached, output to a file, commands over RCON. DECK writes down the process number and reattaches on the next start. Restarting the panel is invisible to the players.
The build is pinned, not incidental
A project carries its FXServer version as a statement. Builds sit side by side, and switching one does not overwrite the other. A server running 35245 locally and 35574 outside has bugs you never see at home.
Tick time is a difference, not an average
The performance endpoint reports totals since boot. Divide those and you get the average of the last three days — a number that stops moving. DECK divides the delta: the average of the last two seconds, and that one moves. If the endpoint is locked, it shows a dash, not a zero.