How to Install ArmA: Armed Assault and Join a Server

The first thing ArmA does to a new player is make them walk. Not through a corridor with scripted events in it — across two kilometres of open ground, in real time, towards a village that is still a smudge on the horizon when you set off. Nothing happens for four minutes. Then something does, from a direction you were not watching, and you are dead before you have identified the building it came from.

That is the pitch, and it has not changed in twenty years. ArmA: Armed Assault was Bohemia Interactive's first game under that name, and it exists because the studio that made Operation Flashpoint no longer owned the title. Same engine lineage, same island-sized maps, same refusal to help you.

It is also the entry in the series with the smallest remaining population by a wide margin. Listings for it collect on the game's hub, and this guide is written for somebody who wants the original specifically, knowing what they are choosing. If you want the modern version of the same experience, skip to the last section.

Where the population actually went

Being direct about this first, because it changes what you should install.

Bohemia has released four more games in this line since. Each one absorbed the community of the one before it. The mission makers and the addon authors moved with them, and Armed Assault's own multiplayer scene did not so much collapse as relocate — first to its sequel, then to the third game, which is where most of the series' player base still is, and more recently to the studio's newer engine.

So the honest position: playing this one online means finding a group that has deliberately stayed with it, or standing one up yourself. That is a real thing people do. The terrain is not the terrain of the later games and the handling has its own feel, and there are players who prefer both. It is not a thing that happens by accident on a Tuesday night.

If that sounds like too much work, the third game in the series is where you should go instead, and this guide will still mostly apply, because the mechanics that matter carried forward without much change.

Getting it

Armed Assault is a paid PC game. It has been sold through Steam and through other storefronts over the years, sometimes bundled with its expansion, sometimes under a slightly different name in different regions. Check what a given listing actually contains before buying, because the packaging around this game has been inconsistent for a decade and a half.

If it is a Steam purchase, the install goes where your Steam library lives and appears in the Library like anything else.A great many people already own this from an old bundle. Our Steam guide covers account setup if you find you do not.

A note on where the files land: the game keeps its own configuration and profile data separately from the install directory, and the exact location depends on your Windows version and how the game was installed. Rather than guessing at a path, launch the game once and use the in-game menus to find your profile — the mission editor and the addon system both work from inside the game, and you rarely need to touch the folder structure directly unless you are installing mods by hand.

Hardware is a strange conversation for this game. It is old enough that a modern machine should not notice it, and built in a way that punishes modern machines anyway — the engine leans heavily on single-threaded performance and view distance, and it was written before multi-core processors were the assumption. Turning the view distance down does more for your frame rate than turning textures down.

What a session actually is

This is the part that people coming from other shooters get wrong, and it matters before you try to join anything.

ArmA servers do not run a permanent game mode the way a Counter-Strike server runs Counter-Strike. They run missions. A mission is a file somebody made in the game's own editor. It places the units and sets the objectives. It writes the briefing. It decides how many player slots exist and what each one of them is. When the mission ends the server loads another one and everybody starts again.

That has four consequences you will feel immediately.

The server's identity is its mission rotation, not the game. Two ArmA servers can be completely different activities.

You pick a slot rather than a class. The mission author decided there would be one pilot and two medics and a squad of riflemen, and when you join a lobby you take one of those specific positions. Get in early if you want the interesting one.

Missions have real endings. Objective complete. Everybody dead. A timer running out with the convoy still three kilometres from where it was supposed to be. There is no endless respawn loop unless the mission author built one, and plenty of them deliberately do not.

Briefings matter. The mission tells you what it wants in text before it starts, and skipping it is how you end up standing in a field wondering what the plan is while everybody else drives away.

Four habits that keep you alive

None of these are taught. All of them are the difference between a frustrating first evening and a good one.

Stop moving to look. Bullets travel, drop and take time to arrive, and a moving target at four hundred metres is a hard shot. A stationary one in the open is not. Move between pieces of cover and do your observing from behind them.

Use the map constantly. Distances in this game are real and your sense of them is wrong. The map, a compass bearing and a landmark are how everybody who is good at this navigates, and the alternative is walking into the wrong village.

Get in the right seat. Vehicles have positions, and being in the wrong one means you are a passenger watching somebody else play. Learn which key cycles seats before you need it in a hurry.

Assume you will not be revived. Damage here is localised and injuries do not evaporate. Whether a downed player can be brought back at all depends on what the mission author built, and plenty of missions simply do not include it.

Addons, and the thing that stops you joining

Every serious ArmA community runs addons, and addon mismatch is the single most common reason a connection fails.

The model is straightforward once you have seen it. Addons are folders of packed content that the game loads at launch, and the set you are running has to match what the server expects. Load too little and the server rejects you because you lack content it needs. Load something the server has not approved and it rejects you for that instead — servers can be set to verify that every addon a client has loaded is signed by a key the server holds.

Practically, this means you do not assemble a mod list yourself for a community server. The community publishes the list in the order it wants loaded, and you match it exactly. Groups that run this game seriously will have a page or a pinned message that tells you precisely what to load, and following it exactly is the whole job.

Launchers exist to make this less painful — third-party tools and, for the later games, an official one. What is available for this specific entry varies, so ask the group you are joining what they use rather than assuming.

Connecting to a server

Open the multiplayer section from the main menu. You get a server list with the usual sorting, and — the part you want — an option to enter an address directly rather than finding it in the list. The exact label for that option has changed across the series, but it has always been on that screen, and it takes an address and a port.

Copy the whole thing. Bohemia's games have never used the 27015 that Source games default to, hosts run several instances on one box, and a listing's port is not optional information. If you have an address from the hub and it will not connect, the port is the first thing to check and it is right most of the time.

Some servers ask for a password on top of that, which is normal for private group servers and is usually the point rather than an obstacle — the whole model here is a known set of people playing together. If you are on the other side of that and thinking about how to let strangers in without ruining the server, running a whitelist that people actually apply to is about that exact problem.

After connecting you land in the mission lobby rather than in the game. Pick a slot and read the briefing, then wait for the mission to start. The gap between joining and playing is longer here than in almost any other multiplayer game. It is not a bug and nobody is going to apologise for it.

Playing with two or three friends instead

You do not need a public server, and for this game you probably should not start with one.

The mission editor is built into the game and it is genuinely usable within an hour. Place a few units, place yourself, place an objective, save it, host it. Bohemia has always shipped the editor as a first-class part of the product, which is why the series has the mission-making culture it does.

Hosting from inside the game makes your machine both the server and a player. That works for a small group in the same evening. It has the same two limits it has in every game: your friends need to be able to reach your machine from outside your network, and the whole thing ends when you close the game.

For anything that should exist while you are asleep, you want a machine that stays on. Bohemia has published dedicated server software for its games for a long time, and whether you run it on a spare box at home or rent one, where to host a game server is worth reading first — with a game this sensitive to latency across a large map, the region you host in is the decision that matters most.

Problems

"You cannot play/edit this mission; it is dependent on downloadable content that has been deleted." The mission uses an addon you do not have loaded. Match the server's list.

The server rejects you at the lobby. Signature verification, or a version mismatch. Both mean your addon set differs from what the server holds.

Terrible frame rate on a modern machine. Turn view distance down first, then object detail. This engine's bottleneck is not your graphics card.

Everything feels sluggish and imprecise. It is not a twitch shooter and the aiming deliberately has weight and sway to it. There are sensitivity and deadzone settings in the controls menu worth spending ten minutes on before deciding the game is broken.

You cannot find anybody to play with. This is the real problem with this specific entry, and it is a community problem rather than a technical one. Our communities section is built around finding the group before the server, which is the correct order for this game.

Where to go next

The direct line forward is Arma 2, which is where the series found its audience and where the DayZ mod was built before it became its own game, and then Arma 3, which has the overwhelming majority of the series' remaining players and the deepest mod catalogue of any of them. Arma Reforger is the newest engine and the one the studio is building on now.

Sideways, if what you liked was large-scale organised infantry combat rather than the sandbox, Squad took that part and made it much easier to walk into. Hell Let Loose did the same thing with a Second World War coat of paint.

<!-- joingg-footer -->

---

JoinGG is a live directory of community game servers. Every listing is queried directly every fifteen minutes, so the player count you see was measured rather than reported by its owner, and each one carries a copyable connect address. ArmA: Armed Assault servers are listed here, and every game on the site has its own hub. Player counts across every game are on the statistics page.