Gentleman, thank you for being productive…
All my movie files that get ripped from old sources are not using Plex friendly file names. They are usng Plex friendly FOLDER names though.
There is an automated procedure that creates one or more files called "movie"xy.ext
If it is just one file, it gets renamed to “movie.ext” (literally, not the movie’s Name, but the string “movie”). If it is - for any reason - more than one file, it justs adds a number to the individual files.
This has been working for YEARS without Plex and is really my personal standard.
I do not have a long history using Plex. Plex is ADD-ON to me (a very well liked one).
I do have a scripting environment which is working fine for my needs.
And - Plex is WORKING like a charme for almost all movies. I rarely have Problems at all - with the exception of “movie4.ext” files (it is not the same with “movie3.ext” or below, only with numbers 4 or higher.
I can totally accept that your rules are your rules (yours, not mine). Please accept that these rules are not good or convenient for everyone. And as a software Provider, it should be one of your goals to have a look at it and see if there’s a way to make even more People happy. Last words from myself about that.
@ChuckPA I can understand that these naming routines can get quite complex. Mine (for presenation management purposes) is quite complex in itself. I also had a hard time to differentiate until I learned that I get the best results when using reduction on both ends. When dealing with localized family names and talk titles which I need to compare with a file name or folder name or both, I dramatically boost accuracy of search results in converting all terms to a reduced charset and use almost all non Alphabet (Special Alphabet characters (like é) no included, These just get replaced to their ASCII variants according to complex tables) as white space. I really was surprised how accurate these results become, if you double check then and count for language dependant special alphabet characters (just as an example, for German ä or Ä - Count “ä”, “Ä”, “ae” and “AE” or “Ae” or “a[non-e]” … (you get it). You definitely need to try and run a few thousand tests and have a look at the numbers, but These measures are working almost flawlessly and you totally get rid of white space problems also. When searching in talk titles, we even reduce a long list of white space surrounded grammatical articles on both sides. I bet you are doing something similar. My company is using that to auto-magically find presentation slots for files or folders thrown at our software. Of course, there was nobody telling us… oh, please do that. We just wanted the very best results we could possibly have in identifying speakers and their talks without the need of anybody to do something whenever possible (reducing costs). In your case, your clients are the ones that have those “costs” (ie. time).
Therefore, the “dot” problem really should not be one… but hey, who am I to say that 
Greetings
Ah, and whoever asked if I can find the naming conventions by myself… did so a Long time ago. No need for your “help”, thank you.