F4

It looks like it's just missing thechannel.json file from resources/dcs/beacons, and since in github thechannel.json is just "[]", which is the same as the existing normandy.json, just copying normandy.json to thechannel.json seems to be a workaround to avoid pulling individual file from github.

Ground force movements, RTS... that's caught my attention, because presumably the DC now contains some strategic-level knowledge such as what the goals might be in a given scenario and how to achieve them (rather than just randomly move around). Good stuff.

Hey MBot, As one of the programmers from Falcon 4.0: Allied Force I congratulate you. This stuff isn't easy, which is why nobody yet managed to beat or even match F4's dynamic campaign. The basic reason for that is the core of F4 is a database and the playable F16 is simply a client of the database. Many other titles place the flyable as the core (can you image selling to management, hey what our gamers want is a database! lol). I don't have the DCS F-5, since I came here interested in the Spitfire so I can't try your code at this time. Maybe in the new year I'll spend some money and try it out, though in the meantime I will enjoy reading the scripts :) Good job.