Nyuu config not respected

[kzshantonu]

--out {fnamebase}.nzb ignored. NZBs save as filename.ext.nzb instead of filename.nzb

[Ravencentric]

This is not exactly a bug, it's just how I made it. The naming has a bit of logic behind it which is why it's not left up to the user. There was point where I was discarding extensions but that soon caused issues which is why I'm forcing extensions

• Nyuu doesn't like backticks, but filenames with backticks are valid in pretty much every common fs. Altering filenames is bad practice, so juicenet handles it by making an intermediate nzb with invalid characters replaced and renames the nzb to it's original name after it's done uploading.
• Folders and filenames can be identical minus the extension. /Big Buck Bunny/ and /Big Buck Bunny.mkv will end up as identically named nzbs (and overwritten) with {fnamebase}.nzb.
• Different files with the same filename but different extensions are also valid and discarding extensions here will once again end up with identically named nzbs (and overwritten) with {fnamebase}.nzb.
• File extension is quite important info that must not be omitted because it can decide whether something is compatible on your system or not (common example would be Dolby Vision Profile 5 releases, which were mostly mp4 in the era of mkv).
• The foldername of BDMVs is quite useless, you can have several BDMVs that are just titled "BDMV" or "DISC1" or something vague like that. Again, juicenet has a bit of logic here to avoid this and provide better naming by going up the path and grabbing the parent folder's name. This sort of goes against my point 1 (never alter name) but this is a situation where altering is the only choice to avoid collisions.

Due to the above reasons, juicenet currently overrides nyuu's config for --out and "decides" on it's own.

[kzshantonu]

I see, makes sense. Hope there will be a feature implemented someday to be able to use nyuu config as-is but with resume capability

[Ravencentric]

I would recommend just letting juicenet name the files, since it already follows best practices and handles problematic cases as mentioned above