movie.NFO generation

[west]

With the update to v10.9 and v10.9.1 there's been a change in how movie NFO files are created and saved on the filesystem.
movie.NFO files are being generated and prioritized instead of 'movie's actual filename'.NFO files.

First question: Can this new change be reverted or re-configured to not do this?
Second question: If no to the above, how do run a script or a scan that changes replaces existing .NFO files to the new movie.NFO so that existing metadata, locked data instructions, upload/creation dates are retained and no duplicate .NFO files remain?
Third Question: How do we name and handle our multiple version of movies folders now?
(I can further explain the new set of problems with multiple versions movies if necessary)

[TheDreadPirate]

I'm assuming it would put both movie's metadata in movie.nfo. That's how it works for shows, IIRC. Its been a while since I used NFOs.

[west]

For single-item movies it made an identical copy and all further metadata edits will be written to it (movie.nfo).
The 3rd question is more important really. It didn't consistently copy the pre-existing .nfo file. It created a new one with all fields filled from scratch. This really threw a monkey wrench into my multiple version movies. I had them all previously filenamed before the 10.9 update in a way that played nicely with the stacking logic, as well as getting reliable version selection playback in all environments (desktop, web, android and android TV).
Around 75% of the multi-versioned movies in my library now aren't playing nice with the stacking logic or getting reliable Android TV selection playback. I've got to think other people have run into this. I'm probably just going to re-name everything after a bit of testing to see what works better with the new logic.

[MrFusion]

[edit] Reading the below has cleared up my question on this for now
https://github.com/jellyfin/jellyfin/pull/10339

[balieu]

This post has made it much clearer to me, how Jellyfin interpret the filename versioning syntax. Thanks.

As a supplement I have noticed, that if the version label section of the movie filename contains a year (a number that can be interpreted as a year), then the auto-grouping fails, and every movie version file is seen as a separate movie. It also triggers the generation of the <main filename equal to the parent folder name>.nfo file, in addition to the movie.nfo file.
This was seen in Jellyfin v10.9.3 (Web Client).

So if you can't get Jellyfin to auto-group movie versions, then this may be the reason.