Thankyou for the reply, Levi

I think the "a" there refers to the <a> tag, where you place rel="lightbox".
In the actual lightbox
js file, the part where all the image paths are is here, ive pasted everything above so you can see what the javascript specifies before these image paths, and it doesn't seem to relate to one gallery, just the entire lightbox:
HTML Code:
(function($) {
/**
* $ is an alias to jQuery object
*
*/
$.fn.lightBox = function(settings) {
// Settings to configure the jQuery lightBox plugin how you like
settings = jQuery.extend({
// Configuration related to overlay
overlayBgColor: '#000', // (string) Background color to overlay; inform a hexadecimal value like: #RRGGBB. Where RR, GG, and BB are the hexadecimal values for the red, green, and blue values of the color.
overlayOpacity: 0.8, // (integer) Opacity value to overlay; inform: 0.X. Where X are number from 0 to 9
// Configuration related to navigation
fixedNavigation: false, // (boolean) Boolean that informs if the navigation (next and prev button) will be fixed or not in the interface.
// Configuration related to images
imageLoading: '../images/lightbox-ico-loading.gif', // (string) Path and the name of the loading icon
imageBtnPrev: '../images/lightbox-btn-prev.gif', // (string) Path and the name of the prev button image
imageBtnNext: '../images/lightbox-btn-next.gif', // (string) Path and the name of the next button image
imageBtnClose: '../images/lightbox-btn-close.gif', // (string) Path and the name of the close btn
imageBlank: '../images/lightbox-blank.gif', // (string) Path and the name of a blank image (one pixel)
// Configuration related to container image box
Sorry if i have understood your answer incorrectly!
i suspected the only way you could do it really is a) if you know what youre doing: add something in the javascript that will detect the directory and then list new image paths for each level of subdirectory. or b) if you dont know what youre doing with javascript (me): make duplicates of this lightbox script, and include different image paths for each level of subdirectory, then include the different versions in the html pages head sections depending on where they are in the file structure.
I just wondered if there was a less messy way to do it than b)!