Skip to content

[Feature Request] Ignore brackets and their content in filenames (for scanning purposes) #18290

@toao1985

Description

@toao1985

Typically, a game file is named as such Game Name (Region) (Revision). RetroArch has no trouble reading it and properly lodging it in a corresponding database, playlist and even providing thumbnails for the game.

If a file is externally modified (normally for translation and general rom hacking), users tend to rename it, for better organization and clarification. As to not mess with the original naming scheme, any additional information is usually added between brackets, which denote those external modifications; on the other hand, information about the original, untampered, file is kept between parenthesis.

As an example, let's consider a hypothetical japanese game:
My Game (Japan).extension
Translated to english, it could be named:
My Game (Japan) [English Translation].extension

Naturally, RetroArch cannot recognize the translated name. After all, it's not the original file, and it's not humanly possible to add every single little modification for all games into a internal database.

However, although My Game (Japan) [English Translation].extension isn't inside the database, My Game (Japan).extension is. That means, any modified game can be readily recognized, if RetroArch choose to ignore the brackets and their information in any filename. That's what I suggest with this feature request.

Not everyone wants this behavior though. Some people like to have multiple modifications of a same game, so it would disturb their usecase. Thus, the feature could be an option (off by default) inside of Settings > Playlists > Ignore brackets when scanning filenames.

I consider it a middle-ground, a compromise, that could help with the following suggestion:
#15162

And this one, by focusing on manual scan with filename matching, instead of checksum comparison:
#10952

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions