Add a feature to the CurseForge modpack editor that automatically separates files into two collapsible sections:
Original Modpack Content — Mods, resource packs, configuration files, and other content included with the original modpack.
Custom Added Content — Anything the user adds after installing or creating a copy of the modpack.
This could work similarly to the existing category system, but it would use only these two automatic categories. Each section could be expanded or collapsed, making large mod lists easier to read and manage.
The main purpose would be to help users customize a modpack without losing track of which files belong to the original pack. This would reduce the chance of accidentally removing or changing a core mod while allowing users to quickly review their own additions.
Suggested Implementation
Automatically label files based on whether they came with the modpack or were added later by the user.
Display the two groups as collapsible headers within the mod list.
Show the number of items in each section, such as Original Content (142) and Custom Added (8).
Preserve the separation when the modpack is reopened or exported.
When updating the original modpack, keep custom additions in their own section so users can clearly review what changed.
Add a warning before deleting or disabling original content, while allowing custom additions to be edited freely.
Optionally provide a filter or badge so users can quickly identify original and custom files in search results.
Compatibility and Library Mod Organization
The editor could also highlight or group mods according to their compatibility with the selected Minecraft version, mod loader, and other installed mods. Simple icons, labels, or colors could identify mods as compatible, outdated, missing a dependency, potentially conflicting, or not yet verified. Users could then filter or sort the list by compatibility status, making problems easier to find before launching the game.
A separate collapsible Library and Dependency Mods section could organize APIs, frameworks, and other mods that mainly exist to support gameplay or content mods. CurseForge could identify these through its existing dependency information. Keeping library mods visible but separated would reduce clutter without implying that they are unimportant or safe to remove.
Possible sections could therefore include:
Original Modpack Content
Custom Added Content
Library and Dependency Mods
Compatibility highlighting could appear within all three sections rather than creating another permanent category. This would preserve the simple layout while still helping users identify version mismatches, missing requirements, and likely conflicts.
This would make the CurseForge modpack editor cleaner and safer to use, especially for players who frequently modify existing packs. It would provide the benefits of categories without requiring users to organize every file manually.