ACE Medical for Arma Reforger: Versions and Compatibility
Compare ACE Medical Workshop branches, dependencies and game-version tags for Arma Reforger, with a checklist for testing before a live server change.
You will need
- Arma Reforger Workshop access
- The game version your server and group intend to use
- A separate test instance and recoverable backup before changing a live mod list
ACE Medical has separate Release and Dev/TESTDEV Workshop branches, and neither Core pair checked here is tagged for the current Arma Reforger Stable build, 1.8.0.13. The available metadata also does not confirm support for Experimental 1.9.0.10, Xbox, or PS5. Use this as a version and dependency reference, not a promise that an ACE stack will start or accept your players. For a separate mod-specific reference, see RHS Status Quo versions, dependencies and console storage. It covers another Workshop stack and makes the same distinction between listing metadata and tested compatibility.
The practical distinction is simple: each Medical Core depends on the matching ACE Core, and the Workshop’s “Game Version” field is a useful compatibility clue, not a successful test. Before changing a live server, check the current item pages, test the exact list on the game build your group uses, and make sure you can recover the server state. The general Arma Reforger mods guide explains how Workshop mods fit into a server list; the step-by-step guide to adding mods covers the panel and config workflow; the unit server guide covers change records and operations planning.
Is ACE Medical compatible with current Arma Reforger?#
The official Workshop pages I checked do not show a Core plus Medical Core pair built for Stable 1.8.0.13 or Experimental 1.9.0.10. The Release pair is tagged for game version 1.7.0.41; the Dev pair is tagged for 1.8.0.10. Treat that as a reason to test before scheduling an operation, not as proof of incompatibility or a guarantee that the mod will work.
Bohemia’s News page lists 1.8.0.13 as the current Stable update and 1.9.0.10 as an Experimental update. A Workshop “Game Version” tag describes the build the author used for that upload. It does not say that later builds reject the mod, and popularity or download counts cannot fill that evidence gap. I did not install the modules, start a server, join with a client, or test a console in this review.
The guidance below separates documented identity and dependencies from compatibility results. Before you publish an ACE mod list, open each linked Workshop entry again: authors can change versions, dependencies and game-version tags after this page is published.
Keep ACE Release and ACE Dev/TESTDEV as separate stacks#
The two official ACE Medical Core entries are separate Workshop items. Each lists a corresponding ACE Core dependency. Choose a pair from one branch; do not combine the Release Core with Medical Core Dev or the reverse.
| Branch | Workshop item | Author | Mod version | “Game Version” tag | Dependency |
|---|---|---|---|---|---|
| Release | ACE Core · 60C4CE4888FF4621 |
acemod | 1.4.4 | 1.7.0.41 | None shown on its page |
| Release | ACE Medical Core · 60C4C12DAE90727B |
acemod | 1.4.3 | 1.7.0.41 | ACE Core |
| Dev/TESTDEV | ACE Core Dev · 65AD7D0D9941A380 |
acemod | 1.5.39 | 1.8.0.10 | None shown on its page |
| Dev/TESTDEV | ACE Medical Core Dev · 6586079789278413 |
acemod | 1.5.36 | 1.8.0.10 | ACE Core Dev |
“Dev” and the Workshop tag “TESTDEV” describe the ACE mod branch. They do not mean that the item was built for Bohemia’s Experimental game application. Likewise, “Release” does not mean “confirmed for the current Stable version”; the build tag still needs to be compared with the game your server and players will run.
The dependency field is the Workshop author’s declared requirement. Include it when you stage the Medical Core, and check the in-game or panel mod list after adding it. A dependency appearing in a listing does not establish that a larger collection of optional modules loads in the order or combination your scenario needs.
What the optional ACE Medical modules add#
ACE Anvil’s documentation splits medical features across modules. The current Dev/TESTDEV entries checked below are all tagged for game build 1.8.0.10 and list acemod as author. Their pages also show ACE Core Dev and Medical Core Dev as dependencies; Breathing Dev additionally lists Circulation Dev.
| Module | Workshop ID | Version / build tag | Listed dependencies |
|---|---|---|---|
| ACE Medical Hitzones Dev | 65B343F799FB521B |
1.5.36 / 1.8.0.10 | Medical Core Dev; ACE Core Dev |
| ACE Medical Circulation Dev | 65AD7D4F994EA327 |
1.5.36 / 1.8.0.10 | Medical Core Dev; ACE Core Dev |
| ACE Medical Breathing Dev | 671F73D99978B4F2 |
1.5.36 / 1.8.0.10 | Medical Core Dev; ACE Core Dev; Circulation Dev |
| ACE Medical AI Dev | 6A1AF6DD9938A580 |
1.5.36 / 1.8.0.10 | Medical Core Dev; ACE Core Dev |
The names describe separate components, not a requirement to install all four. Start with the modules your scenario actually needs, follow the dependency links shown on Workshop, and test the whole proposed list. This table records Workshop metadata; it is not a tested preset, a load-order guarantee, or a recommendation that the Dev modules are ready for a live Stable server.
After you have verified the exact mod set, the Arma Reforger RAM guide explains how to read current server memory data. A memory estimate cannot prove that ACE loads, that a client can join, or that the pack fits on a console.
The separately published Defibrillation for ACE Dev is by Hypoxic125, not the ACE team. Its page calls it an alpha, says “Expect issues,” lists PC-only support, and requires the ACE Dev medical stack. It is an example of why the item author and its own support statement matter: a mod with “ACE” in its name is not automatically an official ACE module or a console-ready recommendation.
ACE Dev is not Bohemia Experimental#
There are two different version axes to check. ACE Release and Dev/TESTDEV are branches of ACE Workshop content. Arma Reforger Stable and Experimental are game applications with their own builds. As of this review, Bohemia’s News page lists Stable 1.8.0.13 and Experimental 1.9.0.10; its current 1.9 Experimental notes identify separate Steam and Xbox Experimental applications, and do not list a PlayStation Experimental client.
That distinction matters when you compare a Workshop tag. The ACE Dev pair and optional Dev modules above say they were built for game 1.8.0.10; this does not mean they target Reforger Experimental 1.9.0.10. The Release pair says 1.7.0.41. None of those tags certifies compatibility with today’s Stable build.
Bohemia’s 1.9 development reports describe substantial changes to vehicle simulation. That is a prompt to recheck the mods your server uses after a game update. It is not evidence that every vehicle mod, or ACE Medical in particular, has broken. Check each Workshop changelog and test result rather than copying blanket claims about a new build.
Check platform support before a crossplay operation#
Reforger supports crossplay on servers that enable it, and mods are available on Xbox and PS5. Bohemia documents the dedicated-server choice as PC-only or PC with Xbox and PlayStation together; there is no Xbox-and-PS5-only pairing. Those general rules do not confirm that a particular scripted ACE module can run on every platform. The ACE Workshop entries listed here do not provide a verified PC, Xbox and PS5 compatibility matrix, and I did not test any of those clients. Treat ACE Medical support on all three as unconfirmed until the mod author or a test of the exact build establishes it.
Storage is a separate constraint from compatibility. Bohemia documents a 25 GB mod-storage allowance on PS5 and up to 50 GB on Xbox. Those are ceilings for a console’s Reforger mod storage, not a promise that a required ACE list fits, downloads correctly, or works in the game. Check the total size and leave room for the group’s other required Workshop content.
If your unit includes consoles, verify the exact server and mod list with a player on each console before announcing that the pack is ready. Do not infer console support from a PC server’s crossplay switch, a mod’s download count, another community’s server listing, or the fact that unrelated Workshop mods are available on consoles.
Test a mod change without risking the live scenario#
Use a separate test instance or a quiet maintenance window that your group controls. Before touching the live mod list, identify a backup that you can actually recover, and record the current scenario, game build, mod IDs, versions and dependencies. A backup slot or a “copy” label alone is not proof that the right save can be restored. Do not wipe a save, replace a scenario or attempt a restore to get past a mod error unless you have verified the recovery path first.
On the test instance, use the chosen branch and its listed dependencies, then compare the server’s startup log with the expected mod IDs and versions. Next, join with a PC client on the same game build and check that the scenario reaches a playable state. Record the result, exact builds and any error text; a server process that stays open does not prove a player can join or use ACE Medical. Repeat separately for Experimental if your unit intends to run that branch. A Stable result does not transfer to Experimental.
For a crossplay group, test Xbox and PS5 clients individually with the same server build and proposed mod list. If a check fails or cannot be run, keep the result marked unknown and hold the change from the live operation. Review the scenario guide before you test, so the test instance uses the same scenario the group plans to run. You can also use the milsim unit server checklist to record ownership, change windows and recovery responsibilities; neither guide certifies this ACE stack.
Use ACE’s docs for medical controls and settings#
ACE Anvil’s Medical documentation owns the player treatment guide and the detail for its components. It explains what each medical module changes, controls for players, and settings under missionHeader and m_ACE_Settings. Follow that source for current treatment and configuration instructions instead of copying an Arma 3 ACE guide; Reforger is a different game and uses its own Workshop items and server configuration.
The Workshop pages are the better source for the exact item name, author, ID, current mod version, supported game-version tag and listed dependencies. Revisit both sources before an update because they can change independently. If you need someone else to operate the server, Game Hosting’s Arma Reforger page explains its managed server option. The panel provides general Reforger controls; it does not certify ACE Medical compatibility or provide an ACE-specific preset.
Quick answers
Is ACE Medical compatible with Arma Reforger Stable 1.8.0.13?
Compatibility is not confirmed by the Workshop metadata checked here: the listed Release modules target 1.7.0.41 and the Dev pair targets 1.8.0.10. That is a version-tag mismatch, not proof that either branch fails.
Do I need ACE Core for ACE Medical?
Yes. The ACE Medical Core Workshop entry lists ACE Core as a dependency; the Dev Medical Core lists ACE Core Dev. Keep each branch paired with its own dependency.
Does ACE Medical work on Xbox and PS5?
ACE Medical compatibility on either console is unconfirmed. Reforger crossplay and general Workshop support do not certify this mod for a specific console.
Is ACE Dev the same as Arma Reforger Experimental?
No. ACE Dev or TESTDEV labels an ACE Workshop branch. Bohemia Experimental is a separate game application and game build.