Manage Path Replacement???

[KodiUser1138]

Still looking for an explination of what exactly is supposed to be entered in the path replacement field for native mode.

[mcarlton00]

It's a simple string replacement.  Remote path is where the server looks for files, local path is how the client should reach those same files.

Example:
Your library is mounted on your server at /mnt/media/Movies.
The library is available over your network at nfs:/export/Movies

You have two options here.
- Option A: one to one replacement
  - Remote Path: /mnt/media/Movies
  - Local Path: nfs:/export/Movies
- Option B: Multi match replacement
  - Remote Path: /mnt/media
  - Local Path: nfs:/export

Option A works just fine and is effectively a 1:1 mapping of folder on the server vs how a client can see it.
Option B can simplify the mappings if you have multiple paths stored in a single location.  ie: this would work for both /mnt/media/Movies and /mnt/media/Shows, assuming both of them are also available under the same relative NFS path.

[KodiUser1138]

I really have no idea how this is supposed to work exactly but I put the paths to my media locations that I use in JF into the addon data data.json file and it worked. Got everything synced. So I fumbled my way to a solution, somehow. Blind squirrel with a yummy nut.

Still having issues being able to access libraries for any reason after initial setup though. That just seems completely broken no matter which version of Kodi I try this on.