I've just updated the script to version 1.1.0 with a new optional switch called DontResolvePath which lets you control whether the path you enter for a particular path/command group will be automatically resolved or not before checking for a match.
For example, say you have this command pair, to automatically redirect a library to its absolute path:
Path1 = lib://Documents
EntryCommand1 = Go C:\Users\YourName\Documents
Normally, the script would use the FSUtil.Resolve method on the path which would result in the path being set as C:\Users\YourName\Documents, then stores that to check against the path shown in the lister. This allows you to use aliases in the script's config, etc.
But in this case, we don't actually want the resolved version, because the path that shows in the lister is literally lib://Documents, so we want to keep that as the path to check against. Therefore before, it wouldn't detect a match even though the path used in the config is what shows in the lister.
So now you can include the DontResolvePath switch for that particular group and it should work.
For example this is what I have in my config to redirect any library to its true path:
Path3 = lib://*
EntryCommand3 = Go {sourcepath}
Switches3 = DontResolvePath
Also note that you can include the usual function arguments like {sourcepath} just like you would use in a User Command. And also notice how wildcards still work because that is checked separately.