Skip to content

[Feature] Set As... DLC/Update #3619

Description

@XargonWan

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

RomM already supports associating multiple files with a single game, which is great.

However, organizing those files into a proper directory structure still requires manually moving them in the filesystem. There is currently no way to classify a file as the Base Game, Update, or DLC directly within RomM and have the corresponding directory structure created or updated automatically.

For platforms such as the Nintendo 3DS, it's common to have separate files for the base game, updates, and DLC, all belonging to the same game.

Describe the solution you'd like

I'd like each file associated with a game to have a "Set as..." action, allowing it to be marked as:

  • Base Game
  • Update
  • DLC

When a role is assigned, RomM should automatically create the expected directory structure if necessary and move the file to the appropriate location.

For example, starting from:

3ds/Game.cia
3ds/Game Update.cia
3ds/Game DLC.cia

This might be done with an "Edit files" button that might appear only in the multi file games.

After marking the files, RomM would reorganize them as:

3ds/Game/Game.cia
3ds/Game/update/Game Update.cia
3ds/Game/dlc/Game DLC.cia

If the structured layout already exists, RomM would simply move the selected file into the correct directory.

Describe alternatives you've considered

The same result can already be achieved by manually reorganizing the filesystem outside of RomM. However, this becomes tedious when managing large libraries, especially when dealing with many games that have updates and DLC.

Additional context

This would be particularly useful for systems like the Nintendo 3DS, but the concept could apply to any platform where a game consists of multiple related files.

Image

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