For convenience.Phergus wrote:Why a per campaign repository?
having a single respository with all your images available to any of your campaigns is totally possible, and is in fact what the rptools gallery does.
The whole concept is having an index file you tell MT about that contains the md5key of the image and a relative path on the web server of the actual file.
The index for the rptools gallery, which comes default with every campaign, uses a perl script to walk the gallery image hierarchy and creates the index. We'll be making this script available along with other ways of creating the index.
We hope to get it installed at other major image repositories such as rpgmapshare.
I'll also add MapTool level repositories that you add that apply to all campaigns that you load. Then you just add all the major repositories along with your personal repositories, and you should never have anyone pulling images from your MT server again
Summary
The campaign repo export is simply a convenience mechanism to take advantage of a more elaborate system. It automatically creates the index and groups the images necessary for your campaign. But nothing is stopping you from creating your own repository with your own index and updating it in any way that you want