List view
I think it's time I though about being more ambitious for NIOD, V3 is going to be pretty big. - Rewrite the network system: Right now it's a bit of a mess, I need to make sure that NIOD reconnects when disconnected, handles big messages (socket seems to overload when too much info is passed) the ultimate test should be to execute MOOSE using NIOD. I'm going to overhaul the entirety of the code to try and make it more up to my personal standards lately ;) - Add typing and support for all of the DCS vanilla API: https://wiki.hoggitworld.com/view/Category:Functions . I said I wouldn't do it given the time it would take but with hindsight I now think I should - Start working on higher level functionalities: I'm a big supporter of frameworks like MOOSE. What I'm less a fan of is the OOP approach and the fact that they have to run in the game environment. I'm going to try to make my own framework, that runs in the javascript engine. This could be a big fail but I think it is going to be a rewarding challenge ;) Here's what I want to have at some point: - Spawning of groups based on a template - Spawning of statics based on a template - Zone handling - Persistancy - AI Tasking - ATC - Intelligent SAMs - CAS: for players, dispatch them to frequencies with JTAC - Troup transport - ADF beacons - Cargo handling - AI air defense system That a lot of stuff, everything most likely won't make it to 3.0, we'll see
No due date•2/4 issues closed