EDIT: After testing all of this again and fixing a bug or two, I have revised the set of instructions reminders. I will place a copy of the Instructions on the VASL repo Wiki.
(1) Boards
When pushing new boards/board versions to the VASL repo it is necessary to push an updated version of the associated .xml file as well.
The new/updated board files (bdXX) should be placed in the VASL/boards/bdFiles folder.
If the board supports los checking then, for new boards, create a folder with the board name (bdXX) in the VASL/boards/src folder and then place a copy of all of the individual files from the bdXX zip file into this new folder. For updated boards, place the new version of the revised files into the existing VASL/boards/src/bdXX folder.
Update the v5boardVersions.xml file in the VASL/boards folder.
(2) Overlays
For new overlays or new versions thereof it is necessary to update both the VASL repo and the VASL.info repo on GitHub.
For the VASL repo on github, push an updated version of the v5overlayVersions.xml file as well. Push the .xml file to VASL/boards, push the overlay file (ovrXX) to VASL/boards/bdFiles/overlays and push any new/revised images in the overlay file to VASL/boards/bdFiles/overlays/images.
For the VASL.info repo, depending on the overlay, either add the revised overlay (ovrXX) to the Standard_overlays.zip file or push it up as a new overlay to the vasl-website/boards/overlays folder on github. Update the html in vasl-website/overlays.htm as required.
(3) Extensions
For new extensions or new versions thereof it is necessary to update both the VASL repo and the VASL.info repo on GitHub.
For the VASL repo on github, it is necessary to push an updated version of the extensionVersions.xml file to VASL/dist,
For the VASL.info repo, push the new or revised extension (XXX.vmdx) to the vasl-website/extensions/e6 folder on github. Update the html in vasl-website/extensions.htm as required.
In all cases, when updating the .xml files for new/updated boards, overlays or extensions please update both the version number and the date of the new version.
Board and overlay files are checked for new/updated versions when selected via Boardpicker AND when used in a saved game file (.vsav/.vlog) that is opened on the device running VASL.
At present, extension versions are not checked at start up (when extensions are loaded) but are only checked when a loaded game file is updated from a previous VASL version to the new VASL version using the newly-reactivated Game Update function.
EDIT: After testing all of this again and fixing a bug or two, I have revised the set of instructions reminders. I will place a copy of the Instructions on the VASL repo Wiki.
(1) Boards
When pushing new boards/board versions to the VASL repo it is necessary to push an updated version of the associated .xml file as well.
The new/updated board files (bdXX) should be placed in the VASL/boards/bdFiles folder.
If the board supports los checking then, for new boards, create a folder with the board name (bdXX) in the VASL/boards/src folder and then place a copy of all of the individual files from the bdXX zip file into this new folder. For updated boards, place the new version of the revised files into the existing VASL/boards/src/bdXX folder.
Update the v5boardVersions.xml file in the VASL/boards folder.
(2) Overlays
For new overlays or new versions thereof it is necessary to update both the VASL repo and the VASL.info repo on GitHub.
For the VASL repo on github, push an updated version of the v5overlayVersions.xml file as well. Push the .xml file to VASL/boards, push the overlay file (ovrXX) to VASL/boards/bdFiles/overlays and push any new/revised images in the overlay file to VASL/boards/bdFiles/overlays/images.
For the VASL.info repo, depending on the overlay, either add the revised overlay (ovrXX) to the Standard_overlays.zip file or push it up as a new overlay to the vasl-website/boards/overlays folder on github. Update the html in vasl-website/overlays.htm as required.
(3) Extensions
For new extensions or new versions thereof it is necessary to update both the VASL repo and the VASL.info repo on GitHub.
For the VASL repo on github, it is necessary to push an updated version of the extensionVersions.xml file to VASL/dist,
For the VASL.info repo, push the new or revised extension (XXX.vmdx) to the vasl-website/extensions/e6 folder on github. Update the html in vasl-website/extensions.htm as required.
In all cases, when updating the .xml files for new/updated boards, overlays or extensions please update both the version number and the date of the new version.
Board and overlay files are checked for new/updated versions when selected via Boardpicker AND when used in a saved game file (.vsav/.vlog) that is opened on the device running VASL.
At present, extension versions are not checked at start up (when extensions are loaded) but are only checked when a loaded game file is updated from a previous VASL version to the new VASL version using the newly-reactivated Game Update function.