Skip to content

Mod Groups #8262

Open

Description

@HammBorgirr

Please confirm the following.

What parts of Modrinth is your feature request related too?

Modrinth App

Is your suggested feature related to a problem? Please describe.

When i make modpacks i like to add some mods that i add basically to all modpacks, and it's very tedious and i always forget some. Also i cannot find mods often in my modpacks when i try to check what i have because it's often scrambled basically

Describe the solution you'd like

Let us group mods and upload groups of mods to other modpacks you have. Similarly to how it looks like when you make a new instance with the start with a modpack and you have the group of the modpack content and content you added.

Describe alternatives you've considered

Don't have any alternative solutions because the premise is so simple and is technically already done on the app just we don't have that much control over it

Additional context

My rendition and the original picture used for reference

Image Image

(this took me too long for what it is 😭 )

Activity

  1. HammBorgirr commented on Nov 9, 2026

    @HammBorgirr
    Author

    somewhat similar to #7503 but it's a bit simpler in premise, and instead of another menu you can just import other modpacks into a different modpack achieving something similar to what #7503 proposed but also easier to understand and use as a normal consumer

  2. SalmonSnaked commented on Nov 10, 2026

    @SalmonSnaked

    Yes, we need this! Who would have guessed I also like your ideas here ;D

    A scaled-down version of my Modpack Studio would allow building instances from collections without synchronization between them. Collections are already established on the Modrinth website and also deserve their own library in the app.

    Image

    Modrinth's collections are currently plain mod lists without any specific project versions or configuration files assigned to them. Bringing that control would start to look more like my content repositories.

  3. HammBorgirr commented on Nov 11, 2026

    @HammBorgirr
    Author

    i just thought of an interesting way to do this that would be i think easy to implement or just a WIP version that could be there as a placeholder while they make something more aligned with what you and i said. What if they made it so that the instance could read nested folders within the mod folder, as an example:

    image

    and they could then display it in the way i proposed in my original post:

    image

    i believe this could be a good way to implement this overall not just as a placeholder

  4. SalmonSnaked commented on Nov 11, 2026

    @SalmonSnaked

    That was actually the approach proposed in #4234
    Unfortunately, not every mod loader natively supports loading mods from subfolders. Apparently, Quilt is the only mainstream one that does this. Fabric has JVM flags to load mods from custom locations. And (Neo)Forge needs companion mods to establish custom mod loading.

    You're facing the exact same two issues I laid out: grouping mods and managing your sanity over the same mods that get added to every instance. And these issues are closely tied together and should be solved together.

  5. HammBorgirr commented on Nov 11, 2026

    @HammBorgirr
    Author

    not every mod loader natively supports loading mods from subfolders

    i didn't know that was the case, i got the inspiration for the idea from how sinytra connector handles it's things by putting it in another folder inside the mods folder so i thought it could work, although if it needs companion mods to be able to do that then why not have a mod that allows to do that and it's just installed when you turn on the option to group mods. or is that not how it works

  6. Olafcio1 commented on Nov 11, 2026

    @Olafcio1

    On Fabric, the Modrinth Launcher could just add the correct JVM flags for subfolders. I see no issue there.

    On (Neo)Forge, that could be overcame by one of these two things:

    1. Modrinth making a Java Agent (or just add this as a last installation step) to patch the modloaders to load from subfolders;
    2. Modrinth making a "mod" (without a mods.toml on Forge, as a JIJ in a parent JAR with neoforge.mods.toml on NeoForge) that adds a custom mod locator to locate from subfolders.

    Although! This subfolder loading behaviour is risky. Some mods (HammBorgirr said Sinytra does it! So it would be an actual issue!) may create subfolders inside the mods folder that may contain e.g. remapped mods. For example, Paper does that - well, it's not a mod, but if a mod somehow gets to load Paper itself, then the subfolder-loading behaviour would cause issues.

  7. HammBorgirr commented on Nov 11, 2026

    @HammBorgirr
    Author

    (HammBorgirr said Sinytra does it! So it would be an actual issue!)

    hmm that's a good point actually, i haven't thought about that. what if there was a way to mark specific folders that it would read from otherwise i don't really know how else to do it. the "groups" that modrinth makes when selecting the option to start from a modpack i think are made by just having specific file names show up in the group keeping a list that tells it what to show in the group. and if im wrong then the list aproach could still be an option, as in keep a text file somewhere in the instance for it to read to group the mods

  8. SalmonSnaked commented on Nov 11, 2026

    @SalmonSnaked

    Most likely Modrinth App will leave the mods folder untouched and only categorize content within the app because unwanted side effects will arise without all modloaders directly supporting subfolders. Regardless, I think the folder organization could be very useful for everyone who likes to manage content externally.

    Content grouping will likely end up looking like a feature where we assign custom tags and filter the content page with those, without organizing the underlying filesystem. Possibly also filters for the other existing tags (e.g. Adventure, Decoration, Optimization, Utility). For the visual implementation, I must say that the separate sections for grouped content like HammBorgirr showcased would look much cleaner (rather than filtering with tags).

    Related to grouping content, wouldn't we all really like it if we could add "Collections" to instances just like any mod or resource pack, and have them automatically become grouped, whether that's a tag or a separate section in the instance. And while we're at it, compose instances by handpicking which collections we want to combine into one final instance. The earlier flowchart represents this exact composition process.

  9. HammBorgirr commented on Nov 12, 2026

    @HammBorgirr
    Author

    Yes, we need this! Who would have guessed I also like your ideas here ;D

    A scaled-down version of my Modpack Studio would allow building instances from collections without synchronization between them. Collections are already established on the Modrinth website and also deserve their own library in the app.
    Image

    Modrinth's collections are currently plain mod lists without any specific project versions of configuration files assigned to them.
    Bringing that control would start to look more like my content repositories.

    I actually think that the auto-installing dependencies part could be skipped or made optional because as an example i would make a "modpack" that will be just visual QoL mods that i will import to a different modpack and there i would have something like "wakes reforged" and "wakes sable compat" and when i try to import it to a modpack where i dont have sable i would just disable the sable compat mod, if you understand what i mean, im gonna try to give a visual:

    image

    sorry didnt feel like editing the red danger text thing

  10. SalmonSnaked commented on Nov 12, 2026

    @SalmonSnaked

    Perfectly understandable. This is why I think the "Review summary" phase shouldn't just show a plain list of all content it gathered from all collections, but instead categorize the pop-up in a way that you could easily tick off any project and bulk-select content and dependencies.

  11. HammBorgirr commented on Nov 12, 2026

    @HammBorgirr
    Author

    Yes proper bulk selecting would be essential and have a like option for adding to other groups from the selection

  12. Olafcio1 commented on Nov 19, 2026

    @Olafcio1

    Regarding my message. The (Neo)Forge behavior could also work by Modrinth having its own mods folder. Like modrinth-mods in your instance folder. Because then it could load all JARs from all subfolders inside that custom folder rather safely.

  13. HammBorgirr commented on Nov 22, 2026

    @HammBorgirr
    Author

    Regarding my message. The (Neo)Forge behavior could also work by Modrinth having its own mods folder. Like modrinth-mods in your instance folder. Because then it could load all JARs from all subfolders inside that custom folder rather safely.

    that does make sense but i wonder if they would want to implement it like that

  14. IMB11 commented on Nov 22, 2026

    @IMB11
    Member

    We're currently working on this :)

    image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions