Skip to content

Releases: ozdeadmeat/DDC2

Release 2.0j Stable Release

Choose a tag to compare

@ozdeadmeat ozdeadmeat released this 04 May 10:35
f31f3a9

Discord to DCS Command and Control 2.0j Stable Release

Change Log:

System Requirements

  • Added Powershell 7.x as a pre-requisite for DDC2. (pwsh.exe)
  • Added Licencing Agreement

Node-Red Flow

  • Added Version info to Node-Red Display
  • Fixed Start / Restart not showing Uptime information and Priority data
  • Fixed Double message on Server Start / Restart. A Status response will now follow the acknowledgement of the command being recieved

Powershell (ddc2.ps1)

  • v2.0j Added DDC2-AutoStart
  • v2.0j Added Add-Position
  • v2.0j Added Set-Position
  • v2.0j Updated Set-Window
  • v2.0j Updated UPDATE-MOOSE
  • v2.0i Changed PwdRandomizer to distinguish between SRS and DCS so PwdRandomizer could be called directly from application specific Start Command (start-dcs, start-srs)
  • v2.0i Added Start-Server
  • v2.0i Added Set-Priority
  • v2.0i Added Wait-For-Response
  • v2.0f Fixed Stop-SRS from closing all instances of SRS
  • v2.0f Re-purposed Start-DCS
  • v2.0f Added Start-SRS

Powershell (ddc2_config.ps1)

  • v2.0j Added $DesktopLocation
  • v2.0i Added $SERVER_PRIORITY
  • v2.0i Added $DCS_SERVERSTART
  • v2.0e Added $DDC2_MASTER, $AUTOSTART_DCS_WAIT, $srsCLIENTSFile, $srsCONFIGFile

Issues resolved in this version:
DDC2 Issue #11 - !restart command not functioning
DDC2 Issue #12 - Only 1 instance of DCS is starting when server is Rebooted
DDC2 Issue #13 - SRS returning error when attempting to update multiple instances similtaniously
DDC2 Issue #14 - !support request not pinging member
DDC2 Issue #15 - Missing data from Server Start