Does your Py program provide an easy way to construct the json or is that a manual process? There should be a text-json conversion utility I could use though.
The client program doesn't have a way to generate a json, but I made a simple django-based webapp for it. Code is at https://github.com/T...rasque/yammyamm
Does your program only depend on the json? In other words, will files be fetched from mod links defined in the json?
It only depens on the json info. If the json doesn't have a link to a file, it can't download it.
Will the MO plugin version fetch and deposit the mods into the defined MO "downloaded mods" path and then invoke MO's installation utility for each of those mods in turn? As in: download mod1 > install mod1 > ... download modn > install modn OR download mod1 ... download modn > install mod1 ... install modn
Right now it has a mod info and download window that looks like this. Clicking the "To MO" button will try to open the "install this mod" in MO (if yamm's plugin is installed). But I'm thinking of reworking that a bit
Do you have any plans to implement instructions for the automated MO-based installation/configuration of each mod? In other words, if the json had atributes defining installation/MO configuration, would it be feasible to invoke automated installation?
Not at the moment, but a meta-mod containing a fomod installer or an exe or override files could perhaps do that? I'm not that well versed in actually installing mods, so don't know what would be needed there. Load order could be embedded in the json, with a priority field I guess. But I think that could get messy fast when you have a lot of mods. Again, I don't know the advanced things around mod installation.
(as long as downloads occur from Nexus and pass appropriate tokens identifying the Nexus member downloading the mods and counters, etc. ... as a proxy for manually downloading each individual mod ... meaning that Nexus has no idea that these downloads are being performed by a service as a proxy of the Nexus member rather than the member).
This could technically be done with a field for the nexus ID, but it would likely also make an enemy out of the Nexus admins, especially if it became popular. That's not my intention - I'd rather have their support :)
Edit: When that's said, I think the SA-STEP goals could be achieved, but that would need cooperation with the MO devs. I've been thinking about having option extra / extended json file for mods that can be downloaded for more metadata. So far I've only thought about screenshots and extended description, but having installation metadata could fit in there well. Acting on that metadata should be in MO's domain (or an MO plugin), but yamm can get the data to MO.
Edited by Terrasque, 22 May 2015 - 03:48 PM.