Plex Movie Scanner/Agent confused by square brackets?

Server Version#: 1.42.2.10156
My movie collection is stored under a single “Movies” folder, with each movie in its own folder. Every folder is named using the same convention, with a sequential number (which I need for my own reasons) within square brackets, followed by the movie title, then the year between round brackets, like this:

[123] Batman Begins (2005)

Isn’t Plex supposed to ignore everything within square brackets? I have reinstalled Plex recently and re-indexed my movie collection, the current Plex Movie agent was able to match 10% of my movies, at most. I switched to the legacy agent and it got probably 50%. Could it be that the new agent gets confused by the square brackets?

Also, is there a way to bulk re-match the content of a library? I know you can do it individually, movie by movie, but it’s quite tedious…

Thanks in advance!

The agents ignore the contents of square brackets but that’s a format I’ve not seen.

For TEST CASE ONLY…

What if you take one and put the [123] at the end? Does it match that way?

@ChuckPa: thanks for the quick reply. I confirm that the issue is the square brackets in front of the movie name. More precisely, here are the folder names I tried and the results:

[1519] Splitsville (2025) => NOT matched automatically

Splitsville (2025) => Matched automatically

Splitsville (2025) [1519] => Matched automatically

I can’t really move the square brackets to the end of the folder name, because it’s used for sorting (too long to explain, it’s related to a small app I developed), but at least now we know exactly what the issue is. Do you know if there is a way to report this to Plex developers?

I think the issue is the first bracket.

‘way back when’ plex required an alphanumeric character to be the first character in a media file name. Not sure if that’s still the case.

It’s possible, I haven’t tried that. Note also that the actual MP4 file inside the folder is named exactly as the folder, save for the [nnnn] prefix. I guess the agent is using the folder name for matching the movie, not the file name…