That's basically what I did with a batch file for CortUI. Have a look at the BuildModulusPackage.cmd. (There are some required related files, like your mod's Definition.xml and 7zip for packaging, but you can find them all in the repo.)fuzzylunkin1 wrote:Modulus should have some kind of CLI i can use
create a .desc file in each folder package and do a batch job to create mods quickly
like creating .deb files
Nothing should stop you from doing it in IronPython. It should be quite simple, but I'd be curious to try this, so feel free to contact me if you're intested.Spinoza wrote:QUOTE (Spinoza @ Jul 27 2010, 09:36 PM) I could do something similar in AHK or Python (if I knew Python) and if it were an option.
I would rename 'Voice' to 'Voicechat' (as Spinoza said), to make clear that it encompasses not only new voice chat packs, but also pure rearrangements.Orion wrote:QUOTE (Orion @ Aug 8 2010, 11:40 PM) I'm implementing tags, and I'm thinking we should come up with a standard list of tags so people aren't creating very similar ones. I'm not going to lock anyone out of making up their own tags, just going to have a list of recommended ones: (note: they're going to be case-insensitive)
"Texture"
"Icons"
"GUI"
"Voice"
Another type of mod I could think of are keyboard remappings (inputmap1.mdl).
I don't think 'CortUI' should be a tag, but I'd suggest 'UI' (there is no CLI for Alleg, so we don't need 'GUI') for stuff that generally modifies the UI of Allegiance and 'HUD' for individual HUDs. I'll tag the current CortUI installer with both -- of course it could also make sense to split it up into a number of different mods, but that's too much work for my taste right now.
PS: Just call it 1.0, Orion. End the fear of going post-0.x.
PPS: I agree on not making CortUI a featured mod, btw. Those who like it know about it and will find it. Use the featuring to promote new, less well-known, mods.