Notes on how to perform various tasks related to maintaining the mod loader.
- Finish up your changes on the master branch
- Increment the version in
modApi.version
variable, inscripts/mod_loader/modapi/init.lua
. - Prepare package zip
-
GitHub workflows:
- Run the
Package
GitHub workflow, replacing the default version input (#.#.#
) with desired version, eg.2.6.3
- When the job completes, the properly named artifact will be available for download
- or -
- Run the
-
Manually:
- Run
package.bat
script - it will produce a file namedITB-ModLoader-#.#.#.zip
- Replace the
#
with appropriate version numbers, eg.#.#.#
to2.6.3
- Run
-
- Prepare a new release
- Navigate to the Releases page on the mod loader's GitHub repository page
- Click
Draft a new release
button - Fill out the tag version and release title fields with the version number, prefixed with
v
- So for version
2.6.3
, the tag and release name will bev2.6.3
- So for version
- Write out the changelog for the release, briefly summarising all changes made since last release, with links to relevant wiki pages on the mod loader's GitHub wiki.
- It's useful to prepare the draft as soon as there's a change, and prepare the changelog entry for it. This way you don't have to recall features you've implemented several weeks/months back.
- Attach the zip file to the release
- Publish the release
- Update releases, links, and write update posts for:
- Nexusmods
- Brief release notes, link back to GitHub release page for full notes
- Upload ZIP package
- Subset forums thread
- Edit original post - update thread title & download links, pointing to GitHub release page
- Post brief release notes, link back to GitHub release page for full notes
- Discord
#modding-discussion
channel- Brief message that a new version is available, possibly mention major milestones, link back to GitHub release page
- Nexusmods
Navigate to https://github.com/kartoFlane/IntoTheBreachLua (or your fork) - the README has instructions on how to build the .dll