Liteloader Modlist format
Hello, I am seeking to use liteloader and FML together. I plan on using FML's modlist format so that I can store mods maven style, however liteloader does not support this format.
Details on FML's Modlist format: https://github.com/MinecraftForge/FML/wiki/New-JSON-Modlist-format
A simple way to implement this could be to add the argument --liteModList <file location>. That file can follow the same format as the FML modList, however litemods would be listed under liteModRef instead of modRef. Of course this can be implemented in any way you wish, however I just ask that it doesnt conflict with FML. Also, I would need this feature backported into liteloader 1.11.2, as that's the version it would be used on.
I would really appreciate it if you could add this feature. It would be integrated into WesterosCraft's new launcher so many people would find use in it.
-
I can certainly add support for this. 1.11.2 is currently still a supported version so any changes are backported to that version anyway.
LiteLoader's mod discovery system is already more modular than FML's, with mod enumerator modules being a standard part of the loader core. Adding support for this should basically just involve adding a new enumerator type.
-
There is indeed, I basically have it working and am just testing it to destruction before I push it to live. It was quite an interesting feature to implement because of the way it interacts with the rest of LiteLoader's discovery scaffolding, and I think my implementation actually supports slightly more of the maven artefact shorthand syntax than cpw's (in that I also support the @ suffix for setting the artefact file extension, meaning you can use jar, zip or litemod extensions in the repo).
Once I'm happy with it I will push it to the live snapshots.
-
Status changed to closed by commit a2a91d21
-
mentioned in commit 5f482b2d
-
mentioned in commit a2a91d21
-
mentioned in commit 61c45ce8
-
Merged into 1.11.2, 1.12 and 1.12.1.
The modList JSON can be specified with the
--modRepoargument. The argument can be an absolute path or a relative path which is interpreted relative to the game directory.All artefact specifiers use the maven shorthand syntax, examples:
-
com.mumfrey:macros:0.14.5- resolves to a.jarfile -
com.mumfrey:macros:0.14.5@litemod- resolves to a.litemodfile -
com.mumfrey:macros:0.14.5:mc1.12.1- jar with classifier -
com.mumfrey:macros:0.14.5:mc1.12.1@litemod- litemod with classifier
As per cpw's spec, child configurations evict parent ones. Mods with matching IDs discovered in the
modsfolder respect the revisioning rules of litemods. Eg. a newer version of a particular mod placed in themodsfolder will evict a version specified in the repo, and vice versa. -
