Survive The Horde. Not The Admin Work.

Over the game's built-in telnet admin port (8081 by default). Enable telnet and set a password in serverconfig.xml, add the server in the panel, and the console, live player list, chat feed, and ban enforcement come online.

Telnet alone drives the console, roster, chat, and admin commands. If you also expose 7DTD's built-in web API, Metabans lights up the extras: a live world map with player positions and tracked entities on the real map tiles, per-player buff and debuff state, and the in-game clock with the blood-moon countdown. Those four need the web API — everything else works on telnet alone.

Ban, unban, kick, server-wide say, set world time, force a world save, and a graceful shutdown. Panel broadcasts are mirrored into the live chat feed, because 7DTD echoes server-originated chat without a name segment and the connector deliberately drops those lines.

Yes. 7DTD is crossplay and the roster reports both the native platform id and the EOS crossplay id per player. Metabans resolves each player to the platform they actually joined on, so a Steam survivor and an Xbox survivor on the same server are two correct identities, not one guessed one.

Overhaul modlets that keep the stock telnet output format work as-is, since Metabans reads the standard roster and chat lines. Modlets that rewrite chat formatting can change how chat is attributed — tell us which one you run and we will look at the parsing.