What's broken,
what's fixed

What changed

• Regenerated all seven mod signatures as Arma 2 OA v2 signatures with the project key.
• Replaced the stale dayz_code.pbo signature that caused BattlEye to reject otherwise matching client files.
• Release packaging now runs cryptographic signature validation before publishing client or server artifacts.

What to expect now

• The launcher downloads the corrected signature and the server accepts the client after Steam identity verification.
• Hosts should use the 1.1.3 server bundle or replace the signature files while the server is stopped.

What changed

• Helicopter-crash loot holders now receive separate nearby valid ground positions instead of sharing one position under the wreck.
• Persistent and admin-spawned vehicles keep using their stored UID for cargo saves until the engine assigns a numeric ObjectID.
• The server bundle and existing-hoster mission hotfix contain the same fixes.

What to expect now

• Crash-site loot appears around the wreck instead of as one buried pile.
• Vehicle cargo remains present after the next server restart.
• Hosts should stop the server before replacing the bundle or overlaying the mission hotfix.

What changed

On self-hosted servers the database ran in a console window tied to the person who started it. When that session logged off, disconnected over Remote Desktop, or went idle, the database quietly dropped. Mid-game that froze the server long enough to kick players, and on reconnect their character loaded an older save: you'd get booted and reappear where you were ten to fifteen minutes earlier. The installer now runs the database as a proper Windows service that survives logoff and reboots, and tunes it for stability.

What to expect now

• No more periodic "lost connection" drops or position rollbacks from the database dying.
• The server's database starts on its own after a reboot, no console window to babysit.
• Players-only change is none: this is a fix for people who host their own server. Re-download the server bundle and re-run the installer.

What changed

This revival shipped without a working vehicle spawner, so private and LAN servers never got any vehicles no matter how long you played. Servers now seed about 50 vehicles on first boot.

What to expect now

• Cars, motorbikes, ATVs, vans, trucks, a bus and a few coastal boats, scattered near towns and airfields.
• They spawn damaged and low on fuel, like the old days: find parts and jerry cans to get them running.
• Once seeded they persist. The fleet only refills on a fresh database, so restarts won't pile up duplicates.

What changed

The crash-site spawner relied on engine helpers that don't load on the server, so it failed and no wrecks appeared. Rewritten to run reliably.

What to expect now

• Several smoking UH-1 wrecks spawn around the map each restart, with military loot piled nearby.
• Crash sites only appear on a dedicated server, not the in-game host option.

What changed

• An in-game admin menu for whitelisted UIDs: teleport, spawn, heal, weather.
• A web admin panel showing players and vehicles on a live map, with Satellite, Topographic and Grid backgrounds.

What changed

One download. The launcher detects your Arma 2 OA folder, installs the signature-correct mod files and the Win11 BattlEye fix, and handles every future update. No more standalone installer.

What changed

When you break line of sight with a zombie, it's supposed to give up after about 20 seconds of searching. v8.15 added the system, but a timing bug meant the counter never advanced. The zombies kept chasing forever.

What to expect now

• Run behind a wall, stay quiet, and chasing zombies drop aggro after roughly 20 seconds.
• If you re-enter line of sight first, they reacquire normally.

Zombies

• Once a zombie drops aggro, there's a brief grace window before it can reacquire: no more instantly re-engaging the moment you peek.
• Zombies that get stuck during a chase give up faster (cut the stuck threshold roughly in half).
• When line of sight is broken mid-chase, zombies now path to your last known position at reduced speed instead of teleport-rubber-banding onto you.
• Aggro decay (the "lose interest" timer) fires reliably after about 20 seconds without sight.

Error spam

• Fixed errors when eating that occasionally fired right after respawn.
• Fixed errors thrown when the trigger that detects nearby zombies wasn't ready yet (common during the first second of spawning).

Known cosmetic issues still present

• One missing bandage sound effect.
• Audio device enumeration warnings on startup.
• Bone/skeleton warnings for backpack and butt-pack slots: visual only.

What changed

Vanilla 1.6 zombies, once aggro'd, were essentially permanent: they'd home in on the player's exact position with no concept of "lost sight." Stealth was binary: undetected or doomed.

This patch adds a memory and decay system to the zombie brain:

• Last-known position chase: when you break line of sight, zombies move toward where they last saw you, not where you actually are.
• Slower when blind: they walk while pathing to last-known-position instead of sprinting.
• Aggro decay: if line of sight stays broken for about 20 seconds, they give up and return to wander.
• Reacquire grace window: once they drop aggro, brief pause before they can re-engage.

What to expect now

• Stealth play is viable. Run, break sight, hide; they'll wander past.
• Hatchet-and-run hit-and-runs no longer trail an unshakable mob.

What changed

Originally, dying triggered a complicated in-session respawn flow that often left background timers running while your character was technically dead. Result: weird flickers, leftover medical state, and the occasional ghost-state bug.

Now: death screen plays, then you're dropped back to the multiplayer lobby. Rejoin the server for a clean fresh life through the normal spawn pipeline.

What to expect now

• Death is unambiguous. No half-alive states.
• Save/disconnect on death is clean: your final state writes to the database properly.
• Rejoin lands you at the spawn beach with a fresh character.

What changed

The 2012 release of 1.6 shipped with many code paths that referenced variables before initializing them. Most of the time the engine tolerated this and nothing visible broke, but the server log filled with errors that made it impossible to spot real problems.

This batch of patches hunted down and guarded the worst offenders, especially around death, respawn, model switching, and the medical loops.

What to expect now

• Death and respawn cycles complete cleanly without scrolling red text.
• Disconnect-during-action errors largely gone.
• Server log is quiet enough that any new error actually means something.

What changed

Vanilla 1.6 had a long-standing bug where the medical system from your previous life kept running after respawn, causing periodic screen desaturation flashes and stale medical state (still "in pain", "infected", etc.) on a fresh character.

Across v8.4 through v8.8, all per-life medical state now resets on spawn, and the competing color-correction effects that caused the flash were tracked down and resolved.

What to expect now

• Fresh spawn = fresh body. No inherited "in pain" or "low blood" flags.
• Hit feedback flash is visible per landed strike, not buffered into a stuttering mess.
• No mysterious mid-game desaturation pulses.

What changed

The v8 refactor included a stricter check for "can this zombie actually see and reach the player" before letting it land a hit. The check was too strict: at melee range, the geometry test misfired and zombies were unable to damage anything.

v8.2 relaxed that check. v8.3 fixed a related issue where the engine fires a damage event multiple times per strike (once per body part hit), causing the same blow to register 3-5 times.

What to expect now

• Zombies actually hurt you when they swing.
• One zombie strike = one hit, not five overlapping ones.

v1: Talking to the database again

The original 1.6 client used a long-dead inter-process method to talk to the server-side database extension. Replaced it with the modern call interface so logins, saves, and world streaming all work.

v2: Default values for the basics

• Sunrise time defaults to 6 AM (was undefined, which broke day/night logic).
• Stealth/sound indicator works again.

v3: Hit registration sanity

• Half-second cooldown stops duplicate hit events from firing.
• First pass at "zombies can't damage you through walls": line-of-sight required to hit.
• Zombies slow to a walk when their path is blocked, mitigating the door clip-through.

v4 to v7: Medical system stabilization

Long-running diagnosis of the respawn-flicker bug. Final fix in v7 introduced a session-ID gate so the medical loop from your dead character self-exits the moment a new life starts: instead of silently continuing in the background and fighting with the new one.

v5: Debug toggle

Added a master debug flag plus tagged log categories (health, eat, drink, bandage, hit) so future bugs can be isolated quickly.

v8 / v8.1: Refactor and hotfix

• Reset to a clean 1.6 baseline and re-applied all the v1 to v7 fixes in a cleaner structure.
• Backported later DayZ stability patterns: smarter attack gate, duplicate-hit guarding, building loot dedup, weighted loot cache, view-distance-aware zombie spawn throttling.
• v8.1 hotfix reverted one piece that accidentally used Arma 3 syntax (which doesn't work in Arma 2 OA).

What this means

14 years of changes to Arma 2 OA, BattlEye, Windows, and the wider gaming infrastructure had broken the original 1.6 build in dozens of subtle ways. Getting from "files on disk" to "I can log in, walk around, kill a zombie, log out, log back in, and find my character" was Phase 1.

What got fixed

• Server stack stood up on Windows: dedicated Arma 2 OA server, portable MySQL database, hive extension to bridge them.
• Database schema patched for legacy field widths so 1.6 records save correctly.
• Client/server connection works over LAN through Steam.
• Anti-cheat shimmed for Windows 11 compatibility.
• Custom signing keys generated for the patched files.
• Full round-trip verified: login → spawn → play → save → disconnect → reconnect → resume.