I enjoy writing scenarios, and if it is something relatively simple (one task force vs. another task force), I can probably put something together fairly quickly
Be cautious of any scenario offered by someone whose personal philosophy is:
A couple of my early scenarios do have a couple of bugs, but these have been reported, and it is possible (pretty easy, in fact) to work around the two or three weapons that don't fire properly and win the scenario anyway. I left those scenarios on Harpgamer so people can experiment.
Mark
openly admits that his scenarios have bugs,
knows exactly which ones they are, and
STILL refuses to correct any of them. Hapless players are left to, "
work around the two or three weapons that don't fire properly". It is abundantly clear from his own words that no matter what problem is reported, it will never be fixed. This is the underlying attitude of HUD and the primary reason why no one plays HUD scenarios.
RGM's a new player still trying to figure out how things work (or don't). Complicating it with database errors will probably just result in additional frustration. Arriving within range of the target and then trying to find a weapon that actually fires should not be part of the learning curve.
If you have been able to successfully follow the action in Air Lane Raiders, you may be ready to try a scenario such as Matrix Siege. As the USN, you only have one frigate, one guided-missile destroyer, and two helicopters. It does not get much simpler than that. However, you are pitted against over a dozen enemy missile boats. You get to witness the sheer power of a Arleigh Burke-class AEgis destroyer.
Matrix Siege
hds ii giuk\m_siege.scn
[video=youtube_share;ef5y6APsNgE]http://youtu.be/ef5y6APsNgE[/video]