Read the instructions carefully. Before leaving any questions regarding DMS, please read through the DMS "config.sqf"; the majority of the questions we receive are answered (directly or indirectly) by the config.
Defent's Mission System (DMS) is written from the ground up to be an efficient, easy to install, and vastly customizable mission system for the ArmA 3 Exile Mod.
However, creating such a mission system takes a lot of time and testing. We (the authors of DMS) are not perfect, and as a result, there may be bugs, glitches, and/or errors within DMS. We appreciate your co-operation in identifying and resolving such issues to improve DMS; however we are not liable for any issues resulting from the usage of DMS on/by your server. We are also not liable to help you in resolving any issues that may arise.
You are welcome to port DMS or any of its functions for any other mod or (legal) purposes. For more information read the License Overview below:
This work is protected by Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). By using, downloading, or copying any of the work contained, you agree to the license included.
DMS by Defent and eraser1 is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://github.com/Defent/DMS_Exile.
The following overview is a human-readable summary of (and not a substitute for) the full license.
Share — copy and redistribute the material in any medium or format.
Adapt — remix, transform, and build upon the material.
Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
NonCommercial — You may not use the material for commercial purposes.
ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation. No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
Please search the DMS thread before asking any questions DMS will work "out-of-the-box" for almost any map. You have to keep in mind that if the map is too small (such as Stratis), then you will need to reduce the Mission spawn location settings. Also, for especially hilly maps (such as Panthera), you will need to reduce the Minimum surfaceNormal (the config value is automatically adjusted for some maps. You can check the map configs to see the adjusted config value overwrites).
It is highly recommended that you add
!="(_this select 0) execVM \"\A3\Structures_F\Wrecks\Scripts\Wreck_Heli_Attack_01.sqf\""
at the END of the line that starts with "7 exec" in scripts.txt (if it exists). Here is the pastebin.
AND:
!="_v)} do {\n_posV = getPos _v;\n_smoke1 = \"#particlesource\" createVehicleLocal getpos _v;\n_smoke1 attachTo [_v,[0,0,0],\"engine_effe"
after "7 createVehicle"
- Download the a3_dms folder
- Edit the config.sqf to your preferences.
- Pack the a3_dms folder with a PBO tool (PBO Manager, Eliteness, or the Arma 3 Tools suite)
- Put the generated PBO in your
@ExileServer\addons\
directory. It should be alongsideexile_server.pbo
andexile_server_config.pbo
.
## infiSTAR: * If you want to enable "VehicleWhiteList_check", make sure to add ```'O_HMG_01_high_F'``` to ```_VehicleWhiteList```, as well as any other vehicles you add to DMS that are not whitelisted.
If you are using Vilayer or some other GameServer hosting service, and/or the above steps did not work, then follow these instructions:
- Create a new folder called @a3_dms in the root ArmA 3 folder.
- Create a subfolder called "addons".
- Place the "a3_dms.pbo" in the "addons" subfolder.
- Edit your startup parameters/modline to include "@a3_dms". For example:
-serverMod=@ExileServer;@a3_dms;
If you're having any issues with DMS, check your RPT for errors and make sure PBO is packed correctly by unpacking it and ensuring the folder structure is "\x\addons\a3_DMS...".
If you can't figure it out, leave a post on the DMS thread on exile forums. Make sure to include your RPT, config.sqf, as well as any changed files. Please use pastebin, spoilers, or something similar; DO NOT PASTE EVERYTHING DIRECTLY INTO THE POST (without putting it in a spoiler)
DMS does not currently support headless client. Do not attempt to use HC with DMS unless you know what you are doing.
- Defent from NumenaDayZ.
- eraser1 from TrainwreckDayZ.
- secondcoming from ExileYorkshire.
- Zupa for suggestions and coding help.
- Nawuko for catching a silly mistake :P
- shaworth and KawaiiPotato for making the README all nice and pretty :)
- maca134 for M3Editor Stuff
- Darth Rogue from SOA for the awesome base for the first DMS static mission :D
- William from Refugees of the Fallen for the amazing slums static mission base and ideas :)
- DONKEYPUNCH for everything on the February 17th 2016 commit ;)
- MGTDB for the plethora of fixes, testing, and all-around doing our work for us :P
- Everybody's feedback on the DMS thread on exile forums
- William from Refugees of the Fallen
- JamieKG from Eternal Gamer
- Valthos from The Altis Project
- Flowrider from Optimum Gaming
- CEN from ATD Gaming
- Regularly update marker position.
- Implement function(s) for AI pathing.
- Spawn AI that are meant to "hunt" individual players.
- Air/Land AI Vehicle Patrols
- Spawning in a trader on mission completion (Trillseeker82).
- AI will still be offloaded to clients (ideally); strictly DMS functions will be handled by the HC.