Instructions for how to update your mod on Thunderstore
Packages can be updated with new versions (you cannot modify existing versions) through the same page that you uploaded the original package.
Unzip your original package.
Add or modify your README.md, CHANGELOG.md, code, and other assets.
Modify the manifest.json file's version_number field to a higher version number. Do not modify the name field or it will be uploaded as a new package instead of updating the old one.
Upload it again under the same Team (otherwise it will be uploaded as a new package instead of updating the old one).
Version numbers follow the semantic versioning syntax without suffixes, and the highest available version will be displayed on the website & mod manager as the latest version.
Be careful with semantic versioning, v1.0.20 is higher than v1.0.3
Example of modifying the manifest.json:
{"name":"ExamplePackage","version_number":"1.0.0","website_url":"","description":"This is an example","dependencies":[]}
{"name":"ExamplePackage","version_number":"1.0.1","website_url":"","description":"This is an updated example!","dependencies":[]}
Package versions are immutable! Once a version is successfully uploaded, it can no longer be edited. Any further changes (including README.md edits) will require uploading a new version. Immutability is required for the ecosystem to offer conflict-freeness guarantees and efficient caching.
When updating a package, you can leave the Categories field blank and it will use the categories you selected when you uploaded your package the first time!
Changelog
Thunderstore supports CHANGELOG.md files which use the same markdown as your README.md file.
