Search the Community

Hello dear people, this is my first forum topic and please dont kill me if I do everything wrong! I am a beginner server administrator and trying to get some things to work. I rented a A3Wasteland server and got it running with https://github.com/MayhemServers/MAYHEM_A3Wasteland.Altis mission. Now theres an addons folder and I try to get some of them working but nothing I tried was a success. For example the buryDeadBody addon can someone explain how to get it running? Im thankful for any help and tipps 😃 Also theres an AI_Spawner folder but I dont get it running too. We hoped to have a nice Wasteland server with occasionally spawning AI troops to support or attack. Im trying my best but its hard. Thank you guys in advance. Nils

THERE IS ONLY WAR A Warhammer 40,000 mod for Arma 3. Warhammer 40,000 is a thrilling fantasy universe, one filled with deep stories, enormous conflicts, supremely evil characters, and an eternity of unending, soul-crushing war. It deserves a proper, massive, frontline experience that only a certain game can provide, and that game is Arma 3. "There is Only War" is a mod whose goal is a true representation of 40k in Arma. There will be a no-nonsense approach to creating this ultimate experience - Boltguns will blow targets away, Necrons will be nigh indestructible, Space Marines will stand heads taller than mortals, and one day, Battle Titans may stride over warzones, crushing and annihilating whole companies of troops with one volley of fire. This project will be true to the universe, and lore will be followed as closely as possible, confined only by game limitations, and in extreme cases, common sense. Now, this mod is not affiliated with the Warhammer 40k mod already on the Steam Workshop. While most of the devs on this team came from that project, and quite a few assets were given to us by that mod, we are not working with them, we are a separate mod. It is also important to state that we are not and will not be using any stolen assets, or assets from 40k video games, content will be made the old-fashioned way. "There is Only War" is currently in early development, and we have under a dozen developers at this time. We don't have a first release date yet, but it is certainly within a few months, and afterwards, we plan on monthly updates and patches! This mod is a very ambitious one, scores of animations must be done, hundreds of models completed and textured, and uncountable hitboxes and configs made, and we are looking for more developers to aid us in our endeavor, if you love this universe you'll find yourself at home with us. It's a tough job, but this task is not impossible to complete. Here is a short gallery of assets currently being worked on : There are many more assets in production, but all will be posted in time. Lastly, we do not own Warhammer 40k, all credit goes to the respective owners!

Hi all, Here is a new module in MGI Advanced Module addon, for spawning any groups you want, any time... (done) This module allows: - to spawn any group, even customized, on any side, - spawning on multiple possible areas (triggers) - with a wide randomized choice or a very specific group. You can place several modules on the map, each of them have their own parameters; 1. Choose the side (applies to all groups spawned from a module, no matter the initial vanilla side). So civilian units can be aggressors. 2. decide if you want to spawn: * at total random (so the groups are picked in cfgGroups, but for the side you chose (normal limitation) * at randomized or specific faction(s) . They must exist in cfgGroups (not all factions from cfgFactionClasses are available for groups). All factions (cfgGroups) are available so not depending, here, on the final side * You can filter these first possibilities by the type(s) of groups. For example, "infantry" and/or "motorized" and/or "armored"... But, these types must exist in the cfgGroups. * you can choose to spawn a specific group (from cfgGroups).. or even an array of units, vehicles... or even an edited group (with all customized textures, pylons, loadouts...) * linked group(s) on module, customized or not, will be candidates for spawning. That's fine for spawning not existing groups such as air or sea patrols. 3. Choose the attitude: behavior, combat mode, formation... 4. choose the repeat sequence (limitation and delay) 5. decide on what condition groups module can spawn (not only at start, but any time!) 6. decide for a simple task (or not). Chase players, enemies, defend... 7. run a code for each group (useful for specific task) MODULE(S) IN 3DEN - Position/ area of the module(s) if no synced trigger area. Direction of the module, in 3den, is the direction of the group (if no synced trigger area) SYNCED TRIGGER AREA(S) - The position, area and direction of the module doesn't matter any more. The group(s) are spawning at randomized positions in randomized trigger area(s), with the direction of the trigger area. SYNCED UNIT(S) - In 3den, you can place (customized or not) group(s) with the module(s). No matter if you synced one (leader or not) or several units of a group, with the module. The group will be candidate for spawning. PARAMETERS SIDE - Definitely the side of your group(s) for this module. No matter the choice you did (edited group, chosen faction(s), or type(s) of group or group(s)..) What ever you spawn we belong to this side. --> But, if you let the module at full random (no synced group, no, faction, no type, no group), in this case, the randomized group is picked among the native possibility from cfgGroups. So, if you just select a side (say EAST), you'll spawn randomized groups(s) from OPFOR. HOW MANY GROUPS - The number of group(s) to be spawned at each occurrence. Randomization will depend on the possibility of what you want to spawn, so your choice) Min 1 max 12 (limited for performance saving when spawning heavy customized groups. Feel free to add other modules) NOTE: The modules works with edited groups or existing configs/classes of groups in cfgGroups (see config viewer from console). So, scripted groups have always the architecture: configFile >> "cfgGroups" >> "side" >> "faction"* >> "type of group" >> "group" ... then units/vehicles for each group Example: side like "Indep" , faction like "IND_E_F", type like "infantry", group like "I_E_InfSquad" FACTION(S)* - If empty, no filter about them. If filled without any more details (type(s), group(s) ) all available factions in cfgGroups can be used to spawn any child type, then any child group. But ⚠️ all current faction names can't work. Some existing factions in cfgFactionClasses are not present in cfgGroups. For example: "CIV_IDAP_F" (IDAP civilian faction has no group) or even "OPF_V_F" (Arma Viper) can't work in the architecture of cfgGroups. (for Viper, the only group defined in: configfile >> "CfgGroups" >> "East" >> "OPF_F" >> "SpecOps" >> "OI_ViperTeam" exits. So at faction level, there is nothing to do). You can fill the parameter with a working class like: "OPF_F" , or the config (configfile >> "CfgGroups" >> "East" >> "OPF_F"), or an array of these possibilities. Not case sensitive. TYPE(S) - if more a filter about what you want to spawn. That should be simple as "infantry" or " motorized or mechanized" or "armored". That doesn't. Even in Arma vanilla, you can find exotic classes as "motorized_MTP". Any dev has his own mind to sort the groups by types. The reason is probably the way you can find sorted groups in 3den's right panel. But, it's just impossible (or needs an updated list of hundreds of names) to filter groups easily. You have to do that job, if you want to do so, writing a config or a class or an array of that, for filtering the type(s). Not case sensitive but do not make typo's error! If wrong, there is no more filter. You can fill the parameter with a working class (not the config) like: "specops", or an array of these possibilities. SPECIFIC GROUP(S) - a step more for less randomization. You are at the group level. As factions, you can fill it with class (of group) or config or an array of these possibilities. Much more, you can add arrays of units/vehicles class(es). That's also a way to customize some groups, but one the contrary of synced edited ones, you'll not able to define appearance for vehicles or pylons payload at this moment. RADIUS AREA - radius of the module area, so the spawn area if no synced trigger areas. Useless if any trigger area synced. GROUP(S) DIRECTION - orientation of the module in 3den (shift mousse drag) . Do not write anything on field (it's a result, not an entry). Useless if any trigger area synced. GROUP(S) SKILL - As 3den, skill for whole group, with +/-10% randomized on each units. ENABLE DYNAMIC SIMULATION - As in 3den. See Biki for detailed explanation (recommended) CONDITION FIELD - checked every 2 seconds. So, much more convenient than a simple condition of presence at start! Feel free to do what you want but return a boolean. Examples: * spawning only at night : sunOrMoon < 0.5 * strengthening weakened side : INDEPENDENT countSide allGroups < 3 * waiting for more players : count allPlayers > 2 * even checking for 1000 m distance at least from any player: private _possAreas = _logic getVariable "possAreas"; (count allPlayers > 0 && allPlayers findIf {private _plyr = _x; _possAreas findIf {_plyr distance _x#0 < 1000} == -1} == -1) but that will not despawn or hide or disable the groups! See the dynamic simulation instead. REPEAT OCCURRENCE - the added times for re-spawning the same groups (not at the same place) . 0 means no more occurrence. -1 means infinite repeat. So if you want to spawn 3 times a group, set it to 2 (1 shot + 2 added) INTERVAL FOR REPEAT - A delay between 2 consecutive spawns , if the condition are met. If not, the spawn will wait for condition to be TRUE, then spawn, then wait for interval duration, then check for condition... min 30 sec max 2 hours. FORMATION OF THE GROUP - As usual. Sometimes this setting is reinitialized to default wedge. I didn't identify why. So check twice before OK button and save scenario. BEHAVIOR - (or behaviour, sorry) Same as usual COMBAT MODE - same as usual SPEED MODE - As usual. same little problem as formation. Check twice. INSIGNIA - I hope that works fine everywhere... CODE FOR GROUP - Blank of any code (without {}). Passes parameters are <group> <<leader>, <vehicles of the group> . For example, just write: params ["_grp","_lead","_vehs"]; private _wp = _grp addWaypoint [<aPosition>,0]; _wp setWaypointType "MOVE"; _lead forceFlagTexture "\A3\Data_F\Flags\Flag_red_CO.paa"; {_x setFuel 0.2} forEach _vehs No bracket, just like this. BASIC TASK - can be: * Do Nothing (the preferred one of dumb AIs) * Attack nearest known enemy. So the group will start after an enemy knowledge acquisition. Not before. I hope I managed air assets for chasing air assets... I can't imagine infantry running after a jet. * Chase nearest enemy. Same as above but the position of nearest enemy is known (for spawning attack waves for example) * Attack nearest Player (known enemy) . The group must acquire the detection of a hostile player. * Chase nearest player (enemy). The group will start the hunting on player's (updated) position. * Defend this area. some SAD waypoints in the area of the group(s). known difficulties - Mods like Unsung or CUP or RHS (all in fact) requires a sharp attention for the name of the factions/groups but also Types... of groups. You can't imagine hundreds of names for stupid things like "infantry" "armored" "mechanized" ... That should be normalized, but not! - Too many mods, even non used by mission, but just loaded on server (so ticked), will affect the randomization for nuts, and lead to unwanted results like Arma or CUP units during Unsung play. know bugs all corrected so far To do list: - respawn without delay on whole group death - add a filter for mods... A lot of work. Enjoy! All feedback welcome. [RELEASED]

Allahu Akbar my friends, i present you an Zeus|Achilles addon which your community will love if they survive. This addon extends Achilles with 4 new modules all for the modern suicide bomber and terrorist. Carbomb Drop the module on a vehicle and make it a portable bomb, when you hear the mobile phone ringing its already too late. Carbomb KI Drop the module on a civilian and select the vehicle which the "terrorist" will sabotage. Remote IED Drop the module on a civilian near a road and let him place a IED Suicide Bomber Drop the module on a civilian to convert him to a portable IED, never forget they have maybe a deadman switch. Requirements: CBA_A3 ACE³ Achilles Notes: 3den Attributes currently removed Ace³ carbomb disarming will be included in a later update various function name changes Download: Steam Workshop Armaholic Reuploads are not allowed exceptions: Armaholic Functions: News,updates and more on my Discord. For mission makers Needs rework

So long story short i made a mod which retextures the NATO vanilla vehicles problem is, and ill try my best to explain it. If for example i just hop into editor play as a character but have not spawned ANY of the retextured vehicles in the map as soon as i log into zeus i simply just cant see the category made for those vehicles neither can i find them but if i go back to the EDEN editor and spawn a single vehicle from the category and then log in as zeus my retextures are suddenly available, i have no idea why and i have a slight suspicion my code is possessed. class CfgEditorCategories { class baseCat { displayName = "NATO Digital woodland"; }; }; class cfgVehicles { class B_MBT_01_cannon_F; class Digital_MBT : B_MBT_01_cannon_F { author = "Psyco"; scope = 2; scopeCurator = 2; side = 1; editorCategory = "baseCat"; faction = "BLU_F"; displayName = "Digital Merkava"; crew = "B_crew_F"; hiddenSelections[] = {"camo1","camo2"}; hiddenSelectionsTextures[] = {"\digital_retex_NATO_Armor\data\Merkava\body_CO.paa","\digital_retex_NATO_Armor\data\Merkava\MBT_Turret.paa"}; }; }; Heres a snip of my code Any ideas?

Altis Special Police Unit v1.50 by FoxFort Description: At the end of civil war in Altis, the Jerusalem Cease Fire of 2030 mandated the creation of an armed defence force to secure the sovereign territory of The Republic of Altis and Stratis, with that act Altis Armed Forces was born. But it was limited to have less then 1000 soldiers. In recent years, the on-going counter-insurgency operations in North-Western Altis resulted with worn down AAF military strength and with WW3 on the doorstep, the need to deal with insurgency and to increase overall security was a top priority. With active embargo on increasing the military strength. Altis government decided to form a Special Police Unit. The newly formed SPU consists only from current serving Altis police officers, who volunteered to server in area of counter-insurgency operation with hope of bringing order to chaos. New needed equipment for SPU was imported into country and the new 100+ strong SPU was formed. Wearing distinctive blue uniforms, SPU saw their first action in defence of Oreokastro. Features: Police Unit to boost defence of Altis from evil West and East 🙂 ------------------------------ Changelog: v1.50 - Added: Fieldpack in Green color, also replaces Fieldpack AT on Woodland AT class. - Added: Bonniehat in MC camouflage. - Added: PASGT helmet in Green-Olive camouflage (From Laws of War DLC). - Changed: All infantry classes now have randomized headgear, except Crew class. - Changed: Now Olive version of rangefinder is used instead of Sand version. - Tweaked: Color of MTV (GA Carrier Lite) Olive-Green camouflage. - Fixed: Default version of the mod, had wrong weapons magazines in cargo. - Fixed: Missing SPU Zafir and Rahim black versions in Arsenal. ------------------------------ Notes: - The SPU addon is "standalone", which means you don't need to download any other addon in order to use SPU. Now there are alternative weapons files included that require official Arma 3 DLC ownership. Use them if you wish, but you can use only ONE set of alternative weapons at the time. - Originally, new Hmmwvs have been imported from ArmA 2 into ArmA 3 by "Aplion", then further tweaked by me (FoxFort) for usage in SPU addon. - The new MI-35M is not finished, I should improve it eventually.. ------------------------------ Known issues: - The new MI-35M is not finished, expect improvement. - Jeeps and Mi-35M mostly have a proper metal hit effect, but dirt splash when hit is still present on some parts (WIP). ------------------------------ License / Disclaimer: Just by downloading and/or using my mod/addon you automatically accept and apply: - You are allowed to use my "Altis Special Police Unit" in your private or public missions and servers. - You are allowed to use my "Altis Special Police Unit" as part of your mod/addon as long as you make that your addon/mod requires to have my mods/addons installed and running at the same time as a seperated entities. - You are not allowed to alter or to extract my assests from any of my mods/addons and to release it to public as your own work. - You are not allowed to use all or parts of my mods/addons in order to intengrate it into your mod/addon, without making "Altis Special Police Unit" mod/addon as a requirement to be installed and run as a seperated entities. - You are not allowed to use all or parts of my mods/addons in order to make any kind of damage to my name. - You are not allowed to port my work into other games/mods without asking me. --(Basically, just do not steal my stuff and pretend that you made them.)-- ------------------------------ Required Arma 3 DLCs for Alternative Weapons: For "Alternative Weapons APEX AK12": You need to own APEX DLC: https://store.steampowered.com/app/395180/Arma_3_Apex/ ------------------------------- For optional "Alternative Weapons APEX SPAR": You need to own APEX DLC: https://store.steampowered.com/app/395180/Arma_3_Apex/ ------------------------------- For Optional "Alternative Gear - Contact DLC": You need to own Contact DLC: https://store.steampowered.com/app/1021790/Arma_3_Contact/ ------------------------------ DOWNLOAD LINKS: Armaholic ModDB Steam Workshop ------------------------------ Credits & Thanks: BIS, Aplion and Mickyleitor. ------------------------------- Video preview of the mod: ------------------------------- Screenshots:

Hello, does anyone know how to create the Zeus modules for the Zeus of Arma 3 Vanilla. I knwo how to create the modules for EDEN, but I don't see nothing for Zeus Modules https://community.bistudio.com/wiki/Modules Thx.

https://github.com/jakehekesfists/DMD_BuildingReplace

Hi All, I am looking for guidance on creating a cpp to support custom flag and billboard images that I have created for the prupose to include them in an addon. Any useful guides our information you could help me with? thanks :)

Update: Due to authors request. Link has been removed.

Hello, community! 🙂 I have tried to create a mod with units using Drongo's Config Generator. I know how it works and I have created some mods already. What I want to share is an issue when I made my last mod. I have used this mod: https://steamcommunity.com/sharedfiles/filedetails/?id=1124966491 for the uniforms and also Contact's Spetsnaz units, as my units should be Russians. I have tried the mod afterwards and only the uniforms are the CSAT vanilla (default) ones instead of the Russian variants. I have tried several times and I have got the same error every time, no matter if you units are from the F1 faction menu or the F2 groups menu. What could cause this problem? Thank you in advance! 🙂 🍻

Ok so I thought I understood this...I've packed several small mods before and I could load them just fine. However, I'm trying again for the first time in a while, following the exact same structure, and it's coming back telling me "file not found". I have the following as my file structure in my P: drive: P:\law\modName\addonName Within the addon folder I have included config.cpp with the following line, as per the Arma 3 samples, and the file basicdefines_A3.hpp also copied from the samples. #include "basicdefines_A3.hpp" At the moment this is the only thing in the config file not commented out. However when I pack this (without errors) and load it into the launcher (...Arma 3\@modName\addons\addonName.pbo), whilst loading it tells me it is unable to find the basic defines file. The same is also true of any other files I try to #include. This tells me I probably haven't referenced it correctly, but after a whole morning of googling and trying every conceivable iteration of file paths I've decided it's time to ask for help. Much appreciated, Law

Achilles Deprecation Notice Achilles is no longer under active development by the core dev team. Please check out Zeus Enhanced (ZEN) instead. Note that you can still create pull requests, which will be bundled and released as updates if accepted. Description Achilles is a gameplay modification for Arma 3. It expands the Zeus real-time editor with many new additions as well as provides bug fixes. Achilles started as an expansion to Ares mod, which was created by Anton Struyk. Achilles became the de facto successor to Ares at the point the latter was no longer updated. Achilles has already grown into a splendid project, but new additions are still to come! Table of Contents Features Language Localization Getting Started Installing Required Addons Incompatible Addons Optional Addons Other Zeus Addons Documentation Reporting Issues, Requesting Features and Changes How to Contribute Basic Steps Setting up Your Local Development Environment Add a New Module Add a Translation Authors Contact License Features Visual changes to the Zeus interface Tons of new modules: ACE Medical (e.g. heal, injury; also work in vanilla!) AI Behaviour (e.g. animations, garrison buildings, surrender) Arsenal (e.g. add/modify) Buildings (e.g. destruction, breachable doors) Development Tools (e.g. execute code, config/function viewer) Environment (e.g. advanced weather, earthquakes) Equipment (e.g. toggle tac light) Fire Support (e.g. artillery, suppressive fire) Objects (e.g. attach to, toggle simulation, IEDs) Reinforcements (e.g. spawn reinforcements on the fly) Scenario Flow (e.g. advanced intel, side relations) Spawn (e.g. custom compositions, smoke pillar, USS Freedom) Zeus (e.g. add/remove objects) Extended attribute window: Groups (e.g. careless, hold fire) Vehicles (e.g. cargo, pylons, garage, damage wheels) etc. New waypoint types: e.g. seek and destroy, paradrop, sling load Hotkeys: Copy/past units including the full loadouts Remote control etc. Customizations: Settings (e.g. faction filter) Language Localization Achilles is available for the following languages: English French German Japanese Russian Simplified Chinese Traditional Chinese If your language is not on the list, the English localization will be used. We welcome any new translations (check out How to Contribute). Getting Started Below is what you need to know to get Achilles up and running: Installing Required Addons Incompatible Addons Optional Addons Other Zeus Addons Installing You can download Achilles from: GitHub Steam Workshop Armaholic If you are not familiar with installing ArmA 3 addons, check out the Armaholic installation guide. Required Addons Achilles requires: Arma 3 Community Based Addons A3 (CBA_A3) Incompatible Addons Addons that you should not run when you use Achilles: Ares Optional Addons These mods below are required for certain features (e.g. fast-roping): Advanced Combat Environment 3 (ACE3) Advanced Rappeling (AR) Task Force Arrowhead Radio (TFAR) Other Zeus Addons A list of other Zeus mods that are not required, but nice additions: Zeus/Eden Compositions (ZEC) Zeus/Eden Compositions for CUP (ZECCUP) Zeus/Eden Interiors (ZEI) Documentation Check out the Achilles Wiki and the Achilles Tutorial Series on YouTube. The documentation is rather limited at the time and thus, you will certainly have questions. We will gladly answer them on our Discord server. Reporting Issues, Requesting Features and Changes Please use our Issue Tracker for these kinds of purposes. In the case of a bug report, please only use a minimal set of mods (i.e. only use other mods than the required ones if they are clearly related to the issue). How to Contribute We always welcome contribution to the repository and thank you for your work! We will update the list of contributors. What you need to know: Basic Steps Setting up Your Local Development Environment Add a New Module Add a Translation Basic Steps Fork the Achilles repository Set up your local development environment Do your stuff Create your pull request And then we will have a look at your work! Setting up Your Local Development Environment Clone your forked repository Set up your addon builder (either get Hephaestus or use the AchillesAddonBuilder.bat in the repository) Add a New Module A good starting point for your new module is the custom module framework. We will gladly help you to port your custom module to Achilles (message us on our Discord server). Add a Translation You have to edit the stringtable.xml. The basics about string tables can be found on the Bohemia Interactive Wiki. If you don't want to edit the file with a text editor, you can use a dedicated tool such as Tabler. Authors Check out the list of contributors. Contact Find us on our Discord server. License Achilles is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license.

I can't get the hull of my boat to be in the water. It just sits above the surface. Can you help me?

Hey folks, I am currently developing a Coast Guard Addon for Arma 3. I already modded a Coast Guard Faction and Uniforms as well as Boats and a Helicopter, and now I want to add some special Objects. A rescue basket and a life raft. I am pretty good at making 3d Models of technical objects so that was no challenge. However I am not really good at scripting configs for Arma 3 and working with the Object Builder. So I could use your help. Here is a model of the rescue basket I made https://steamcommunity.com/sharedfiles/filedetails/?id=1862964052 I was able to implement it into Arma but I need to add some features and solve some problems with your help. Features I have to add: -basket floats on water (implemented) -basket can be slingloaded to a helicopter (implemented) -basket has 2 passenger "seats" one for the survivor sitting in the basket and one for the rescue swimmer hanging on the side of the basket (implemented) -basket has strobelights for night operation (not really implemented) -lights can be toggled Problems: -basket is static, it won't fall down if placed in the air (fixed) -i dont know how to get textures on the basket (worked around) -basket doesnt move if a vehicle crashed into it (fixed) -crew view position is not where its supposed to be -sling loading behaves odd -light sources don't relly emit light to the environment Basically I want the basket to be a Boat which can't be driven because it has no motor. This is the current config of the basket class cfgPatches { class Rescue_Basket { units[] = {"Rescue_Basket"}; weapons[] = {}; requiredVersion = 0.1 requiredAddons[] = {}; }; class Life_Raft_8 { units[] = {"Life_Raft_8"}; weapons[] = {}; requiredVersion = 0.1 requiredAddons[] = {}; }; }; class CfgVehicles { class Boat_F; class Rescue_Basket : Boat_F { side = 1; scope = 2; faction = "Coast Guard"; model = "\Coast-Guard-Objects\Basket.p3d"; slingLoadCargoMemoryPoints[] = {"SlingLoadCargo1","SlingLoadCargo2","SlingLoadCargo3","SlingLoadCargo4"}; displayName = "Rettungskorb"; }; class Life_Raft_8 : Boat_F { side = 1; scope = 2; faction = "Coast Guard"; model = "\Coast-Guard-Objects\LifeRaft8.p3d"; slingLoadCargoMemoryPoints[] = {"SlingLoadCargo1","SlingLoadCargo2","SlingLoadCargo3","SlingLoadCargo4"}; displayName = "Rettungsinsel (8 Personen)"; }; };

Hi everyone, hi need help, i want to put in safe my script in my Altis Life server to avoid script stealing, I wanna to create a addon like life_server and put my script there, but i dont know how to do that, please, any can help me?

Work in Progress (v0.8) What is CoopR? The abbreviation CoopR resolves into Coop Roleplay. These two keywords are leading the whole idea of this modification. CoopR Mod is a gameplay overhaul. Combining coop gameplay with interesting yet not immersion-killing roleplay game elements. CoopR will come in two different release systems. The first to be published is the CoopR Light coop gameplay enhancement. It can be described as a subset of features that passed quality assurance by bringing proper gameplay enhancements that do not have any dependency to other addons of the CoopR Mod ecosystem. The other release is the CMF (CoopR Mission Framework). This framework will provide a library of editor modules and scenario attributes to create multiplayer missions that redefine ArmA3 gameplay by a large package of new immersive features. Additionally the integration of popular modifications like ALiVE and ACE3 will push the feature list even further. The CMF will be officially implemented by CoopR and is planned to run on multiple game servers. The collection of those servers is defined under the CoopR Combat Theatre term. A “theatre” defines the lore multiple servers are running under. Technically players can transfer their characters and squads only between servers where the threatre is the same. There is no way of transfering a World War 2 threatre character into a NATO war theatre. CoopR Light CoopR Light’s primary goal is to extend the gameplay of coop multiplayer squads. It is a small subset of the whole CoopR mod idea. When the development of CoopR Mod started it was clear that this modification will take at least two years to implement all planned features. As time went by the amount of feature ideas grew and therefore the release date was pushed back further into the unknown future. To this date the CoopR team managed to develop a working base with a good amount of core features. We realized that there is a basic feature set ready to be released. We call this set the “CoopR Light” release. The reason to release this light version to the community is to start testing the early state of the modification. We expect to receive hands-on feedback and suggestions that help adjusting the development process. Reported bugs will be brought into the development of CoopR and fixed in future releases. The following conditions need to be met so an CoopR addon is a candidate to be released in the CoopR Light release: No dependencies to other Non-Light addons Adds striking enhancement of coop gameplay Will not require a wipe of any persistence data CoopR Mission Framework The CMF (CoopR Mission Framework) will provide a vast variety of editor placed modules, scenario attribute configurations mission configurations. The CMF will also offer a library of script functions to publish an API for other addons or mods. This is what the framework will bring to the customization point of view. With CMF you can build a completly new type of coop missions. One core feature is the RPG addon. It allows players to create characters with perks and role specifications. These characters are persisted and accessible between different mission created by the CMF. This bring another gameplay addition to coop missions - progress. Characters can increase their skills and “farm” their equipment. Incapacitation is not a trivial thing anymore. You can lose access to your character for a long time or even lose him completely due to permadeath situations. But the RPG system is not at all the only thing coming with the CMF. To shorten it up here is a short list of features that are either nearly completed or work in progress: Character RPG System "Deployment Life" Simulation System Local Persistence & Web Persistence (CoopR HQ) Perk System Role Skill System Temporary Camp / Shelter System Supply Request System Personal Storage / Barrack System Recon Mission System CoopR Webapp / Mobile-App Character Management Extended Squad System many more in concept... Recruitment! The CoopR Mod team is looking for some fresh meat/veggie. Here are some positions we are in need for: SQF Developer (All Skill Levels) ArmA3 Extension Developer Game Concept Designer Vue.js Developer (All Skill Levels) 2D Artist Feature Roadmap Wiki WIP Find us CoopR Youtube Channel @cooprmod Instagram Support us on Patreon! Contribute on Github! Have a chat with us on Discord

M2 Slammer Firepower Upgrade Project Current version: v6.1 Hello, I have created a little config mod with adds a new tanks based on the M2A4 Slammer tank for BLUFOR. It's my first mod like that so not everything works perfectly, so if you have any suggestions how to fix, or improve, certain elements, feel free to weight in. It was done mostly to figure out how to properly edit the config files. THIS MOD DOES NOT CONTAIN NEW MODELS (sadly) [FLUFF] NATO found the existing M2A1 firepower to be lacking. To fix this issue the "Firepower Upgrade Conversion Kit" has been developed for the M2A4 Slammer with was already upgraded with the TUSK (although M2A4 only had 105mm main gun). Along with the improved armor of the M2A4 variant, the additional firepower of the M2A6 is something to be respected. It can still carry troops as well, making it a unique jack-of-all-trades armored fighting vehicle. However, recent high intensity conflicts have shown that a highly trained and motivated enemy, as opposed to usual goat pushers NATO likes to stomp on, can withstand suppression from .50cal MG's. To rectify this, two further modifications to the M2 Slammer has been designed, based on the successful M2A6 Firepower Upgrade; the M2A7 and M2A8. For both, the gunner's 12.7mm coaxial machine gun has been replaced with 20mm autocannon, with has much bigger shock & terror impact on the infantry. The "Designated Infantry Combat Killer" variant, the M2A7, sees commander with 20mm Grenade Machine Gun instead of usual .50cal. The 20mm GMG have been proven useful in dealing with the infantry in cover. The M2A8 is a slight variation of the M2A7. Not happy with decreasing the long range engagement capabilities of the commander's weapon system in M2A7, the NATO engineers came up with the idea of mounting and "Advanced Suppression System", in a form of an 20mm autocannon, for commander's use. While the cannon lacks some of the splash damage 20mm grenades had, it allows for a long range engagements, retains most of the shock value, and can serve as an anti-air weapon. [/FLUFF] Features 4 new Slammer variants: M2A6, M2A7, M2A8 and M2A9 The main features of M2A6 Slammer Firepower Upgrade:new standalone tank for BLUFOR (just for compatibility's sake), the M2A6 improved armor of the M2A4 variant M2A6 can still carry troops enhanced optics for both, commander and the gunner. 2 new extra zoom levels and the commander gets an additional ultra wide default zoom (old one is still included) FLIR modes changed to black and white 120mm main gun ability for main gun and gunner's MG to lock onto ground targets (MG can lock onto air targets as well) with impact point calculation and automatic range and leading correction for moving targets 12.7mm coaxial machine gun for the gunner (Ma Deuce still got it) with 3x500rnd magazine with ability to lock onto air and ground target, impact point calculation and automatic leading for moving targets commander's MG now has impact point calculation ability to launch guided anti-tank and anti-air missiles, in both wire guided as well as fire-and-forget modes commander has a fully functional laser designator available for designating targets for other M2A6's, aircraft and such commander can fire 82mm mortar rounds, 8 shells in total AI gunner, once locked onto laser designated target, keeps following it allowing for guiding really tricky shots as a commander the M2A6 AI crew is aware of laser designated targets and will engage them, meaning UAV or infantry designation for the M2A6 is possible improved the engine power so the tank is more nippy and feels better to drive The main features of M2A7 Slammer Firepower Upgrade Cannons Infantry Terrorizer:further firepower enhancement of the M2A6 all of the advanced M2A6 features (laser designator, CCIP, 82mm mortar, etc.) 12.7mm coaxial MG has been replaced with a 20mm autocannon commander's MG has been replaced with 20mm Grenade Machine Gun The main features of M2A8 Slammer Firepower Upgrade Cannons Advanced Suppression:further firepower enhancement of the M2A6 all of the advanced M2A6 features (laser designator, CCIP, 82mm mortar, etc.) 12.7mm coaxial MG for both commander and the gunner have been replaced with a 20mm autocannons The main features of M2A9 Slammer Firepower Upgrade 140:further firepower enhancement of the M2A8 most of the advanced M2A9 features (laser designator, CCIP, etc.) commander loses his mortar no passenger capacity in exchange for more ammo new 140mm main gun with ammo: APFSDS, HE and FAE. The new gun can still fire missiles new 140mm main gun has a 4 shots autoloader with 5.5s delay between each shot and 20s magazine reload time new 140mm ammo: a thermobaric rounds (140mm FAE). They have pretty low damage, but they have huge splash radius less nippy then the other variants due to added weight of the bigger gun and ammunition (it just doesn't get the improved engine other variants got, it behaves like vanilla M2A4) Classnames B_MBT_01_FU_F - M2A6 classname B_MBT_01_FUC_IT_F - M2A7 classname B_MBT_01_FUC_AS_F - M2A8 classname cannon_120mmFU - new gun classname cannon_140mmFU - new 140mm gun classname mortar_82mmFU - commander's mortar classname HMG_127_FU_Hull - gunner's machine gun classname HMG_127_FU_Commander - commander's machine gun classname 20mm_cannon_FU_Hull - M2A7 & M2A8 gunner's autocannon classname GMG_20mm_FU_Commander - M2A7 commander's grenade machine gun classname 20mm_cannon_FU_Commander - M2A8 commander's autocannon classname ultra_Wide - new, additional, minimal zoom level for commander extra_zoom1 - extra zoom classname extra_zoom2 - new additional maximum zoom classname Sh_140mm_APFSDS - 140mm APFSDS shell classname Sh_140mm_HE - 140mm HE shell classname Sh_140mm_HET - 140mm FAE (thermobaric) shell classname 4Rnd_140mm_HE_shells - 4 round magazine of the 140mm HE shells classname 4Rnd_140mm_APFSDS_shells - 4 round magazine of the 140mm APFSDS shells classname 4Rnd_140mm_HET_shells - 4 round magazine of the 140mm FAE shells classname Known Issues 1. I have created a new gun based on vanilla 120mm, the classname is "cannon_120mmFU", its rather important as some script might require the gun classname to function properly (smart tanks for example). Also the model of the M2A4 is unchanged, meaning the gun still has 105 model, but it's not really all that noticeable. 2. For some reason the commander's weapons only get lead indicator when target is locked in by the gunner and for that target only. I think it's some engine limitation. 3. The AI likes to fire AT missiles first, so M2A6 only gets 2 AT missiles 4. Sorry, but this one is rather janky. I couldn't get the artillery computer working for the commander, it only worked for gunner and he didn't have the mortar available to him. You will need to eyeball it when firing. Also due to how turrets and such work, the mortar shell is fired from the commander's MG. 5. It's pretty random what weapon AI will use to fire at the laser marker, they like to fire AT at it. Also, they do not always spot the marker, so moving it around their field of view might get their attention. 6. With the new autocannons AI REALLY likes them for some reason, so far it may fire them at targets like APC's and such. If anyone knows how to limit that: drop an info. 7. The new CCIP has some issues with ACE, if you use the ACE FCS to range the target the CCIP will NOT be corrected for new range. This more of ACE issue with Arma 3 then with my mod, I'm sure it wil be fixed someday. Changelog v6.1 - current version * automatic leading and rage correction for the gunner returns * 140mm gun changed to be more like a World of Tanks autoloader: 4 shots in the magazine, 5.5s delay between shots, 20s magazine reload * lowered pitch on the 140mm firing sound to make it sound more powerful * added muzzle flash to 140mm (just artillery firing effect didn't have that for some reason) * added magazine reload sounds to 140mm * nerfed splash damage of the 140mm FAE (thermobaric) round, from 50m to 30m * changed ammo composition for the A9 with 140mm, now it has 4 round magazines with overall ammo count same as before, more or less * AT missile magazine to be bigger v6 * new variant the M2A9 with a new 140mm main gun. The new gun is bigger so commander lost his mortar in this variant and the passenger compartment was converted into ammo storage. The added weight makes the M2A9 slower then the other variants (it just doesn't get the improved engine other variants got, it behaves like vanilla M2A4). It still gets the 20mm autocannons as secondary guns * new 140mm gun gets new ammo as well with better stats then 120mm shells * new 140mm FAE shell. This thermobaric round has a low damage, but huge splash radius, ideal for taking out large groups of infantry * improved the engine on the M2A6, M2A7 and the M2A8. The tanks feels a bit more nippy especially on slight inclines. * lowered artillery charge of the commander's mortar to 30%. 50% made it shoot too far and it was hard to lob shells over close obstacles * removed the automatic leading correction for gunner. I discovered it could mess with your aim, the new lead indicator is shown instead, same as with commander v5 * new additional zoom levels for commander and the gunner. The commander also gets a new extra wide zoom level * FLIR modes for commander and the gunner changed to black and white * commander's mortar: reload time increased to 6 seconds (from 1.8), artillery charge dropped to 50% (from 70%) * 20mm cannons got another slight buff to RoF (still slower then 20mm GMG) * reduced magazine number for 20mm cannons and 20mm GMG, removed 1 magazine each v4.3 * fixed an issue in with commander's weapon systems were automatically corrected for targets aimed by the gunner. Now commander only gets target lead indicator, so he can fire at other targets without aim being messed up. v4.2 * fixed some of the 82 mortar issues: removed 2 firing modes so you only have 70% artillery charge, now you only need to press button once to change from mortar. Removed firing effect from the main gun * fixed AI sounds for 20mm cannons, now they are same as player's * 20mm cannons got a tiny RoF buff * decreased the amount of ammo for v4.1 * fixed the AI rate of fire and sounds for autocannons, hopefully without braking it in other ways v4 * two new variants for the Slammer, M2A7 and M2A8. Both now sport 20mm coaxial canon. The M2A7 is the infantry killer variant with 20mm GMG for the commander. The M2A8 has 20mm cannon for commander instead v3 * M2A6 now has it's own custom version of the .50's for both commander and the gunner. Both sport impact point prediction and gunner's MG can track air targets as well as automatically give lead to locked moving target. Those are custom in order to not create any possible compatibility issues * cleaned up config a bit v2 - fixed ballistic computer prediction, for now main gun can only lock onto ground targets, AA missiles work as they did v1 - initial release Download (Mediafire) Armaholic mirror Play withSIX mirror

ello, community. I have created my second mod using Drongo's Config Generator. There was no problem creating the first one and I have learned to create such mods and files very quickly. I did everything the right way - I created my units and added Drongo's generator module in the editor, which created the .cpp file. I converted it into a .PBO file successfully using the Addon Builder. After that I uploaded the .PBO file and created a mod, launched it with the requirements, but an error occurs: File Addons\ config.cpp, line 2: /cfgPatches/: '-' encountered instead of '{' What could be wrong? I have opened the file and the '{' was there instead of '-', so it was OK. Here's the whole file's content: Thank you in advance!

Spetsnaz SSO v1.30 By FoxFort Description: Unknown camouflage units have been spotted on island of Altis, they appear to wear russian made equipment and they have no markings of any kind. No one knows for sure who there are and what are they doing there, but they appear to be working with AAF. The locals have a nickname for them, they call them: "Little green man". ------------------------------ Features: Adds Spetsnaz SSO look-alike. ------------------------------ Usage: In Editor, on AFF side, you can find them separately under "Spetsnaz SSO". ------------------------------ Notes: This was my first addon that I made for ArmA 3 and I've even forgotten about it, so here's a quick fix in order to bring it into working condition (again in 2018 & now in 2019 LoL). In case you do not own APEX DLC, you can still play. AI will use APEX AK-12s, but you will have to use a different weapon. ------------------------------ License / Disclaimer: Just by downloading and/or using my mod/addon you automatically accept and apply: - You are allowed to use my "Spetsnaz SSO" and "FoxFort Camo Pack" in your private or public missions and servers. - You are allowed to use my "Spetsnaz SSO" and "FoxFort Camo Pack" as part of your mod/addon as long as you make that your addon/mod requires to have both of my mods/addons installed and running at the same time as a separated entities. - You are not allowed to alter or to extract my assests from any of my mods/addons and to release it to public as your own work. - You are not allowed to use all or parts of my mods/addons in order to intengrate it into your mod/addon, without making "Spetsnaz SSO" and "FoxFort Camo Pack" mods/addons as a requirement to be installed and run as a separated entities. - You are not allowed to use all or parts of my mods/addons in order to make any kind of damage to my name. - You are not allowed to port my work into other games/mods without asking me. --(Basically, just do not steal my stuff and pretend that you made them.)-- ------------------------------ Changelog: v1.30 - Added: IR Strobe Grenade to all soldiers. - Changed: All soldiers now use Russian Radio Protocols. - Changed: All soldiers now have mix of Euro, Asian faces. - Changed: Heavy AT for desert squad now use brown version. - Changed: RPG-42 Green texture changed to new vanilla A3 one. - Changed: All MRCO scopes on AK-12s have been replaced with ARCO AK. - Changed: All NV Goggles have been replaced with new Compact green NVG. ------------------------------ SCREENSHOTS: ------------------------------ Requirements: - FoxFort Camo Pack - APEX DLC ------------------------------ DOWNLOAD: MODDB ARMAHOLIC STEAM ------------------------------

YouTube Advert: Who are we? Zeus Community, an open community which has been playing Arma since the OFP days in 2001. Our Teamspeak server is our primary home with more information available via our website, forum and Discord channel. Links provided below. What should I expect on your server? We strive for Milsim oriented gameplay. In the hierarchical command structure, players are expected to follow the orders of their superiors and take responsibility of their subordinates. Communication and teamwork is key. Lone-wolfing, purposely ignoring commands, and other selfish behaviours will not be tolerated. We do employ some basic Standard Operating Procedures (SOPs) and radio procedures for the sake of efficiency but nothing overly complex which can't be understood quickly while playing. We play mostly cooperative (PvE) missions at platoon scale (around 30 players) though we have been known to play Team vs Team (PvP) missions on occasion. How many ArmA 3 servers do you run? Three main game servers: A “vanilla” public server (#1), an “addon” server (#2), and a "CDLC" server (#3). The vanilla public server is open to anyone interested in milsim gameplay, experienced or new, as long as you don’t break server rules of course. For the public server, there is not a mandatory mod requirement though we do often play missions which require official DLC such as Apex for the Tanoa terrain. However, it is strongly recommended that players to connect to our Teamspeak server (even if you don't have a mic) since we use Teamspeak for pre-mission briefing, post-mission debriefing, and on-mission squad comms (instead of group/green channel). We also recommend that players install our optional custom modpack called "ZClient" which includes very useful client-side mods such as ShackTac HUD (see Info Repo link below). On the other hand, the addon server requires all players to have a working mic and installation of our custom addon server modpacks which includes gameplay enhancing mods such as ACE3, ACRE 2, RHS, additional terrains and more. It is recommended that newcomers try out our vanilla public server before considering moving on to our addon server where gameplay is slightly more hardcore (i.e. always revive vs permanent death). The CDLC server can be considered a hybrid of the previous two servers mentioned where we play most CDLCs (e.g. SOG Prairie Fire, Global Mobilization, Western Sahara) in a weekly rotation. Mod-wise, ACRE2 is required (as well as any necessary CDLC-ACRE compatibility mod if using Steam Workshop mod version) but other than that, all that is recommended is to also run our optional modpack mentioned earlier "ZClient". What times do you play? Zeus Community #1 Public: Gamenight every Sunday, start 18:30 UK time (GMT/BST) Zeus Community #2 Addon: Gamenight every Saturday & Wednesday, start 18:30 UK time (GMT/BST) Zeus Community #3 CDLC: Gamenight every Thursday, start 18:30 UK time (GMT/BST) Why should I choose Zeus Community? Milsim gameplay but without the role-playing fluff. While the missions we run on our servers do employ a hierarchical command structure, the community itself (outside of gameplay) does not have player ranking, role whitelisting, or any other unnecessary RP fluff like some other milsim communities. No need for "Sir! Yes sir!". No mandatory training or minimum attendance required. We are an open community so we don't punish players if they happen to have a busy life and can't commit to playing games on a regular basis. We only ask that you don't slot into mission critical roles (e.g. squad leader, pilot, etc.) for a mission if there is a reasonable chance that you may have to go AFK for significant periods of time. Also, although we do employ basic SOPs, radio comm procedures, and we do organise optional training sessions, we don't require newcomers to undergo mandatory training before they can play. Just listen to your leaders, follow the example of more experienced players and you will quickly familiarise yourself with how we operate. In-community developed, custom missions. Using the 3den Editor tool, 99% of the missions we run on our servers are developed by the community, for the community. While we do allow our community’s developers creative freedom, we still maintain quality standards for our missions. Do note that, despite a coincidence in the name, we actually rarely play Zeus Game Master missions (our community name predates ArmA 3's ZGM gamemode). High frequency of brand new missions to play. Most milsim communities are stuck with a relatively small pool of missions to replay for months where new missions are produced on an infrequent basis. Our community on the other hand, benefits from a combined pool of around 600+ missions and produces an average of 5 brand new missions across both servers each week for the community to play. Mission diversity. Unlike many other milsim communities, we don't limit ourselves to particular factions, equipment, vehicles or mission objectives. In one mission you may be a guerrilla fighter with limited equipment tasked with ambushing an enemy convoy, and then in the next mission you may be a tank crewman in a combined arms scenario with CAS and artillery support. Even revive or respawn mechanics (or lack thereof) can differ between missions. Diversity is the spice of life. Servers Zeus Community #1 Public - IP address: 185.103.96.3 Port number: 2302 Zeus Community #2 Addon - IP address: 185.103.96.3 Port Number: 2310 Zeus Community #3 CDLC - IP address: 185.103.96.3 Port Number: 2320 Links Teamspeak: teamspeak.zeus-community.net Discord: https://discord.gg/v6yng8p Steam Group: https://steamcommunity.com/groups/ZeusCommunity Website: https://zeus-community.net/a3/ Forum: https://zeus-community.net/a3forums/index.php Information Repository: https://goo.gl/mLQgP5 Questions? If you need more info, our Information Repository (link above) provides extensive information and tutorials. Also, feel free to message me if you have any questions or queries.

Replacing weapons with Airsoft Guns and Game system. Current version 1.4 Steam Workshop •add 15 weapons. •Three game mode systems. •ArG Weapons Box. •gamer units and groups. •HitCall System. •TimeCounter operation Items. •Kill Count operation Items. •Capture The Flag Operation Items. (WIP) --Ver1.4 Changelog-- Add •GameMaster Menu.--Ctrl + Shift + Y is the default key to open. Key setting is possible. •Capture The Flag Operation(Stable). •Combo starter (multi-operation compatible). Change •start music can be selected from the ArG Game Setting Module or GameMaster Menu(27 songs). •To the new work which made the sample mission correspond to Ver 1.4. Remove old missions. Delete •TimeCounter Operation Call Ready(Blue) •TimeCounter Operation Call Ready(Red) •kill Count Operation Call Ready(Blue) •kill Count Operation Call Ready(Red) Fix •Lots of small fixes .... •Works on single player, listen server, dedicated server. •Include sample mission file(@ArG_Core\optional_files\Missions). [For the mission editor] 1.Place markers on the map that will be the game area. Marker name is "GameArea" 2. [case of “Kill Count operation”] Place GameStart Call Ready[Blue] and GameStart Call Ready[Red]at the start positions of west and east respectively. [case of “Time counter operation”] Place GameStart Call Ready[Blue]and GameStart Call Ready[Red]at the start positions of west and east respectively. And place the time counter box and the buzzer sound source anywhere. [case of “CaptureTheFlag operation”] Place GameStart Call Ready[Blue]and GameStart Call Ready[Red]at the start positions of west and east respectively. And place the Capture the flag and Place markers of variable names "westHQ" and "eastHQ" anywhere. 3.If you want to make it possible to recover after a hit, place a revive object at each start position or place an ArG Gamer Medic unit with revive ability 4.You can change the mission details with "Game Setting" Module. ※The hit call system works within the range of the marker "GameArea" & the game start. The game start variable is InGame = 1; PublicVariable "InGame"; ※If you go out of the game area for about 10 seconds after the game starts, it will be treated as a hit. You can return to the game if you revive.

So i recently made a retexture of a uniform following a tutorial, at first i used the config that the tutorial used and then one that i found on the internet. But it doesn't work i was wondering if someone could help me out here. Note - i do not know how to make configs or how to code.

[FOX] Ambient Airspace Heyo, [FOX] Ambient Airspace is a modified version of my ambient flyby script. Features: Auto initialization, load the addon and done Random CIV flyby in ANY mission (default every 15 min / 1 vehicle) Support for RHS,CUP and for custom classes via patch or script Singleplayer | Localhost or use it only on server ( clients dont need it ) WKS-> https://steamcommunity.com/sharedfiles/filedetails/?id=1617724896 For settings check out https://github.com/Skullfox/fox_ambient_airspace

Hi I am new to Arma 3 modding scene, but I have previous experience with another engine. I am wondering where to start - and what resources are available. Such as rigging for clothing and units, but also vehicles mainly tanks. If anyone could point be to tutorials or even some sample resources to use, that would be appreciated! Thanks for any advice!