# Switching to the New Module Library
**URL:** https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164
**Category:** Module Discussion
**Created:** [May 11, 2025, 8:58pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164 "2025-05-11T20:58:14Z")
**Posts on this page:** 20
**Page:** 21
### Author:  [@Reg](https://forum.vassalengine.org/u/Reg)
#### Post date: [July 26, 2025, 1:15am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/403 "2025-07-26T01:15:49Z")
> [@uckelman](#):
>
> > [@Reg](#):
> >
> > I fixed the issue by simply editing the extension to the latest main module version.
>
> If you’re still having this problem, please show me the extension file which is failing to upload so I can investigate further.
The file in question is the "VARIANT - Dismounted CSA Cavalry.vext file in the [Three\_Days\_of\_Gettysburg](https://vassalengine.org/library/projects/The_Three_Days_of_Gettysburg_(third_edition)) Project.
This is the exactly same file as posted in the 1.29.0 release but I had to edit the version tag to 1.29.1 in the ‘moduledata’ file before it would upload. (Note this was after I also had to rename the file to .vext which I believe you have addressed already).
These extension file versions load perfectly with all versions of the main module, the only issue was with uploading to the new repository. With the above fixes all is working now.
Cheers,
Reg
---
### Author:  [@Donegal](https://forum.vassalengine.org/u/Donegal)
#### Post date: [July 26, 2025, 8:59pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/404 "2025-07-26T20:59:11Z")
I created Cheaoss module with the old version but now the project doesn’t have the release ,neither the module:
> **[Cheaoss - Module Library - Vassal](https://vassalengine.org/library//projects/Cheaoss)**
>
> Vassal is an open-source game engine for building and playing online adaptations of board games and card games.
And now I can`t upload a new version of the module. Wasn’t the module migrated well?
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [July 26, 2025, 9:56pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/405 "2025-07-26T21:56:36Z")
> [@Reg](#):
>
> The file in question is the "VARIANT - Dismounted CSA Cavalry.vext file in the [Three\_Days\_of\_Gettysburg](https://vassalengine.org/library/projects/The_Three_Days_of_Gettysburg_(third_edition)) Project.
>
> This is the exactly same file as posted in the 1.29.0 release but I had to edit the version tag to 1.29.1 in the ‘moduledata’ file before it would upload. (Note this was after I also had to rename the file to .vext which I believe you have addressed already).
>
> These extension file versions load perfectly with all versions of the main module, the only issue was with uploading to the new repository. With the above fixes all is working now.
Please try uploading these files with the correct `.vmdx` extension and let me know when you have.
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [July 26, 2025, 10:08pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/406 "2025-07-26T22:08:29Z")
> [@Donegal](#):
>
> And now I can`t upload a new version of the module. Wasn’t the module migrated well?
Cheaoss wasn’t migrated properly. I’ve fixed it. Try now.
---
### Author:  [@Reg](https://forum.vassalengine.org/u/Reg)
#### Post date: [July 28, 2025, 9:11am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/407 "2025-07-28T09:11:12Z")
> [@uckelman](#):
>
> > [@Reg](#):
> >
> > The file in question is the "VARIANT - Dismounted CSA Cavalry.vext file in the [Three\_Days\_of\_Gettysburg](https://vassalengine.org/library/projects/The_Three_Days_of_Gettysburg_(third_edition)) Project.
> >
> > This is the exactly same file as posted in the 1.29.0 release but I had to edit the version tag to 1.29.1 in the ‘moduledata’ file before it would upload. (Note this was after I also had to rename the file to .vext which I believe you have addressed already).
> >
> > These extension file versions load perfectly with all versions of the main module, the only issue was with uploading to the new repository. With the above fixes all is working now.
>
> Please try uploading these files with the correct `.vmdx` extension and let me know when you have.
Hi Joel,
The .vmdx upload issue is fixed. Thanks for that. 😀
(Could you remove the old (.vext) QCGC scenario extension file please).
However, the loading of the other extension has still picked up on the parent module version even after renaming the file to .vmdx. This extension loads quite happily into 1.29.0 3DoG main module despite being created with 1.28c. The upload error can be fixed as described above.
Cheers,
Reg
---
### Author:  [@Reg](https://forum.vassalengine.org/u/Reg)
#### Post date: [July 28, 2025, 9:43am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/408 "2025-07-28T09:43:31Z")
Ah-ha!! It was being rejected because the module version number (1.28c) was malformed (not complying with semantic versioning) rather than not matching the Release number.
I updated the version tag in ‘moduledata’ to version format listed in “Older Releases” (1.28.0-c) and it all works now!!!
Thanks very much for your assistance. 😀
Reg.
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [July 28, 2025, 10:27am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/409 "2025-07-28T10:27:01Z")
> [@Reg](#):
>
> Ah-ha!! It was being rejected because the module version number (1.28c) was malformed (not complying with semantic versioning) rather than not matching the Release number.
Correct. I was just writing this in reply, but you beat me to it.
---
### Author:  [@greenknight](https://forum.vassalengine.org/u/greenknight)
#### Post date: [July 31, 2025, 8:01pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/410 "2025-07-31T20:01:35Z")
Star Wars: Armada module [Star Wars: Armada - Module Library - Vassal](https://vassalengine.org/library/projects/Star_Wars_Armada)
I’m the owner of this thing, but how do I get access to update it?
The owner looks like green\_knight but my profile here is greenknight
#confused
(I ask bc a new major version is supposed to release Aug 1)
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [July 31, 2025, 8:09pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/411 "2025-07-31T20:09:48Z")
> [@greenknight](#):
>
> I’m the owner of this thing, but how do I get access to update it?
By doing exactly what you’ve done—asking here, so we know there’s a problem.
> [@greenknight](#):
>
> The owner looks like green\_knight but my profile here is greenknight
The owner was a placeholder account. I’ve merged it into yours. You should be able to edit the project page now.
---
### Author:  [@greenknight](https://forum.vassalengine.org/u/greenknight)
#### Post date: [July 31, 2025, 8:23pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/412 "2025-07-31T20:23:46Z")
That did the trick! Thanks!
---
### Author:  [@greenknight](https://forum.vassalengine.org/u/greenknight)
#### Post date: [August 1, 2025, 10:49am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/413 "2025-08-01T10:49:59Z")
When trying to edit the module readme:
APIError: 401 Unauthorized: Unauthorized
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [August 1, 2025, 11:39am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/414 "2025-08-01T11:39:23Z")
Try logging in and logging out again.
---
### Author:  [@greenknight](https://forum.vassalengine.org/u/greenknight)
#### Post date: [August 1, 2025, 12:49pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/415 "2025-08-01T12:49:54Z")
Maybe I’m unusually slow, but I don’t understand this… I tried making a package bc there are no packages associated with the module that I can see (but I can’t use number 1, so something is there).
But once the package is created, I can’t see it, so what now?
---
### Author:  [@greenknight](https://forum.vassalengine.org/u/greenknight)
#### Post date: [August 1, 2025, 12:51pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/416 "2025-08-01T12:51:37Z")
Now it has appeared… complaining helps…
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [August 1, 2025, 1:21pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/417 "2025-08-01T13:21:37Z")
> [@greenknight](#):
>
> I tried making a package bc there are no packages associated with the module that I can see
There was already a package: It’s the one called “Module”, which has all the releases in it.
---
### Author:  [@greenknight](https://forum.vassalengine.org/u/greenknight)
#### Post date: [August 2, 2025, 9:36am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/418 "2025-08-02T09:36:38Z")
I must say the new system is a pleasure to use - once I wrapped my head around it!
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [August 2, 2025, 7:07pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/419 "2025-08-02T19:07:48Z")
A post was split to a new topic: [Java virtual machine launcher error could not open file](https://forum.vassalengine.org/t/java-virtual-machine-launcher-error-could-not-open-file/86179)
---
### Author:  [@cgmclellan](https://forum.vassalengine.org/u/cgmclellan)
#### Post date: [August 3, 2025, 11:36am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/420 "2025-08-03T11:36:58Z")
Ask who? I am on Afrika Korps, Blitzkrieg, Imperium, The Russia Campaign, and maybe one other one. cgmclellan.
---
### Author:  [@uckelman](https://forum.vassalengine.org/u/uckelman)
#### Post date: [August 3, 2025, 11:41am UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/421 "2025-08-03T11:41:03Z")
> [@cgmclellan](#):
>
> Ask who?
Me. Here.
> [@cgmclellan](#):
>
> I am on Afrika Korps, Blitzkrieg, Imperium, The Russia Campaign, and maybe one other one. cgmclellan.
What we need to know from you is for those games, which content belongs with your project, so we can make a new project page for you.
If you need to refer to the old module pages, you can find them [here](https://vassalengine.org/wiki_old/wiki/).
Please reply by private message, not in this thread.
---
### Author:  [@cgmclellan](https://forum.vassalengine.org/u/cgmclellan)
#### Post date: [August 4, 2025, 5:36pm UTC](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164/422 "2025-08-04T17:36:15Z")
I don’t know what "markdown, BBcode, or HTML to format mean. Also, I do not know how to do "private message.
I understand that you need me to identify those elements that I am responsible for, is that correct?
I understand that the list is for those modules that are a little confusing and need some definition as to what belongs with whom, Is that correct? I identified those modules on the list that I remember I have made modules for. There were plenty of other modules and some have received additional efforts by others.
In Afrika Korps for example, a guy said he was going to “fix” the grid. I had used Avalon Hill’s rather old odd grid system to identify each hex. Others wrote me later that he kind of messed up the grid, but I never went about correcting his errors.
There were a few more VASSAL modules that had multiple modules and stuff. There were also a few modules that are posted on Decision Games’ site and not on VASSAL.
How am I supposed to identify those modules and files that I am responsible for? I am rather computer stupid, so I need detailed instruction.
Thanks, Charles
[Previous page](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164.md?page=20)
[Next page](https://forum.vassalengine.org/t/switching-to-the-new-module-library/85164.md?page=22)