Back when I was working on the Outpost 2 wiki site, an old GUI written in Visual Basic (I think) was pretty useful. You can find it here:
https://wiki.outpost2.net/doku.php?id=outpost_2:helper_programs:mission_scanner.
It depends on library dlls that supported Visual Basic programs that have long been removed from modern Windows computers. It also tends to crash if left open for an extended period of time. These DLLs can be installed into the registry, but there is some general security concerns since they are unsupported now.
I thought it would be a good project to practice pulling exported variables from DLLs and whipped up a console version over the last week. I was pleased how it came together so well. I stole a bit of library code from op2ext and it relies on OP2Utility and Outpost2DLL.
The upside is it doesn't require adding outdated DLLs to your registry and doesn't crash. The downside is you must use your command prompt, just like OP2Archive, and OP2MapImager.
If interested, you can check it out here:
https://github.com/OutpostUniverse/MissionScannerI should probably rename it MissionScanner2 or MissionScannerConsole to make it less confusing than using the previous project's exact name.
Also, I just realized it doesn't add the DLL name for the mission, which is really helpful. That should be pretty simple to add.
There is only a Visual Studio project file, so right now it cannot be compiled on Linux. However, I suspect it is fully or almost fully cross compatible as it stands. It does rely on C++17 features filesystem and string_view.
Any feedback is appreciated. I'll provide a Windows executable of it sometime in the future.
-Brett