e566cbf35a
Units accumulate damage in the local variables "ACE_Medical_Engine_$HitXXXX", but these are never reset. The way these vars are used is as a single-damage-event tracker, and the end result of not resetting their value when they're done being used is that a specific $HitXXXX can accumulate enough damage to cause the "select wound with highest damage" code to always select _it_ for the next wound event, even if it wasn't the primary target of the last wound event. I.E. I get shot in the right leg badly. If I then get winged in the left arm, that wound will end up on my right leg, because when the code runs, it finds QGVAR($HitRightLeg) > QGVAR($HitLeftArm), and so it applies the wound to the right leg. |
||
|---|---|---|
| .github | ||
| addons | ||
| docs | ||
| extensions | ||
| extras | ||
| optionals | ||
| tools | ||
| .editorconfig | ||
| .gibot.yml | ||
| .gitattributes | ||
| .github_changelog_generator | ||
| .gitignore | ||
| .travis.yml | ||
| ace_advanced_ballistics_x64.dll | ||
| ace_advanced_ballistics.dll | ||
| ace_break_line_x64.dll | ||
| ace_break_line.dll | ||
| ace_clipboard_x64.dll | ||
| ace_clipboard.dll | ||
| ace_fcs_x64.dll | ||
| ace_fcs.dll | ||
| ace_medical_x64.dll | ||
| ace_medical.dll | ||
| ace_parse_imagepath_x64.dll | ||
| ace_parse_imagepath.dll | ||
| Arma3_workshop_addon.jpg | ||
| AUTHORS.txt | ||
| circle.yml | ||
| LICENSE | ||
| logo_ace3_ca.paa | ||
| meta.cpp | ||
| mod.cpp | ||
| README.md | ||
Requires the latest version of CBA A3.
Visit us on Twitter | Facebook | YouTube | Reddit
ACE3 is a joint effort by the teams behind ACE2, AGM and CSE to improve the realism and authenticity of Arma 3.
The project is entirely open-source and all contributions are welcome. Feel free to maintain your own custom version, so long as the changes you make are open to the public in accordance with the GNU General Public License (GPLv2).
The mod is built modularly, so almost any included PBO can be easily removed from the configuration. This way, a team can maintain its own tailored version of ACE3 by simply excluding any components they don't need, or those possibly in conflict with other mods. Modules themselves, e.g. the medical system, also include various customization options, allowing mission designers to tweak the overall experience.
Core features
- Brand new 3D interaction/action system
- Performance and reliability framework
- Focus on modularity and customization
- New flexible client and server settings & configuration
- Improved medical system with various levels (basic/advanced) focus on gameplay/realism
- Proper & consistent network-synced weather
- Wind and weather-based ballistics
- Captivity system
- Explosives system, including different trigger types
- Map screen improvements – marker placement and map tools
- Logistics
- Advanced missile guidance and laser designation
Additional features
- Carrying and dragging
- Realistic names for vehicles and weapons
- A fire control system (FCS) for armored vehicles and helicopters
- Realistic ballistics/FCS calculated in C/C++ extensions
- Backblast area and overpressure simulation
- Disposable launchers
- Realistic G-forces
- Vehicle locking
- Realistic night and thermal vision modes
- Magazine repacking
- Realistic weapon overheating mechanic
- Combat deafness (temporary loss of hearing) simulation
- Improved interactions for AARs and ammo bearers
- Adjustable sniper scopes
- No idle animation with lowered weapon
- No talking player avatar
- Jumping over obstacles, climbing over walls and cutting down fences
- Vector, MicroDAGR and Kestrel devices
and much more...
Getting started
ACE3 requires Arma 3 and the latest version of CBA A3. See the following pages for help and information on how to get started with ACE3:
Contributing
You can help out with the ongoing development by looking for potential bugs in our code base, or by contributing new features. We are always welcoming new pull requests containing bug fixes, refactors and new features. We have a list of tasks and bugs on our issue tracker on Github. Please comment on issues if you want to contribute with, to avoid duplicating effort.
Contribution guidelines
To contribute something to ACE3, simply fork this repository and submit your pull requests for review by other collaborators. Remember to add yourself to the author array of any PBO you will be editing and the AUTHORS.txt file; including a valid email address.
Submitting issues and requesting features
Please, use our Issue Tracker to report a bug, propose a feature, or suggest changes to the existing ones. See also:
Testing & building
To help us test the latest development changes, download our master branch (directly, or with git), then assemble a test build:
- Setting up the development environment – step-by-step instructions on how to properly setup and build a version of ACE3 for testing purposes.
Get in touch
| Slack | We have a public Slack team that anyone can join. This is where all our developers and contributors hang out and where we make announcements |
| You can follow our Twitter account to get updates and various links to guides | |
| You can follow our Facebook account to get updates and various links to guides | |
| Bohemia Forum | We have a dedicated thread on the Bohemia Forums for the ACE3 project |
License
ACE3 is licensed under the GNU General Public License (GPLv2).