Skip to content

Latest commit

 

History

History
66 lines (55 loc) · 4.14 KB

README.md

File metadata and controls

66 lines (55 loc) · 4.14 KB
Raw

DUWS-R

ArmA 3 Dynamic Universal War System - Rebirth

New Team Members Welcome

What to fix something broken or add a new awesome feature to DUWS-R? Start by looking at the Developers guide located on the wiki! You can find all the information from how to get started through getting your code into the official builds. We appreciate all the help out there from the community and can't wait to have the next great release!

Copyright / License

Click here for License Info. You are free to release any modded/modified version of the DUWS-R, as long as you put a link pointing to the original DUWS-R.

Disclaimer

The team is not responsible if this mission destroys your computer, or if a ninja kills you with karate while doing a back flip while you are playing this mission. A big shout-out goes to the original DUWS for the great starting point! This project was forked from the work provided at http://forums.bistudio.com/showthread.php?160117-SP-Dynamic-Universal-War-System-(DUWS-alpha0-1)

Overview

DUWS-R randomly generates a campaign with enemy zones to capture. You can also choose to manually place your HQ and enemy zones to make your own unique campaign. The key of this mission is to have maximum replay-ability, where the player can setup their own campaign or let the DUWS-R create everything randomly for them. You can play with the DUWS-R on any island you want, you just have to rename the .pbo file.

Quick Start

Put the .pbo inside your Steam\SteamApps\common\Arma 3\Missions and/or Steam\SteamApps\common\Arma 3\MPMissions folder. When you are asked to choose the campaign settings, just use the default parameters until you are ready to start changing the settings.

Required Add-ons:

None! You can play ArmA III vanilla or use all the add-ons you want: islands, weapons, gear, etc... Note that the DUWS-R will not show add-ons that adds BLUFOR units/vehicle, since they are added by hand. However, add-ons that add OPFOR vehicles will be used, since OPFOR vehicles are taken directly from the cfgVehicles classes.

Using the mission on another island

Just rename the .pbo to the extension of the other island. That's it! Consideration should be taken when doing this as some islands cause more load when generating zones and other items due to the terrain being sloped. Most terrain is fine but islands such as diaoyu can me it difficult to play

  • Example: DWS.stratis.pbo >> DWS.chernarus.pbo

Manually placing zones

After a location for the HQ has been selected the player will be prompted with a dialog with various options. Two buttons will be available at that time. START-R and START-M allow you to place enemy zones randomly or manually respectively.

Features

  • Play the way you want:
    • Play as a lone wolf or as a special forces team, using support assets and gadgets and perform side missions
    • Control your personal squad of troopers and fight against the OPFOR
  • Pretty much every location is randomly generated on the map, from the HQ to enemy zones and side missions.
  • Random side missions, with randomly generated names
  • Play the DUWS-R on any island you want to.
  • VAS by Tonic (Armory)
  • Several support options to unlock (UAV, Arty, Personal FLIR, VAS, ...)
  • You can define the HQ location yourself and the enemy zones, or just the HQ and let the DUWS-R generate the zones automatically. You can also let the DUWS-R create everything by itself. Basically you decide the level of randomization.

Known issues

See our issue list on GitHub for issue we currenty know about.

Credits / Thanks

  • Thanks to all the members of the DUWS-R Team for your hard work and contributions!
  • DUWS Mission made by kibot.
  • VAS script and TAW view distance by Tonic.
  • Thanks to Kempco for the map size script.
  • Thanks to FrankHH for correcting the typos.
  • Thanks to FunkDooBiesT for his help and his time.
  • Thanks to WolfFlight[TZW] and Amarak[TZW] for their help.
  • Thanks to Aeroson for repetitive clean up and SET/GET loadout scripts.
  • Thanks to timsk.