Pardon Our (CMT's) Ignorance.

[Rhydgaled]

Simple: You distribute the CMT sounds, bitmaps, and loc map files and the DLLs into one 7zip, and release it as Halo CMT, mapfiles not included. Then you have each map up for download with a readme stating that the maps will not run without Halo CMT.

I think this is a reasonable sugestion, especially if coupled with the installer app idea and a special page on the halomaps website explaining everything.

This page could have two columns, one saying somthing along the lines of:
"To get the basic version of the CMT SPv2 campaign without additional featues, but avoiding possible compatibility issues and installation difficulties simply download each of the map files listed"
and the other saying somthing like:
"For an expanded CMT SPv2 experience download the following package and run the installer app, or download each item seperatly from this list" (the list would just be so if sombody had a random problem with the installer app but understood where everything needs to go they could still get the open sauce version).
The package mentioned would be the "Halo CMT" package plus installer app and 1.08 patch. When this app is run it would ask for your HALO Custom Edition directory, then find out if the 1.08 patch is installed, if not it will install the patch. When you have the patch, it will put the CMT shared maps into the right places and the open sauce .dll and anything I've forgoten to mention. Next it will show a screen with a bunch of hyperlinks to halomaps, linking to each of the sauced campaign maps. If run again it will also detect if you already have all the pre-requisites installed, and skip right to this screen so you can get any maps you haven't yet downloaded.

Maps depend on two shared maps and two dlls. As Dennis stated, that will put off potential players.

Two .dlls? that can't be right. Unless you are refering to the other .dll that some pepole on this thread: needed to get it to work, which I didn't need (mind you that .dll might have been part of one of the SDKs I had to download to get the sauce to compile).

That Delta UI thing for SPv2 wouldn't be necessary or very pretty if we didn't have a matching ACTUAL Main menu Delta UI, so... It's all good that you cut it, especially for space purpose aswell.

Actually, there hasn't been much talk about it, but as far as I know CMT are making a SPv2 UI, like they made one for SPv1. I assume that as they were given permisson to use the Delta Halo UI pause menu they'll be able to use the theme on their main menu too.

Korn still needs to make the User Manual for Open Sauce, he said he was doing that back in November

I think he decided to cut back on his work on Open Sauce and prioritise other stuff he was/is working on when there were no, or next to no, early takers. Now that SPv2 has sparked a revival in intrested in Open Sauce he might be persuaded to create that user manual. It might give novice developers enough of an insite into the code to actually start developing Open Sauce.