Arma 3 Antistasi Server Setup (Plus the Arma Reforger Alternatives)

Antistasi is the persistent guerrilla campaign for Arma 3: you start as a handful of rebels and take an entire map back from the occupiers, over weeks of sessions. It runs best on a dedicated server, because the war keeps its state between sessions and nobody has to keep a game hosted on their own PC. This guide sets up an Arma 3 Antistasi server on GameServerKings (GSK) using the official Antistasi Community mod: loading it correctly, the server.cfg mission entry, the admin-only setup screen, and where the saves live.

Looking for Antistasi on Arma Reforger? There is no official port. The closest Reforger game modes, and how to run them, are covered in the last section.

Before You Start

Antistasi now ships as a mod, Antistasi - The Mod (Workshop ID 2867537125, version 3.11.1 as of September 2026), with the mission for every supported map built in. You don't upload a mission file. The Antistasi docs set three rules for servers:

• Load it as a normal mod (-mod), not as a server mod (-serverMod).
• Load only one Antistasi mod at a time. Don't combine the official mod with a fork.
• Every player must load the same Antistasi mod as the server.

The mod has no required Workshop dependencies. Faction mods (RHS, 3CB, CUP and others) are optional and change who you fight.

Step 1: Load the Mod

Pick one of two options in the panel's Startup tab.

Vanilla factions: set Additional Mods to

@2867537125;

With a faction modset: the Antistasi team publishes Arma 3 Launcher presets for its supported modsets (RHS, 3CB BAF, CUP, SOG, BWMod, IFA3 and more) in the Antistasi Guide. Download the one you want, upload it to the server root as modlist.html, and leave Modlist File (Exported from A3 Launcher) on its default. The GSK image reads the Workshop IDs from the file, downloads each mod, and copies its signing key into keys/. Your players load the same preset in their Launcher.

Restart once with Automatic Updates on and watch the console for the Downloading new Mod: lines. Faction packs are large, and RHS alone is several GB, so the first boot takes a while.

Workshop downloads need a Steam account that owns Arma 3

The image can only download Workshop mods when the Steam account set on your server owns Arma 3. Those login fields are hidden in your panel. If no Downloading new Mod: lines appear, or the console says Cannot download mod - Download failed, contact support and we'll help. You can also upload the mod folders yourself over SFTP. How the mod variables work in detail is covered in Arma 3 Mods on a Dedicated Server: Workshop IDs, -mod, -serverMod and Keys.

Step 2: Set an Admin Password

The Antistasi setup screen only appears for a logged-in admin. In the GSK default server.cfg the admin password line is commented out. Open Files, edit server.cfg, and change

//passwordAdmin = "ADMINPASSWORD";

to

passwordAdmin = "pick-something-long";

Set the server name on the hostname = line of the same file. Don't set the join password or player count here. The egg rewrites the password and maxPlayers lines from the Server Password and Max Players variables on every start, so change those in Startup.

Step 3: Point the Mission Cycle at Antistasi

The default server.cfg rotates two Zeus missions (MP_ZGM_m11.Altis, MP_ZGM_m12.Stratis). Replace that whole class Missions { … }; block with an Antistasi entry, based on the example in the Antistasi guide:

class Missions
{
    class Antistasi
    {
        template = "Antistasi_Altis.Altis";
        difficulty = "Regular";
        class Params
        {
            autoLoadLastGame = 60;
        };
    };
};

autoLoadLastGame = 60 makes the server reload the last campaign 60 seconds after the first player connects when no admin is logged in, so the war resumes by itself after a restart. The Antistasi guide lists the allowed values as none, 1, 2, 3, 5 or 10 minutes. difficulty can be Recruit, Regular, Veteran or Custom.

The template is the mission's config class plus the terrain name, not a file name. Some of the maps built into the mod:

Maps from other mods or Creator DLC need that terrain loaded on the server as well.

Two syntax traps

The word class must be lowercase, or Arma fails to parse the file. If you'd rather pick the mission by hand, delete the block entirely and leave class Missions {};. The server will then show a blank screen until an admin types #missions in chat.

Step 4: First Start and the Setup Screen

1. Start the server and join it.
2. Press / to open chat, type #login pick-something-long and press Enter.
3. The Antistasi setup screen opens. Voted admins don't get it; you need the password login.
4. On Load game, create a new campaign. On Factions, pick the enemy and rebel factions. Options for mods that aren't loaded on the server are greyed out. On Params, the Antistasi guide suggests disabling membership and TK punishment if you only play with friends.
5. Start the campaign.

After that, autoLoadLastGame brings the same campaign back after each restart. Only an admin can create a new game.

Headless Clients

Antistasi supports up to three headless clients, which take AI off the main server thread. The GSK egg can launch them for you: set [Advanced] Headless Clients (HC) to 1, 2 or 3 (the variable goes up to 5, but Antistasi uses at most three). The egg already fills in the headlessClients[] and localClient[] entries in server.cfg. If the server has a join password, the egg passes it to the headless clients automatically.

Each headless client is another Arma instance inside your plan's memory and CPU, so only turn them on if the server has headroom. The egg describes them as "only recommended for advanced users". Set [Advanced] Clear HC Profiles Cache on Startup to 1 while you use them.

Saves and Backups

Antistasi saves into the server's profile, not into the mission. That's why updating the mod doesn't wipe your war. With the GSK egg the profile lives under serverprofile/, and the main profile is serverprofile/home/Player. Depending on the Use new save file option on the Load game tab, the campaign is written either to the profile's own vars file or to a separate AntistasiCommunity.vars, which the Antistasi team says "makes it easier to transfer saves between machines or profiles". ALiVE campaigns have their own persistence setup, covered in ALiVE on an Arma 3 dedicated server.

To protect a campaign:

• Take a backup before changing mods, factions or the Antistasi version.
• If you schedule restarts with Schedules, save the campaign shortly before each one so a restart doesn't cost you progress.
• When moving to or from GSK, copy the whole serverprofile/ folder.

Antistasi on Arma Reforger

As of September 2026, the Official Antistasi Community has no Reforger version. Its projects are all Arma 3, and searching Bohemia's Reforger Workshop finds no official release. What Reforger players mean by "Antistasi" is usually one of these community game modes:

On a GSK Reforger server:

1. Add the mod and its dependencies to the mods array in config.json (step-by-step in Arma Reforger Mods: How to Add Workshop Mods to a Dedicated Server).
2. Put the scenario ID in the Scenario ID Startup variable, not in config.json. The egg overwrites game.scenarioId from that variable on every boot.
3. Restart. The console lists every available scenario at startup, so you can copy the ID from there if a mod renames it.

Made with 💜 by GameServerKings