I thought about posting this in the megathread related to the new module library, but figured others may want to know how to do this and it may get lost in that thread.
I just submitted the newest version of the Combat Commander:Europe main module. The upload worked wonderfully. But now there’s a v2.6.3 sitting above v2.6.4. 2.6.4 is both in the filename and in the internal module setting.
How do I go about moving the older version out of the current package?
I’m using a different page here where I’m a project owner just as an example. The order of operations should be:
+ to the right of the project nameIt looks to me like you probably clicked the + to the right of the existing version number and uploaded a file there. Is that correct?
You correctly guessed what I did. Given that there are a lot of extensions that are 2.6.1 thru .3, will adding the new version number cause them to get moved down with the 2.6.3 module? Will creating the 2.6.4 project cause the 2.6.4 module to automatically move up to the new project? Or will I need to re-upload everything?
I know that there are a lot of much bigger issues that have been getting tackled with the move to the new library, but at some point a FAQ on this should be created (if there is one already, please point me to it!).
I have a similar issue trying to clean up the ‘A Game of Thrones 2ed’ page but can’t fix it following the instructions above (Or I am misreading it).
I don’t see a + sign next to the project name. Nor am I confident what is meant by ‘Project Name’. Is that the package name '2.0.0? Or the game name ‘A Game of Thrones: The Board Game (Second Edition)’ located at the top?
There is an edit pencil that appears next to the word ‘Project’ on the page, not a plus sign, but it appears to be only for the list of contributors to the page.
To get the result below, I believe I clicked on the + sign next to the Packages, entered 2.0.0, then uploaded AGOT2ED2_0_0.vmod, but it appears below all of the other non-existent modules despite my module being both the newest and with the highest vassal version number.
The problem you’re having is that you are creating packages when you should be creating releases inside packages.
Projects contain packages.
Packages contain releases.
Releases contain files.
I tried adding a new package name as below, but it still placed that addition at the bottom of the long list of version numbers that do not exist.
Would you like all of the packages except A Game of Thrones 2ed to be removed?
Thats a complex question due to the number of different vassal versions for the original game and the physical game expansions to the original game.
My suggestion would be for the layout to be as follows. My reasoning for this follows the multi language version below.
A Game of Thrones 2ed (2011)
A Game of Thrones 2Ed - Expansion: Mother of Dragons (2018)
A Game of Thrones 2ed - Expansion: A Feast for Crows (2013)
A Game of Thrones 2ed - Expansion: A Dance with Dragons (2012)
A Game of Thrones 2ed - Vassal Expansion: The Winds of Winter
A Game of Thrones 2ed - Vassal version for 9 players
A Game of Thrones 2ed - Multi Language Version
Reasoning: A game of Thrones 2ed (2013) is the original game box as produced by Fantasy Flight Games. A mother of Dragons, A Feast for Crow, and A Dance with Dragons are all official Fantasy Flight expansions. The Winds of Winter appears to be a fan created expansion using the cards from the A Game of Thrones Living Card Game which is an entirely different boxed game by Fantasy Flight Games which is why I labeled it a vassal expansion. The 9 player version appears to be an older vassal version of the game expanded to allow nine players, and the multi language version the same but with enhancements for multi language.
There are older versions less detailed than my version by other contributors of the original boxed set, so I’m not sure how to handle those as far as inclusion or not.
I went ahead and updated the ‘A Game of Thrones 2ed’ page as per above. Now the owners of each of those vassal module versions should go in and upload their most recent version to appropriate package version that matches their game.
All of the version numbers above the 'A Game of Thrones 2ed title to include the redundant 2.0.0 module should be deleted. I can do that once controls for that ability are given.
Thanks again for all of your support.
Well, I created a new project for Combat Commander Europe. I thought I was doing things correctly, naming it 2.6.4 (the most up-to-date version of the main module). I’m starting to think I was supposed to maybe name it Module or possibly I should have clicked the + next to the Module heading that already existed. It’s now showing two current versions, the current and the previous, highlighted in green.
I’m not seeing anyway for me to correct this.
Any chance one of the mods with that power could clean it up?
Direct link to the module page: Module Library - Vassal
It looks like this time you clicked the other wrong + sign available to you. You almost certainly want just one package on your page, with multiple versions. To upload a new version and get older ones “shifted down” into the collapsed older versions:
That is what I did. How do I fix it?
I’m trying to understand the state of things with CC:Europe. Is the problem that you created a package named 2.6.4 and put the 2.6.4 release into it instead of putting the 2.6.4 release into the Module package as you intended?
If that’s the case, please let me know and I can move the 2.6.4 release for you. If I haven’t understood correctly, please explain further so that I can understand.
Re: Game of Thrones: I’ll return to deal with that tomorrow, as it’s getting late now.
What I put in the 2.6.4 package should be moved down to the module. Some of what I added to the 2.6.4 package is the same as what’s currently in the module package as I wanted to make sure all the most current versions of the extensions were all in the same place.
So, whatever is in Module/2.6.3-1 should be considered old, and everything that’s in 2.6.4 should be moved into the Module.
I’ve moved the 2.64 release into the Module package for you. You should now be able to delete the empty package.
Empty package deleted. Thank you for helping clean it up!
