Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Import modlist from ModOrganizer2 #92

Open
alekulyn opened this issue Dec 27, 2024 · 6 comments
Open

[Feature Request] Import modlist from ModOrganizer2 #92

alekulyn opened this issue Dec 27, 2024 · 6 comments
Labels
enhancement New feature or request

Comments

@alekulyn
Copy link

I have a huge modlist in ModOrganizer2, and transferring it to LIMO wouldn't be easy. Thankfully, MO2 stores all the data in plaintext files.

@limo-app limo-app added the enhancement New feature or request label Dec 28, 2024
@limo-app
Copy link
Owner

I have not used MO2 in the past but will look into MO2's file structure to see what i can do.

@alekulyn
Copy link
Author

alekulyn commented Dec 29, 2024

I can actually speak a lot about it. So, MO2 stores (mostly) everything in AppData/Local/ModOrganizer.
In ModOrganizer, there are game folders, ex Fallout 4, Skyrim, Oblivion, etc. Let's call the game prefixes.

In each game prefix, there are four main folders, and one main file.
The file, ModOrganizer.ini, stores a bunch of configuration related to the game, such as (but not limited to):

  • MO2 plugin configs
  • configs for executables like LOOT, xEdit, Synthesis, etc
  • selected game profile
  • game location

The four main folders are downloads, mods, overwrite, and profiles.

downloads is the cache were mod downloads are stored, along with their download metadata.

overwrite is considered a mod folder with highest priority. Anything in there wins any file conflicts.

In profiles are folders, one for each profile. Each profile folder stores ini files for the current game profile, like loadorder.txt, plugins.txt, skyrim.ini, and etc.

mods is where all the mods are stored, each in their own folder. For example, mods/SkyUI or mods/SKSE Address Library or mods/Legacy of the Dragonborn. Each mod folder contains all the data for the mod, like the ESPs, BSAs, DLLs, etc. There might also be a optional folder inside the mod folder, which holds the ESPs that the user has excluded from deploy/load order, such as unneeded patches. In each mod folder is a metadata file named meta.ini, which stores (non-exhaustive list):

  • version
  • nexusMods mod metadata (if applicable)
  • category

Hope this helps.

@alekulyn
Copy link
Author

alekulyn commented Jan 9, 2025

An alternative idea is a ModOrganizer plugin that exports the modlist to limo

@limo-app
Copy link
Owner

Sorry for the late response, i took a break.

An alternative idea is a ModOrganizer plugin that exports the modlist to limo

I believe it would be best to add an import feature to Limo. It looks like all the necessary data for this is in the directory you described above. This should be pretty straight forward compared to a Vortex import. There may be issues with the overwrite directory though, as Limo does not have a direct equivalent. The closest thing is a reverse deployer, so i will either add everything in overwrite to that or create a mod called Overwrite instead.

@alekulyn
Copy link
Author

If there are some docs on the limo file structure, I could also spin up something basic to get started

@limo-app
Copy link
Owner

If there are some docs on the limo file structure, I could also spin up something basic to get started

I did not yet have time to write docs for those, sorry. The release for the next update is later today. Once that is done, i will start implementing the import function. This should hopefully not take long, just have to set up an MO2 installation for testing purposes first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants