Field Manual

Optional Client Mods

A short, curated set of sound, visual and HUD add-ons you can run on your own copy of Arma 2: Operation Arrowhead while playing Miksuu's Warfare. They change what you see and hear — nothing else.

The server already allows these. No signup, no whitelist, no application. Our server does not check or enforce client mods, so you can join with any of the mods below — or none of them — and play normally. Players who don't run them are completely unaffected.

First: keep the server pack

If you already play here, your mod line contains the server's own pack: @CBA_CO;@adwasp;@admkswf. That part is not optional@adwasp carries the custom WASP weapon packs (the weapons the mission actually hands you) plus AI and vehicle fixes, and @admkswf is a small Miksuu tweak. Everything on this page is added on top of that pack, never instead of it. When you edit your mod line, keep those three in place.

Before you start

The curated set

CBA_CO

Dependency

Community Base Addons for Combined Operations. Not a feature mod — it's the shared library the HUD and FX mods below are built on. Already the server standard.

Load this FIRST in your mod line. Without it, ShackTac HUD and Blastcore won't initialise.

JSRS 1.5

Sound

The classic Arma 2 sound overhaul by LordJarhead — punchier weapons, richer explosions, better distance falloff and environmental audio. Runs entirely on your machine; pure sound. Use JSRS 1.5 Final plus the JSRS15MOD-HOTFIX.

If you've heard "JSRS spams errors" — that's two missing vehicle sounds, and they're harmless. See the Clean install section below to silence them by deleting the right _c.pbo config files.

Blastcore Visuals R1.2

Visual FXneeds CBA

WarFX Blastcore by Opticalsnare — dramatically better explosions, smoke, dust and particle effects. It changes how blasts look, not how much they cost the server, so it's MP-safe.

Heavy particle moments can dip FPS on weaker machines. If yours struggles, use Blastcore's low-FX profile (or skip it and rely on JSRS + HUD). Requires @CBA_CO.

ShackTac Fireteam HUD (STHUD)

UI / HUDneeds CBA

A minimalist fireteam-position overlay from ShackTactical — a small radar-style display showing where your groupmates are, so you keep formation without spamming map checks. Purely a local overlay; no server component.

Toggle it in-game with Alt + Shift + H. Requires @CBA_CO. Note: the licence is link-only — download from the original source, don't rehost/repack it.

JTD FireAndSmoke 0.3

Visual FXoptional

Ambient fire, smoke and dust effects from the JTD team. A lighter atmosphere layer — burning wrecks and lingering smoke. Purely visual; it does not touch ballistics or ammo.

Partly redundant with Blastcore. Add it only if you want the extra ambient smoke/dust on top. This one's file id on bIdentify is confirmed.

Clean install — stop the RPT errors

These are ~2012-era community mods and a few ship noisy files that spam your .RPT log. None of it breaks the game — but here's how to run each one clean, and which leftover warnings are harmless.

CBA first — the #1 fix

A CBA version mismatch is the most common cause of pack-wide errors. Install CBA_CO and make sure it loads before everything else. If the whole pack is throwing errors, fix CBA before touching anything else.

JSRS 1.5 — silence a noisy sound category

Use JSRS 1.5 Final and apply the JSRS15MOD-HOTFIX. The two known log spammers are missing vehicle sounds:

Cannot load sound 'jsrs_uh1\uh1_ext_high.wss'
Cannot load sound 'jsrs_m134\m134_s4.wss'

These are cosmetic — the sound just doesn't play, nothing breaks. To silence a category, delete only its config PBO — the file ending in _c.pbo (and its matching .bisign), e.g. jsrs_uh1_c.pbo, jsrs_m134_c.pbo.

Golden rule: delete only the _c.pbo config files. NEVER delete a weapon sound container (the non-_c PBO) — several configs share those folders and removing one causes strange overlapping-sound errors.

The separate JSRS15MOD-CONFIGS package lets you switch off script effects (like the in-room / low-FPS ambience sounds) if you find them intrusive.

JTD FireAndSmoke — the one that actually needs a fix

JTD's classic error is not cosmetic: without its config file the mod won't initialise and logs "fireandsmoke mod can not find the config hpp". The fix is to place its userconfig where it expects:

...\Arma 2 Operation Arrowhead\userconfig\JTD\JTD_FireAndSmoke_config.hpp

The userconfig\JTD\ file ships inside the download — just copy it into your OA userconfig folder. Don't delete any PBO; supply the config instead.

Blastcore & ShackTac HUD — generally clean

Blastcore: use the Operation Arrowhead R1.2 build (not "Blastcore Phoenix" — that's Arma 3 and won't work here). Requires CBA. No known chronic log spam. ShackTac HUD: a single clean PBO, nothing to trim. (A reported break on the later 1.68 64-bit patch does not affect our 1.64 server.)

Bottom line: after the CBA + JSRS _c.pbo + JTD userconfig steps above, the pack runs quiet. Any remaining "Cannot load sound / texture" lines you see are cosmetic leftovers — safe to ignore, nothing is broken.

How to install

  1. Download the mod's archive (a folder starting with @, e.g. @JSRS1.5) from the link above.
  2. Drop the whole @folder into your Arma 2: Operation Arrowhead install directory — the same place @CBA_CO already lives.
  3. Enable it in your launcher (the Arma 2 OA Expansions menu, or a third-party launcher's mod list). Tick the mods you want.
  4. Make sure CBA loads first. If you set your mod line by hand, order it like this:
-mod=@CBA_CO;@adwasp;@admkswf;@JSRS1.5;@Blastcore_Visuals_R1.2;@sthud;@JTD_FireAndSmoke

The first three (@CBA_CO;@adwasp;@admkswf) are the server pack — always keep them. From the rest, include only the optional ones you actually want; the line above is the full set. Then just join the server as usual.

Honest caveats

These mods are optional and cosmetic. The server runs identically whether you use them or not — they exist purely so you can make Warfare look and sound the way you like on your own screen.