Packing/"compiling" a completed mod list

[Wynadorn]

Is your feature request related to a problem? Please describe. When you've got a modlist you're happy with you'll have lots of separate bsa archives, lose textures, meshes, etc. While modding this is preferred because it means you can alter the priority / overwrite behavior. However, having a large number of archives and lose files also comes at a performance cost.

Describe the solution you'd like Would it be possible (and also worth it) to "compile" the current mod list into a single set of .bsa archives. This would set the included mods to read-only. I guess it's similar to making a container, one mod that actually contains 100 mods.

Describe alternatives you've considered I suppose it could be implemented in two ways, either a selections of mods could be packed or enforce the entire mod-list to be packed and set to read-only.

Additional context / example You have 100 "simple" mods for various textures and meshes. You're happy with the order in which these files overwrite eachother and decide to compile them.

MO2 then:

• Gathers all the files from these 100 mods into a single directory
• Packs these assets into .bsa files.
• Sets the packed mods to read-only.
• Enables a single "mod" containing the packed assets.
• All .esp files are left untouched, the feature would only targets assets.

[Wynadorn]

Realized this would mess with load orders