fvtt-CommunityLighting seems to ignore the routePrefix foundry option when configured for determining its default asset paths.
For example if routePrefix = "thing" all content is going to be at the base path of https://mydomain/thing/. The current behaviour of fvtt-CommunityLighting results in the following...
GET https://mydomain/modules/CommunityLighting/lights.json 404
It should however be doing...
GET https://mydomain/thing/modules/CommunityLighting/lights.json
fvtt-CommunityLighting seems to ignore the routePrefix foundry option when configured for determining its default asset paths.
For example if routePrefix = "thing" all content is going to be at the base path of https://mydomain/thing/. The current behaviour of fvtt-CommunityLighting results in the following...
It should however be doing...