Skip to content

AIRLOCK

Reads a skill file the way an assistant would, and tells you what it found.

NEXUS

A Windows app that keeps the pieces in one place instead of five windows.

Skill index

Every skill in the index, with the verdict the engine actually produced.

↑↓ to move ↵ to open

Sign in

An account is an email address and a password. Firebase stores the password, hashed — this site never sees it.

Sign in
DECK · in development

One window. Every server.

DECK runs FiveM servers — the one on this machine and every VPS you add. Not a second txAdmin: it asks a different question.

Where it comes from

A rented server was cancelled, the backup had to run somewhere, and starting it again by hand every time got old. DECK is what came out of that — built for one question txAdmin does not ask: how do I run one project across several machines?


Four things it does differently

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.


What is in it today

  • Start, restart and stop, with a graceful shutdown so player data is written
  • Live console with per-resource colours, adjustable size and command history
  • Players with ping, connection time and identifiers to copy
  • Fleet view: reachability, latency, system facts over SSH
  • Credentials in the Windows account, never in a config file

How to get it

DECK is not released yet, and the repository is private for now — there is no download and no public source. This is what running it takes.

Requirements

.NET 9 SDK and Windows. Nothing else — no Docker, no virtualisation.

Runtimes

werkzeug\laufzeit-holen.ps1 fetches FXServer 35245 and a portable MariaDB — 675 MB, each checked against a pinned SHA-256. They are deliberately not in the repository.

Build and run

dotnet build DECK.sln, then dotnet run --project src/Deck.App.


Together with NEXUS

NEXUS carries a DECK entry in its sidebar. If DECK is on the machine, the entry opens it; if it is not, it brings you here. The two are separate programs on purpose — DECK talks SSH, RCON and processes, and that has no business inside an assistant.