Botman Server Manager: Official Support Thread

Tags: hosting, tools, botman, server-manager

Botman is a Lua-based automation layer that sits on top of your 7 Days to Die server. It listens to the telnet API and chat, exposing quality-of-life commands, protections, alerts, and scheduled tasks. Think of it as a second pair of eyes that keeps the server tidy while you sleep.

Why use Botman

• Centralized chat commands for admins and players (teleports, base protection, muting, warnings).
• Automatic region resets, land-claim enforcement, grief protection, and server messages on a schedule.
• Integrations with CSMM and web dashboards for remote control.
• Runs alongside other managers without replacing your existing server config.

Prerequisites

• Telnet enabled on the server with a strong password.
• A persistent host (Windows or Linux) that can keep Botman online 24/7.
• Access to a MySQL/MariaDB database if you want stats persistence and multi-server setups.

Install and connect

1) Enable telnet in serverconfig.xml and note the port/password. 2) Install Mudlet (Botman runs inside it) and import the Botman package. 3) Add your server connection details inside Botman's config and test the telnet connection. 4) Create an admin account, verify chat command prefix, and test a safe command like /help.

Operating guidelines

• Keep Mudlet running in a dedicated session or service so Botman survives reboots.
• Use Botman's built-in backup and region-reset tools for regular cleanups.
• Limit who can run high-impact commands by permission level; audit the command logs weekly.
• Update Botman when you update the game server to keep command lists and APIs in sync.

Troubleshooting

• If chat commands do nothing, confirm telnet is reachable and that Botman is logged in as admin.
• Slow reactions usually mean telnet is rate-limited or the host is low on CPU; keep the Botman host light.
• Database-related errors: verify credentials and network access to the DB server, then restart Botman.