Jump to content
LaunchBox Community Forums

Recommended Posts

11 hours ago, Zombeaver said:

Yes, anything after a bracket or parenthesis.

Thanks a lot!

Is the final name trimmed (e.g. "The Game (xxx)" ends up as "The Game" or "The Game ")?

Link to post
Share on other sites
  • 3 weeks later...
  • Replies 41
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I was helping someone in chat last night and it occurred to me that it's probably worth posting about as a sortof FYI/FAQ for others. The topic was "proper" media naming for automatic matc

I edited the post to also mention the underscore requirement for titles that use an apostrophe. I ran into this last night when I had to rename an image for Nemesis '94 Gradius 2 to Nemesi

Yeah I guess that's possible. I'll try it again tonight and restart LB after changing the rom file. Renaming existing image files and then refr

I have done my own testing of LaunchBox's behavior. I want to make a couple of corrections and additions to Zombeaver's original post.

Here are the four ways to match a media file to a game:

1. Match game title to the media filename.

  • The file extension is ignored
  • Upper case vs. lower case is ignored
  • In the filename, all illegal filename characters from the title (as well as '  single quote) must be replaced by _ (underscore). A title of "Ultima III: Exodus" matches a filename of "Ultime III_ Exodus.jpg".
  • If there is a run of multiple consecutive illegal characters in the title, they must be replaced by a single underscore in the filename. So a title of "Game/:?" matches a filename of "Game_.jpg".
  • The full list of illegal characters to be replaced by underscore is < > : " / \ | ? * '
  • A hyphen followed by a number can be appended to the end of the filename. Any number of digits works. So a title of "Doom" matches "Doom-1.jpg", "Doom-11.jpg", "Doom-111.jpg", etc.

2. Match ROM/application filename to the media filename.

  • Upper case vs. lower case is ignored
  • Otherwise, the filenames must match exactly, except for:
  • A hyphen followed by a number can be appended to the end of the filename. Any number of digits works. So a ROM file of "Doom.zip" matches "Doom-1.jpg", "Doom-11.jpg", "Doom-111.jpg", etc.

3. Match stripped game title to stripped media filename.

  • NOTE: In Zombeaver's post, he said that the stripped ROM filename can match the stripped media filename. This is not true.  It is the stripped title, not ROM filename that works this way.
  • Upper case vs. lower case is ignored
  • In this matching mode, all of the following are ignored (i.e. removed from the strings before the string comparison is done):
  • Whitespace is ignored
  • These special characters are ignored: ! - . & ' , : " / \ ?
  • Matched parentheses/brackets/braces and their contents are ignored. (), [], {}, (a), [b], {c} will all be ignored. However, single unmatched parentheses/brackets/braces will not be ignored.
  • The words "a", "an", "and", and "the" are ignored. However, Launchbox's behavior with these is weird. If there are two consecutive ands ("and and") or thes ("the the"), etc. it doesn't ignore them. I don't fully understand Launchbox's logic here. Also, there may be other "magic words" that get ignored, but I haven't found any.
  • In this mode, illegal characters in the title are not replaced by underscore. This has the consequence that titles containing these illegal characters <>|* cannot use this matching mode.
  • However, underscores in the title must have a corresponding underscore in the media filename.
  • Unlike matching modes 1 and 2, the hyphen followed by a number at the end of the filename is not allowed.
  • Example: A title of "My Strangely_(named) ??Game and, the" will match these filenames: "MyStrangely_Game.jpg", "My Strangely_(named) Game and the.jpg", "My Strangely_ Game (USA) [b] and.jpg", "My Strangely_Game &the.jpg", "TheMyStrangely_GameAnd.jpg", etc.

4. Match game ID to media filename.

  • If the media filename contains the game ID (anywhere; it can be preceded and followed by other stuff in the filename), it matches the game.
  • This is the long local GUID that loos like "46f2a757-d3f3-4540-939f-02f978bbb76e", not the LaunchBox database ID.

This is all I have found in my testing. There are probably some more quirks in the third matching mode, but these rules should cover the vast majority of cases.

 

 

 

Edited by sards
  • Like 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...