ALiVE 3Home
  • DynamicAI commanders plan and fight their own war
  • PersistentSave the campaign and carry on next session
  • Company levelInfantry, armour, air, artillery and logistics together
  • Almost any mapMost maps already indexed, or index your own

For Arma 3

Built by Arma community veterans, its editor modules give players and mission makers everything they need to run realistic military operations up to company level, almost anywhere: command, combat support, service support and logistics.

More tools: Terrain Indexer · Build Lists · FOB Types

Free to play · All rights reserved by the ALiVE Mod Team · No re-uploads, porting or monetising · Licence

Latest dev build · 2026-11-17

Gameplay

A war that runs itself

Place a few modules in Eden, or plan the whole operation in the Mission Builder and export it, and ALiVE builds a living campaign across the entire map. AI commanders work through a ranked list of objectives, invading, holding ground or running an insurgency, backed by their own logistics, artillery and air command.

Players choose their part. Fight alongside the AI, lead a squad on tasks generated from the running war, call in combat support from the tablet, build a FOB and keep it supplied, or pick the AI commander's next objective yourself. Civilians live their lives around the fighting and react to it. Save the operation and carry on next session, solo or with a group.

ALiVE 3

The definitive ALiVE for Arma 3

A top-to-bottom overhaul, one module at a time: modernised code, long-standing faults fixed, a sharper editor and tablet, and new capabilities across force placement, the AI commanders, air tasking, combat support and civilian life.

  1. March 2026The overhaul starts
  2. NowDevelopment builds, steered by testers and mission makers
  3. December 2026Final release, the last ALiVE for Arma 3, on the existing Workshop item
  4. ThenThe foundation for ALiVE 4 on Arma 4

Features

Everything a company-level operation needs

Most features are a module you place in the editor and set in its attributes; Zeus modules go down during play. The docs cover every module and setting.

Editor modules

Place a few modules and markers in the Arma 3 editor and get a full scenario.

Map-wide placement

Enemy and friendly forces are placed across the whole map for large operations.

Virtual AI

Thousands of land, air and sea units simulated off-screen, spawned only near players.

AI commanders

OPCOM occupies, invades or terrorises objectives, with an insurgency mode.

Enhanced military AI

Garrisons, building patrols, route ambushes and insurgent hideouts, and commanders who shell the contacts they have spotted.

Air command

The MACC flies CAS, recce, SEAD and transport for the AI commanders.

Military logistics

Commanders reinforce and resupply their forces through a supply chain.

Insurgency and civilians

Civilians who talk, panic, flee and remember how you treated them, in towns the insurgents recruit from.

Ambient threats

Close quarters urban combat, IEDs, car bombs and suicide bombers.

Combat support

CAS, artillery and air or ground transport from a tablet, plus vehicles, reinforcements and supply drops.

Operations command

A command tablet with intel, an overhead camera and direct control of friendly AI groups.

Player FOBs

Deploy your own forward bases, build them up from supply and hold them: enemy commanders hunt them.

C2ISTAR

Task generation, intel overlays and SITREP and PATROLREP reporting.

Player logistics

Lift, shift and tow objects and vehicles.

Persistent markers

Map markers and tools that survive between sessions, tied into SITREPs.

Multiplayer support

Admin actions, player tags, view distance, gear persistence, multispawn, rally points, recruitment and crew info.

Zeus modules

27 modules a Zeus drops in play: hand groups to the AI commander, call air strikes, plant IEDs, stir up towns.

Faction tools

ORBAT Creator, the Custom Faction Compiler and the Class Picker make new factions and groups simple.

Persistence

Run an operation over many sessions, no database needed.

Zombie Outbreak

A game mode: zombie hordes run by an AI commander roam the map as virtual groups and attack everyone else.

War Room

The War Room is back

The War Room follows groups and their operations on the web. Register your group, add your servers and they report in as you play. Saving and loading persistent missions works in game, on clients and servers.

Still to come: following a running operation live on the Mission Builder's maps, and replaying it afterwards. Follow progress on Discord.

Download

Get ALiVE

ALiVE (Development Version), updated 2026-11-17. Built from the latest code with the newest fixes and features, and updated on the Steam Workshop with every build. Report anything odd on the issue tracker.

Install

  1. ALiVE needs CBA_A3. Subscribe to it first.
  2. Workshop: subscribe, then turn both on in the Arma 3 Launcher.
  3. Zip: extract @ALiVE into your Arma 3 folder.
  4. Servers: add -mod=@CBA_A3;@ALiVE to the command line.
ALiVE War Room world map: a globe with the groups, their servers and the terrains they play, recent operations and what is running now ALiVE War Room live map: tracking an Independent group riding in a KamAZ, with its route, who has spotted it, and the players on the map Mission Builder full screen: the Military AI Commander open, with its synced placements and settings Mission Builder zoomed in on Kavala, Altis, pointing at the hospital: its picture, size and grid Mission Builder at night over Kavala: lit windows, street lamps and the lighthouse beam Mission Builder: choosing an Offensive on Altis Mission Builder: a three-way war between NATO, CSAT and the AAF Build and Supply Catalogue: tanks from RHS with prices and tiers Build and Supply Catalogue: switching categories on and off Index a Terrain: paste a Workshop link and the server indexes the map
War Room: every group's servers on one globe, with what's running now and a live map to watch it.

What's new

Latest ALiVE 3 changes

Straight from the docs changelog. See every change.

Loading the latest changes…

Questions

Common questions

More in the docs Q&A, or ask on Discord.

LLMs, AI and ALiVE 3

These days we hear so much about AI language models (LLMs) and how they're being used in modern development projects, so we think it's important to make clear exactly how they are being used within the ALiVE Overhaul development cycle.

Yes, AI language models (LLMs) are part of how ALiVE 3 is being built.

No, ALiVE 3 is most definitely not a "vibe coded" project.

  • Many of our project contributors are professional IT workers and developers with decades of industry experience.
  • We started the ALiVE project over a decade ago, before LLM AI even existed.
  • We bring the same design, build and test discipline to ALiVE that we use in our professional work.
  • LLMs are one of the modern tools in that process, and whilst we embrace their use, we apply strict rules and use their power to offload specific tasks:
  • Every change starts with humans reading the code around it.
  • Anything substantial is planned first, sometimes with a specific LLM tool set, and all plans are reviewed by humans for issues before any code is written.
  • The code is a mix of human and LLM work: the LLMs do the 'grunt' work.

What does the AI "grunt work" look like in a project such as the ALiVE overhaul?

Boilerplate and scaffolding

writing repetitive setup code, configuration files and standard templates needed to start new modules or features.

Data formatting and conversion

converting large datasets and saved campaign data between formats.

Test missions and checklists

building the test missions and step-by-step checks that each change is run through on our test rigs, once the core logic is written.

Documentation and language translations

drafting function header comments, documentation pages and their translations, explaining how existing code works.

Routine refactoring

renaming variables, updating deprecated syntax across dozens of files, or adapting functions from one specific task to another.

Triaging GitHub issues and breaking them down into specific, tangible tasks.

  • Humans code much of the logic and the nuanced changes (and there are a lot in this project), and every finished change is reviewed again and checked.
  • Nothing goes into GitHub until it has been tested in game, on dedicated server test rigs and by our human testers playing it in a live game session.

To allay any fears: humans are involved in every step of ALiVE's move to ALiVE 3.

Where's the documentation for ALiVE 3?

The ALiVE 3 docs have a page for every module and setting. The old wiki describes the older release and often won't match. In the editor, the circled ? next to a module's icon opens its page, and ALiVE Presets in the ALiVE menu places one of 19 ready-made setups.

What's the least I need for AI to spawn and fight?

ALiVE (Required), the Virtual AI System, a Military Placement with your faction, and a Military AI Commander with the same faction ticked, synced to the placement. Do the same for a faction on the other side and they'll fight.

Should I use the dev build or the stable build?

The dev build. Stable won't be updated until ALiVE 3 is finished, and the dev build is the one that gets new features, fixes and help on Discord. Back up your mission and test it after an update.

Is my faction mod supported?

Almost certainly. If it shows in Military Placement's faction list, ALiVE can spawn it. The Creator DLCs, RHS, CUP and 3CB work as they are, and a faction with soldiers but no groups gets squads built for it.

Is my map indexed?

Open it in the editor with ALiVE loaded and wait for the Index Viability notification: Good, Reduced or Poor means it has an index. The terrain list shows the indexed maps. If yours isn't there, you can index it yourself and submit it.

How do I set up persistence?

Leave ALiVE Data's Database Source on Local, then turn on Persistent in each module whose progress you want kept. Saves go into your own profile, or the server's on a dedicated server. No website is needed.

How do I keep a mission running smoothly?

Most of the cost is how many AI are spawned around players. Lower Force Size on Military Placement and the Spawn Radius on the Virtual AI System. A headless client helps only with spawned AI; the commanders always run on the server.

How do I report a bug?

Open an issue on the GitHub tracker and attach the RPT log from the session where it happened. Turn on Enable Debug for the module involved first. A report without a log rarely gets fixed.

Team

Who makes ALiVE

Development team

  • ARJay
  • Friznit
  • Gunny
  • Hazey
  • Highhead
  • Javen
  • Jman
  • MarcelDev89
  • Raptor
  • SpyderBlack723
  • Tupolov
  • Wolffy.au

Contributors

  • AUTigerGrad
  • Cameroon
  • HeroesAndVillainsOS
  • Naught
  • Neo
  • Rye
  • Sacha L
  • Whigital
  • WobblyHeadedBob

Testers

They play the dev builds week to week and steer the overhaul with their reports and ideas.

  • A. Ares
  • AshTray
  • Benjamin (Benji)
  • Eric
  • Goldwep
  • NeisAEL
  • spooked
  • Will501

Bugs and support

Report bugs on the GitHub issue tracker. Support covers the official ALiVE modules only, not general mission editing, Arma 3 itself or other mods.

Support the project

ALiVE is free. Donations pay for the servers behind the docs, the terrain indexer and the War Room: donate here.

Licence

ALiVE is free to play with, but it is not open source: all rights belong to the ALiVE Mod Team. It's for personal entertainment on Bohemia Interactive's Arma 3 only. Re-uploading, porting or monetising ALiVE is not allowed without the team's written permission. See the licence on GitHub.