Regressing test campaign

To solve this complexity, KodiSave has short functions with more comments starting with ";" in green in Notepad++.
So a comment starting with "; (..." is a call of the function with a particular set of parameters.
The expected result is on the next line also as comment.
An empty line separates two consecutive regressing tests.
For example, in case the spinner returns a float number instead of an integer:

The usage is that you can copy-and-paste the string "(KodiMvPath "C:\\Movies\\Aliens (1986)\\fanart" "fanart" 7 5.5)"
without the double quotes in the Script-Fu console (Alt+R S C). Press Enter.
Script-Fu will reply: "C:\\Movies\\Aliens (1986)\\fanart\\fanart6.jpg"

A campaign of tests is now available before delivering a new version:

Regressing tests have been organized in 74 couples of example of call of function and
the expected result on the following line.

Erro mangement is included in the regressing tests:

How to report a bug?

Due to the amazing complexity, there will be probably some bugs you could discover.
However, instead of a screen capture of a bug,
try to learn, in priority, the two main generators of KodiSave full path of the image to be saved:

1. (KodiMvPath path basename artTypeIdx fanArtNbr)
   calling (GenMvFilename basename artTypeIdx fanArtNbr)
2. (KodiTvPath path basename artTypeIdx fanArtNbr isSeasonAll isSeasonNbr seasonNbr)
   calling (GenTvFilename leftPart basename artTypeIdx filExt strFanArt) and
   (GenTvPrefix path basename artTypeIdx isSeasonAll isSeasonNbr seasonNbr)

Parameters are explained in the source code and illustrated by the regressing tests.

In your post, between the tag "[code]" and its closing tag "[/code]",
indicate the call of one of these functions with your own parameters that generates the bug.

The more you are able to describe the bug in the lowest level of those functions,
the more the bug would be easier to fix include by yourself!