CFTools Cloud for DayZ

CFTools Cloud is the live management product for DayZ. It connects to BattlEye RCon and gives you the player list, kicks, bans, messages, restarts, and a record of those actions. The server can be on CFTools Architect or on a machine you rented somewhere else. Cloud does not care which, as long as the RCon UDP port answers and RestrictRCon is 0. That split is deliberate. Hosting and management are different jobs. The comparison is the hosting choice. This page is the management choice.

You will be asked for the RCon password. That password lives in BEServer_x64.cfg or beserver_x64.cfg, not in serverDZ.cfg. The BattlEye guide is the setup. After Cloud is connected, stop handing the raw password to every moderator. Give them a Cloud login with the permissions they need. When they leave, remove the login. Rotating a shared password in a group chat does not scale, and it does not tell you who pressed ban.

Pricing is not on this page. It is on cftools.com/pricing. Plans change. A guide that copies a number will be wrong and will stay wrong. If you are deciding whether the time is worth it, count the nights you already spent in a remote desktop to kick one person. That is the cost Cloud is priced against, not against a fantasy of free labor.

What Cloud will not do: it will not write your types.xml, choose your map, or move your hive to a new disk. Those are host and mission jobs. Use it for the live server. Use Architect, or your VPS, for the files. Use a restart schedule so the Cloud scheduler is the one players learn to trust. Use the ban list with reasons so appeals have a starting fact.

DayZ Manager is not Cloud. This site reads the public CFTools Gameserver Data Service and shows the roster. Spoofed servers are excluded. Your admin actions are not part of the public page, and they should not be. Players can see your hostname, map, mods, and population. They cannot see your ban file. That is the correct split. If you want the server to look the way you configured it, fix the server. The list will catch up on the next pass. It is not a control panel.

GameLabs is the related CFTools feature for communities that want mission telemetry beyond the RCon player list. It is optional. The GameLabs guide describes it so you can ignore it until you have a question it answers. Most servers need a working RCon connection and a moderator who is not asleep on the host. Start there.

Connect Cloud while the server is quiet. Prove a say, a scheduled message, and a restart you are watching. Then invite staff. A first connection during a raid, with a wrong port and a password that has a space in it, is how people decide the product is broken. The password rules are in the BattlEye file. The port has to be open from the internet, not only from localhost. Test from a network that is not the server's network.

Connect once, while nobody is watching

Create the Cloud connection against the live port only after a local test has already worked. Cloud will not repair a cfg the process never loaded. Have the game port up on the public list or, if you are still private, on a passworded instance you can see in the full roster. Then enter the RCon port, not the game port. People swap them because both are UDP and both are four digits. The symptom is a timeout, or a connection to nothing, while the game itself is joinable. That split is useful. If players can join and Cloud cannot, the fault is the RCon path. If nobody can join, stop debugging Cloud and fix the dedicated server.

Invite one moderator the same day. Give them kick and message, not the billing login. Have them send a say you can see in game. Remove them afterward if they were only a test, so you learn where the revoke button is before you need it angry. A former moderator who still has Cloud is a current moderator. The RCon password they never saw is not a comfort if the web session is still valid. Review the user list when someone leaves the Discord role, not at the next incident.

Use the scheduler for the restart you already decided, and turn off any other auto-restart the host panel also runs. Two schedulers produce a double restart and a message that lies about the clock. One clock, in Cloud, is enough if the host reliably boots the process. If CFTools Architect is the host, that boot is the product. If a panel on a VPS also restarts at the same minute, disable one. Then watch a full cycle on the player chart of your own server page. The cliff should match the minute you published.

The public site will not show that Cloud is connected. There is no badge on the community list or the vanilla list. Players infer it from behavior: a restart that was announced, a ban that survived a reconnect, a server that came back. If you want a visible claim, put it in the hostname only if it stays true. "Managed with CFTools" on a server whose RCon password is wrong is a louder failure than silence. Pricing stays on cftools.com/pricing. After you connect, the next click is a test say, not a tour of every feature. GameLabs can wait until a real question needs it. The country pages will keep listing you based on the IP, whether or not you finished the Cloud setup. Finish the setup before the IP gets popular.