Run a DayZ Experimental Server

DayZ experimental is not a checkbox on your stable server. It is Steam app 1042420 for the dedicated server. The public branch dedicated server remains 223350. Players who want the experimental client opt into it. People who do not will not be able to join you, and they will describe that as your server being broken. Put "experimental" in the hostname. DayZ Manager keeps these servers on their own roster at /experimental so they are not mixed into the stable rank list by accident.

Do not point an experimental process at the only hive your community cares about. Characters and persistence are not a sandbox. Copy what you need for a test, or start empty. The hive guide is the warning in longer form. Experimental builds change. A mod that loaded on Tuesday can refuse Wednesday's depot. That is the reason to run the branch: you want the change. It is also the reason not to run your Saturday event on it.

CFTools Architect tracks the two branches as separate titles. You can install experimental beside public. You should not install it on top of public to "save disk." Workshop mods still come from the DayZ Workshop, app 221100, for both. The server binary is what differs. Update the experimental install on purpose, read the patch note, then decide if the community build follows. CFTools Cloud will manage whichever process you connected, including BattlEye RCon, as long as the RCon port is the one you think it is. Experimental and stable side by side means two ports. Write them down. The ports guide is how those collide.

Linux plus experimental is two unstable choices stacked. The Linux dedicated server has already been the fragile one. Experimental is fragile by job description. If you combine them, do it on a box you can wipe. The Linux guide does not become softer because the branch is new. Windows is the quieter host for a test that other people are allowed to join.

Tell players what the test is for. "Experimental" with no sentence is how you get a full server of people who wanted stable and did not read. A small cap, a password if the test is private, and a wipe date for the test character are enough. Password servers are a filter, not a moral position. The open roster is everyone who did not set one. Your experimental box can be unlisted in spirit by being honest in the name.

When the experiment is over, shut the process down or move the community back to 223350 with a fresh explanation. Leaving an experimental server in the hostname of a stable mission is the kind of drift the list will not correct for you. The crawler reports the app it saw. If you are back on stable, the /servers list is where you should appear, and /experimental is where you should not.

A second process, a second hive, a second port

Experimental app 1042420 does not upgrade your stable 223350 folder. Install it beside, with its own profile, its own game port, its own RCon port, and its own character data. Pointing it at the community hive "for a quick test" is how you corrupt the only world your players care about. Copy a throwaway mission if you need scenery. Do not copy the live persistence. The experimental roster is where this process belongs. The stable roster is where it does not.

Say experimental in the hostname in the first word, not the last. Players sort lists quickly. A famous community name with "exp" buried after a clan tag will still attract stable clients, and those clients will fail the join and blame your IP. Tell them the opt-in is required. Tell them mods may break on a depot update you do not control. Cap the slots small. A password is reasonable for a test that is not a service. The open list is the wrong audience for a branch that can eat characters.

CFTools Architect tracks the branches separately so you do not overwrite one with the other's update. Let it. CFTools Cloud can manage the experimental RCon the same way as stable, which is useful and also a way to restart the wrong server if both connections are named "DayZ." Name them so a half-asleep moderator can tell. Restart messages should say the branch.

Linux plus experimental is a hobby on top of a hobby. Prefer Windows or Architect for a test other people are allowed to join. When the test is over, shut it down. A forgotten experimental process keeps the port and the hostname and shows up on the experimental list looking like a neglected public server, because it is one. Do not merge the leftover files back into stable because they "seemed fine." Stable gets a deliberate update, a wipe decision, and a sentence on your community page that a human could verify. The branch is a workshop. The live hive is not the workbench.