Wow, thanks for that, now all we need is a method to make a .txt file that the program can add to that list, so custom files for say DarkStorm can be made.
Maby a header, followed by item name and then the path.
If this was external to the program other forum members could create files for their mods or other mods.

Well, it's not too big of a deal to scan the files and find the appropriate key words. I already wrote the scanners to read the activities file and the index.ini to find the image path and module name. What gets a little harder, though, is parsing comments correctly. I've noticed a few entities that say "//DO NOT USE WILL CRASH GAME". It's doable, though. I suppose it wouldn't be hard to simply read the index.ini, and find all of the IncludePaths, since they directly reference the files that need to be included.

Granted, a txt file made by the modders would be 30 times easier to read, and a lot faster, too.

The main thing that has to be done is to scan through every mod and look for an AddActivity, and comment it out (and a way to reverse that, of course). Then create a folder as dragonxp said that it something like zzzzSkirmish_Activities.rte (I with there was a better way). In there an index.ini with a reference to basically the same file which the mod manager is creating right now. I'd have to rework how all the entities are managed, too, since I hardcoded everything for now.

If I recall correctly missions.rte is hardcoded to load after all other .rtes

food for thought

It's a shame mods don't have a "Priority = " in the main index, then 1 could mean load first, 9 load last, so misions or iitem dispencers get a high number like 7, based on the priority of it's reliencies.

Aside from that manual .txt's would be easyer, what format should they be in to work? What data would need to be included? The name, type, mod and path would be neccecery.

Like:
Modname - [the display name]
Modpath - [.rte name]
AddACraft - [name]
Path - [.ini path for craft]

If that would work, I'm sure it's missing something or other.

Defining .inis inside a text document is just silly because it already exists.
A plain text Contents.txt that just contained basic info on what's in the mod and who it's by would be ideal, but, hell, the majority of modders don't go to the effort of including a Module Icon; how likely are they to include an entirely superfluous file?

If that's true, then why doesn't including other mods work out of the box?

The txt file wouldn't need to be fancy at all, and very similar to the ini files. I was thinking something like this:

Modname = rte name without rte
Weapon = instancename of weapon
Weapon = instancename of weapon
Weapon = instancename of weapon
Actor = instancename of actor
Actor = instancename of actor
Transport = instancename of transport
Transport = instancename of transport

And maybe some optional ones like these, to separate items a little more.

Grenade = instancename of grenade
Shield = instancename of shield
Rocket = instancename of rocket
Crab = instancename of crab

It's very easy to read (simply call string.split("=");, then modname + "\\" + instancename) and very easy for the modders to implement.
AAL actually includes a file like this already, albeit a harder-to-read one. As grif said, a lot of modders wouldn't bother to do this, so I'd like to take a vote before I start working on either one:

(1) - Scan through files (slow, no modder input required, will get every entity, more room for errors, will take longer to implement)
(2) - Modder included .txt (fast, requires modders to add a separate file, little room for error, can quickly be implemented)

Wait a second...

Couldn't you have it like this?



It would make it so that you wouldn't need a separate file.
But that might be much harder anyway, and would probably not be worth it.

I'd say put in number 2, and work on 1 in the background for a later release.

Well, during that last test, the program simply empties the contents of every file with an AddActivity in it. Oops.

Well, I hope the 300-odd of you who have downloaded this are happy.

In return for that, here's CCMM 1.3.

Changes:

• Enhanced Skirmish - use any mod in skirmish!
• Enabled in the settings menu
• DarkStorm and AAL files included for testing
• Couple bug fixes

Yup, any mod in skirmish mode. Just enable it in the settings menu, which will create all of the necessary files. If you want to use an activity that a mod includes, simply disable Enhanced Skirmish. That will reset things back to default. You'll lose all of your Enhanced Skirmish waves by doing this, however.

The DarkStorm and AAL files can be enabled by copying them to their respective folders, and renaming them to "MMItems.txt".

If you want to create a MMItems files for other mods and post them, I'll put them in the original post.

Here's me fighting some DarkStorm guys I put in with CCMM.

404 error.

I don't even have a witty response witty enough to express my joy. So I'm just going to be downloading this kthx.

EDIT: 404
FFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUU

Oops. Fixed.

EDIT: And fixed again. It's not a Mod Manger.

Do you think we should just put the MMIntems.txt in the .rte? that way, whenever there is an update (added/removed stuff), we could just ask the player to put it into the CC mod manager folder where it's supposed to go, and would not have to PM you with the file. I'm pretty sure this would eliminate a potentially large amount of PM's. Of course, for older mods without active authors, some people might have to make one for them...

Well of course that's the ideal scenario, I was just thinking for mods that have yet to include them in the main releases, I can include them here.

Didn't think I would ever use one of these 'Mod Managers', but the activities manager lured me in.
Great job, really, this is awesome.