This post will link to the lastest version of the guide describing the use of Hunter. Hunter is a server application, which can bring dozens of OPRF assets to life over MP (sailing ships, flying helicopters and static buildings etc).
Further development of Hunter is paused apart from bugs and specific requests for integration (e.g. craters from bombs on runways).
You can still ask me to run Hunter with a scenario - or ask me to help you install Hunter on your own. And I am happy to help preparing a scenario for an event (with sufficient lead time) and run it.
However, Hunter is doomed due to the current capabilities and constraints in FG, which would either make Hunter dumb middleware or double the coding effort. I should have realized this before given the knowledge transferred from e.g. Leto, Pinto, Richard and others - I just realised the amount of impact too late.
So there will not be any dynamic assignment of G/A tasks, no website with hit scores and carrier handling and no reuse of the code/features in osm2city to heuristically place targets.
This has nothing to do with FG or the code/setup used in OPRF - it is just the basic idea of Hunter as an external instance over the MP protocol and written in another language than Nasal being doomed.
#14397923 Aug 01, 2020 at 04:45 PM · Edited 1 minute ago
Hunter has been extended to be able to run truck convoys based on road networks imported from OpenStreeMap data. The Swiss scenario has now two convoys: one around LSMP and one around the lake "Murtensee".