Update a mod

Versioning (SemVer) and writing a changelog.

Developers
How-to
2 min read

Treat your mod like real software, even if it's small.

Versioning (SemVer)

Use Semantic VersioningMAJOR.MINOR.PATCH (see semver.org). Keep this string in sync with your plugin's Version property (§3.4):

  • PATCH (1.0.0 → 1.0.1) — bug fixes, a fix for a game update, no behavior change for users.
  • MINOR (1.0.1 → 1.1.0) — new, backward-compatible features or options.
  • MAJOR (1.1.0 → 2.0.0) — breaking changes (config that no longer carries over, removed features, behavior other mods/users relied on).

Changelog

Ship a CHANGELOG.md and update it every release. A simple, readable format:

# Changelog

## [1.1.0] - 2026-06-19
### Added
- Config toggle for tilt sensitivity.
### Fixed
- Crash on level load when no controllers were tracked.

## [1.0.0] - 2026-05-01
- Initial release.

Release hygiene

  • Note the game version you tested against (and the IPA build) in the README — game updates can break hooks.
  • Re-test after any Jet Island update before you mark a new version as compatible.
  • When you upload a new version to this site (§7), it goes through the same automated scan and review as a first upload — bump the version number so users (and the scanner) can tell builds apart.
  • Keep old versions available where possible; if your update only supports a newer game build, say so.


An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.