Create account / Log in

Module Extension Directory Names

Topics related to the main Vassal engine.

Moderators: Tim M, uckelman

Module Extension Directory Names

Postby Hagar » January 8th, 2012, 5:42 pm

The guidelines for posting updated modules suggest that the module file name have a version as part of the name to avoid confusion. (I forget where I originally read this and have not been able to locate the comment recently.) An older module has extensions in a sub-directory with the same name as the module itself with "_ext" appended. I found that if I post an updated module with a changed file name, i.e. with a version appended, the older extensions will no longer load. Restoring the older module file name solves the problem. I hate to break users' existing setup with the updated module by changing its name. However, the prior version, which is still posted, still retains the old name and would result in an obvious conflict.

Does the newer version of Vassal no longer require this sub-directory name scheme? What is the best way to handle this problem?
User avatar
Hagar
 
Posts: 57
Joined: May 28th, 2008, 11:11 pm

Re: Module Extension Directory Names

Postby mycenae » January 9th, 2012, 5:04 am

I think that suggestion was probably in the designer's guide. Version 3.1 of Vassal looks for extensions in the <ModuleName> _ext folder. it's my understanding that prior to v3.1, this folder had to be created manually and some older instructions still mention this.

However, users can re-add an existing extension in the Module Manager without having to drag and drop stuff into a new folder in the file system. Right-click the module and pick Add Extension, then they can browse to the existing extension file. Vassal will move the extension file into the right folder automatically.
mycenae
 
Posts: 392
Joined: May 16th, 2008, 6:41 pm


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest

cron