Community and Clan Game Servers
CFTools Architect deploys and automates game servers on your own machines (VPS or dedicated), including installation, updates, configuration, and backups.
Quick answer
CFTools Architect is the game server panel for a community or clan that runs dedicated servers on machines it controls. Each machine runs one Architect Agent. Users and roles belong to that agent, so staff can operate the servers they are allowed to touch without using the root account. Control Center lists servers from every Agent you have paired and can start, stop, restart, or kill a server when the signed-in user is allowed to. Scheduled tasks run a CMD, PowerShell, Bash, or Python script from Agent Settings on a one-time or cron schedule. WebHooks post a payload you define to a URL you choose when an Agent event occurs. Players, bans, and RCon admin stay in CFTools Cloud.
Staff accounts stay on the agent
Every Architect Agent has its own users and roles. They are not shared with other machines. The agent creates a root user with every permission. You cannot delete root or change its roles. Additional users get a username and their own password, then a role that limits what they can do. That is how a community grants access without handing out the root password.
- Users and roles are exclusive to each agent
- Root can manage everything and cannot be removed
- Other users only receive the permissions in their role
One view for every paired agent
Control Center lists servers from every Agent you have paired, as a grid or a list. A server card can start, stop, restart, or kill that server when your user is allowed to. Start is available when the server is created or stopped. Stop, restart, and kill are available while it is running. The per-agent server list in the sidebar is separate and requires server.list and server.view.
- Pair each community machine once
- Operate servers from Control Center without opening every agent
- Actions still follow the signed-in user's permissions
Schedules and outbound events
Scheduled tasks live in Agent Settings. You place a script in the Agent scripts directory and run it with CMD, PowerShell, Bash, or Python, either once or on a cron schedule. WebHooks send a payload you define to a URL you choose. Deliveries come from the Agent. CFTools Cloud is the product for live players, ban lists, and RCon admin on titles it supports. Architect deploys and maintains the dedicated server. Cloud administers the players on it.
- Scheduled tasks run host scripts, not a built-in restart button
- WebHooks can target any URL that accepts the payload
- Player bans and RCon staff access are CFTools Cloud
Related
Quick answers
Can clan staff run the servers without the root password?
Yes. Create a user on that Architect Agent and assign a role. Users and roles exist only on that agent. The root user keeps full access and is not the account you share.
Can I see servers on more than one machine?
Yes. Control Center lists servers from every Agent you have paired. Each machine still has its own agent. One agent does not manage game servers on a different machine.
Can Architect restart a server on a schedule?
Scheduled tasks run a script you place in the Agent scripts directory. Executors are CMD, PowerShell, Bash, and Python. The schedule is one-time or a cron expression. Control Center can restart a running server immediately when your user is allowed to.
How do I notify Discord when something happens?
Architect WebHooks post a payload you define to a URL you choose. Point that URL at a receiver your community already uses. This is not a separate Discord app inside Architect. CFTools Cloud has its own Discord integration for player and server admin on supported titles.
Does Architect replace CFTools Cloud for bans and player lists?
No. Architect deploys and maintains game servers on hardware you control. CFTools Cloud monitors and manages existing servers over RCon, including players, bans, and staff access that does not share the RCON password. Many communities use both.