Wind direction aware ATC

When combined with TacScribe 0.7.6 and and CincServer 0.1.0 this will allow the ATC to detect the wind direction and therefore the currently active runway.

Changelog

Added

• Added runway selection based on airfield wind heading.
• Updated all the taxi graphs to for existing airfields to allow for navigation to both ends of airfields thanks to @Brunius

Changed

• Lots of refactoring
• Changed configuration of Discord logging. Moved the channel id from OverlordBot.exe.config to awacs-radios.json
• AWACS Bots will only respond to the callsign assigned to it in the name field in awacs-radios.json. Leave blank for it to respond to all recognised callsigns. Even with a name specified the bot will respond to Anyface.

Upgrade instructions

OverlordBot has not yet had any work done on it for automated first time installation so contact @rurounijones either on Gitlab or the major DCS discords for first time setup. This zip folder does not contain configuration and is intended to be used with an existing installation.

1. Download OverlordBot-1.11.0.zip
2. Stop OverlordBot
3. Backup your existing OverlordBot folder.
4. Delete all json files in the Data folder.
5. Copy the contents of the OverlordBot-1.11.0.zip into your OverlordBot folder.
6. Update the OverlordBot.exe.config with the following config

      <setting name="WindHeading" serializeAs="String">
        <value>90</value> <!--Default wind heading (Where it is coming from)-->
      </setting>

This acts as a default direction in case of no wind directions being detected on the server.
7. Add the following entries into the awacs-radios.json file for each of your radios. botType is either AWACS or ATC. Set the discordTransmissionLogId as desired.

    "botType": "AWACS",
    "discordTransmissionLogChannelId": 0

8. If you want the bot to only respond to one callsign then make sure the name field contains the name, e.g. Overlord. Leave blank for the bot to respond to all recognised callsigns.
9. Restart OverlordBot