As the mission continues over time if Opfor patrols are strong enough they can eliminate infantry at the HQ. It may be worth creating checkpoints along routes that the enemy patrols take to the Blufor HQ. Another possibility is having a way to purchase HQ controlled reinforcements or having the existing reinforcements re-spawn after a certain time limit.

Reference

http://forums.bistudio.com/showthread.php?187877-SP-MP-Dynamic-Universal-War-System-Rebirth&p=2862555&viewfull=1#post2862555

I cant chose anything when I start the mission on a dedicated server, I just have "waiting for the host to find HQ" but there is no menu...

ServerLog:

15:16:15 Error in expression <ignedItems player find "ItemGPS";
if (_number != -1 && !_player_has_gps) then >
15:16:15   Error position: <_number != -1 && !_player_has_gps) then >
15:16:15   Error Undefined variable in expression: _number
15:16:15 File mpmissions\__cur_mp.Stratis\misc\gps_marker.sqf, line 8

Update vehicle list to have latest vehicles

The README.txt should not be in the source folder. Instead it should be merged with the README.md that is at the root of the git project. This will allow the final PBO to be smaller and display the readme contents on the main page of the git project.

Create a new side quest where the goal is to ambush a convoy traveling through a location within a certain time limit. The CP reward will need to be greater for these side quests as time and munitions are constraints here. This also has the option to become a branching reward system. For example, X reward could be given for destroying a critical vehicle in the convoy where Y reward could be given for capturing the critical vehicle and returning it to the HQ.

EXPECTED OUTCOME
A new mission type "Intercept Convoy" with some or all features listed above.

There needs to be discussions around the PROs and CONs of having additional lighting around the HQ. I'm sure there are some players that wish for a stealthy and/or night-ops feel. Others could use additional lighting around the HQ at night.

Reference

http://forums.bistudio.com/showthread.php?187877-SP-MP-Dynamic-Universal-War-System-Rebirth&p=2862555&viewfull=1#post2862555

Pull the todo.TXT out of the source code. This is no longer needed since the project is now on GitHub and issues can be used. When removing this, the todo items should be created as issues on GitHub so they may be tracked. These items may not necessarily be done but should be tracked elsewhere.

After opening the "Recruit special operatives" menu and 'hiring' a soldier, returning to the "Request Units" still shows the command points you had when you entered the menu. This is incorrect.

EXPECTED OUTCOME
Returning to the screen shows the correct amount of CP.

It would be nice if DUWS-R could support using units from other mods. I'm sure this opens up a whole can of worms where equipment and personnel are concerned. A good first step may be making Opfor either pick up the default faction or pick up another mod faction.

Reference

http://forums.bistudio.com/showthread.php?187877-SP-MP-Dynamic-Universal-War-System-Rebirth&p=2862555&viewfull=1#post2862555

We've had report of the game getting sluggish for players after an hour or so of gameplay. In an effort to help players fine-tune the mission to stay performing well on their system it may be worth while to expose the options for the cleanup routine to players. We will most likely need some design around this but currently I am thinking a new menu screen under the "settings" area to help with this.

The understood trade-off here is that looting from fallen opfor may suffer since the routine may clean items up based on the players settings

EXPECTED OUTCOME
A new dialog is displayed after the user clicks the "settings" option from the radial menu. This would allow you to either drop into the new dialog that allows tweaking of the settings to garbage collection or the existing menu that lets the user configure the grass draw distance and excreta.

Below is a snip from the todo.TXT that was located in the DUWS source. The ramifications of this change needs to be discussed since I could see less threat when flying helo's around and the such. This issue may become moot once DUWS-R supports running on a dedicated server.

Tim_Fragmagnet: Optimization idea for DUWS, add a user changable setting for a distance at which the AI in a zone starts up, instead of every zone being simulated and tanking the FPS.
Tim_Fragmagnet: and still have a choice to diable it
Tim_Fragmagnet: big old block of text right here

Research the possibility of having separate CP pools for each player.

Some players wish to have a more custom experience. Allowing loose zone placement give a slightly less random experience but the zone type is still random.

EXPECTED OUTCOME
New avenue is given to players for manual placement of enemy zones.

Heal function in DUWS Modified have unlimited range. Technically, you can play leader and send your troops all over the map, while sitting at base and spamming HEAL (2CP) support. Probably should only handle troops within ~100m radius.

Below is a snip from the todo.TXT that was located in the DUWS source.

For random enemy AI patrols, if there are multiple zones that have ocean water within them have boat patrols. If a zone is in a very mountainous area maybe helicopter patrols.

Builds of the pbo by the dev build server appear broken. Figure out what's going on and fix it.

EXPECTED OUTCOME
Builds from the build server work.

Create a new support option similar to the paratroopers support that air lifts a quad-bike in for the player. CP cost should probably be 3 for now but this could be adjusted in the future during play testing.

#33 merge caused an issue where random zone placement no longer works.

EXPECTED OUTCOME
Random zone placement works.

When starting on Altis, looking at the commander and selecting "Request Units" a dialog displays with the message: "No entry 'missions__cur_sp.altis\description.ext /ressourceheader/controls/unitlistbox.ComboScrollBar". Fix the error causing this dialog to show up.

EXPECTED OUTCOME:
Selecting "Request Units" no longer causes dialog to show.

Below is a snip from the todo.TXT that was located in the DUWS source.

For the assassination side missions, make it so that if you get detected in the area before the target is dead, you fail.

The files in /source/initZones/old at first glance appear to be backups. Determine if these are still executed. If not delete them.

EXPECTED OUTCOME
Unused files are removed

Add the ability to use the virtual arsenal or VAS

If a player presses the respawn key while "bounced" in the air the player will respawn in the skydive position and can become stuck. Respawning again causes the loss of a CP so this is an issue.

EXPECTED OUTCOME
Fix it so player doesn't get stuck in skydive position after respawning

It would be nice if when the player is playing in single player mode after accepting a side mission the game would auto save.

EXPECTED OUTCOME
When accepting a side mission in single player the game is autosaved.

Fix deployLocalBuild and removeLocalBuild powershell scripts to not continue during a failure

$ErrorActionPreference = "Stop"

EXPECTED OUTCOME
Add the above code snippet to the tops of the two files and test to make sure it resolves the issue.

I mean, there is modified version already with loads of features.

EDIT (Frito): http://www.maddonkeysoftware.com/DUWS-R/rlex_duws_mod.zip

DUWS relies on VAS, TAW and pFLIR. These items should be updated if newer versions are available.

When playing DUWS in multiplayer, players do not get a skill perk as they did in single player when having 15 XP. Give the player a skill a skill at 15 XP.

EXPECTED OUTCOME
Players in multiplayer have a skill at 15 XP.

It was reported by users on the DUWS forum that after saving the mission then re-loading there are some radio functions that are missing. Examples include the JDAM and Helicopter Taxi. Please confirm these issues exist in DUWS-R. If the issue is confirmed please resolve

EXPECTED OUTCOME
After a save / load items unlocked by players stay unlocked.

Pappy from Steam commented that he needs more starting CP to play the way he was used to with other modified versions of DUWS. The full discussion can be found here.

60 command points is not enough to purchase all the men/equipment needed to play the way I am used too...

Below is a snip from the todo.TXT that was located in the DUWS source. To me it sounds like the intent was to have different methods for how zone creation is performed. If action on this issue is taken it should be to set up the framework to enable various zone selection 'engines' to be used.

There could also be zone creation choices

Simultaneous

what happens now

• Close - zones spawn close the HQ
• Far - zones spawn far from the HQ

Sequential

One zone spawns, another spawns after that one is captured or have a version of the previous with a timer instead of capture based

• Close - same as sequential but close to the HQ
• Far - you get the idea.
• Progressive - Zones keep spawning farther away from the HQ.

Cluster

Like sequential but they spawn multiple at a time from a user defined number and/or can have a timer version

• Cluster: Close
• Cluster: Far
• Cluster: Progressive

Pack Spawn

This one seems like a neato idea, zones spawn like in cluster, however, they spawn very close to each other and all act as if they were one big zone with AI explicitly patrolling between them and such, and when you capture one, AI from the others goes to provide reinforcements

• Close
• Far
• Progressive

Currently there is a bunch of white space and 'weird' formatting in the source. This can lead to difficulty to read and understand what is going on. Update the code to have a consistent c-like (java / c#) formatting style. Also, removing unused files and large license / comment blocks can cause the pbo to be larger than cloud be. Reducing this would let the download run faster and use less bandwidth on the CDN.

EXPECTED OUTCOME
Format code to something sane
Remove bloat from source

Per Nick on Steam Workshop, the ability to re-arm drones is missing. I'm not 100% sure if this is from the original DUWS from Kibot or from the mod version produced by BigShot. Since we are slowly pulling in the changes from BigShots pbo once we can verify them, this issue may need to be addressed after that.

Does this version feature a fix for the problem where u couldnt re-arm drones? Because right not
its impossible to re-arm drones using "vehicle-refit" because u cant actually sit in it and it 
wont recognize it. (Section omitted). Good work on this mod so far!!

Add the ability to sell back a resource for the CP it cost.

This will need the following considerations:

• Was within a reasonable time limit (2~3 minutes)
• Is not damaged in a major way... see this
• Was purchased by the selling player see this

Below is a snip from the todo.TXT that was located in the DUWS source.

Have another side mission type called assault, where there's a group blufor waiting to attack a position and they go once you get there. It would be fun to have it as a large force with tanks and such. After the assault is completed the remaining force de-spawn after the players left the area.

I'm thinking here of a screen that shows what values were selected when the mission starts. This would be the screen where the enemy AI and starting CP are selected. This doesn't have to contain all the information from that screen as it's not very useful to see what the starting CP was in my opinion. This might be more useful after more features are added to DUWS-R.

At the time of this issue being created, shortly after v0.1.0 was released, there isn't an action item for this issue. I mainly wanted to create the issue so I did not forget about it in the future.

Currently deployLocalBuild.ps1 will rename any official release of DUWS-R so that it doesn't get loaded by Arma. This was done so that way you only have one DUWS-R mission when you are testing. Create a mechanism that restores any pbo's modified by the current deployLocalBuild.ps1.

EXPECTED OUTCOME
Developers have an easy way to revert the local development build without having to manually rename/delete/move files.

Below is a snip from the todo.TXT that was located in the DUWS source.

When the blufor army power gets high enough add a side mission to laser target stuff for a airstrike (Helo or airplane).

Implement enemy multiplier which multiplies amount of enemies in each team created by create*.sqf scripts. Implemented in my version, so can be ported pretty easily.

Make the CP reward for the missions configurable in the main screen. These don't have to be configurable on a per-mission basis but being able to have a multiplier applied to them all would be useful.

Initial thoughts are having these options:
0.5
1.0 (default)
2.0
5.0

EXPECTED OUTCOME:
When starting a new DUWS user is asked for a CP Reward multiplier.

@phr0gz @bolbies @naitp

I have a PM from Rallye on the BIStudio forums stating that he/she has added Zeus support to DUWS-R. Is this a feature we want to include in core DUWS-R? I don't want to sway any votes one way or the other so I'm going to refrain from comment right now.

I have a feeling that one or two of these three files are "old" and not used. Upon basing from this code there were many ".bak" and the such files. While cleaning up some of this these three files seemed very familiar. The task here is to figure out if any of these files can safely be removed from source control to reduce the confusion for future maintainers.

EXPECTED OUTCOME
Clean up the trash (if any)

From the original README.txt...

Find something useful to do with Army Power (suggestions are very welcome)

unforgiven91 reported that squad command is lost by the host during play. I have experienced this issue as well. This seems to be tied to player death.

This may be tied to #27

Steps to reproduce can be found here: http://forums.bistudio.com/showthread.php?187877-SP-MP-Dynamic-Universal-War-System-Rebirth&p=2871223&viewfull=1#post2871223

EXPECTED OUTCOME
After the player dies occasionally they will lose the privileges they started the game with.

Persistent player stats throughout the campaigns, allowing the player to play a multi island driven campaign

Create development cycle overview page

As this is a fork on an existing project, this work must be re-branded. Please re-brand the below items.

• kibot --> DUWS Rebirth Team
• Dynamic Universal WAR System --> Dynamic Universal WAR System - Rebirth
• DUWS --> DUWS-R

EXPECTED OUTCOME
Areas are re-branded.

Configure Pull Request builds & notifications working between TeamCity and GitHub

Create a git primer page to assist people 100% new with git. The goal of this page is to provide a "workflow" of what steps should be taken to contribute in the most basic way.

Create Push Request review guidelines