Issue with path substitution

In your situation where the original path is still valid you could always do something like a path sub to an invalid path to purposely break it for testing purposes which would give you the same kind of feedback.

As I explain in my how-to on the topic the file paths stored in in the database are derived from the Kodi sources that are configured and are not influenced by the substitution. As long as you don’t modify the source paths then the database stays 100% consistent. You also have freedom to change any part of the file path so if you wanted to sub something like “/easystore3/Movies/” to “/easystore4/Movies/” Kodi has no issue with that.

Thanks for the feedback. I can’t really respond to the ‘cleaner’ approach aspect as that is rather subjective. If your comfortable with the process of the database edits I don’t really see a downside to doing it that way other than the amount of effort involved.