ModSync

[0.4.1] - 2026-01-22

Fixed

• Self-upgrade crash: Fixed crash when trying to upgrade to the same version (now skips with "already at target version")
• Bootstrap auto-update disabled: Bootstrap plugin can no longer be auto-updated due to file locking issues (both old and new would be loaded). If a bootstrap update is available, a hint is shown for manual update.

tl;dr

Fixed self-upgrade crashes when target files are locked. Bootstrap updates now require manual installation.

[0.4.0] - 2026-01-22

Added

• Self-upgrade command: /modsync selfupgrade [check|apply] to check for and install ModSync updates directly from GitHub Releases
• Version display: Plugin version is now shown in logs on startup and via /modsync status
• Build-time version: Version is now embedded at build time via generated BuildInfo.java
• Semantic versioning: Full support for comparing versions including prereleases (e.g., 1.0.0-alpha < 1.0.0)
• Config options: New settings checkForPluginUpdates and includePrereleases for self-upgrade behavior

Changed

• Atomic mod installation: Mods are now validated (manifest, hash) before being moved to their final location - no more orphan files if validation fails
• Resilient downloads: Both mod downloads and self-upgrades now use retry logic (3 attempts with exponential backoff) and fallback file operations

Fixed

• Orphan mod files: Fixed issue where downloaded mods could remain in the mods folder without being tracked if manifest reading failed
• File move crashes: Download operations now gracefully handle locked files and filesystem errors

tl;dr

ModSync can now update itself! Use /modsync selfupgrade check to see if a new version is available, and /modsync selfupgrade apply to install it. Downloads are now more reliable with automatic retries and proper cleanup on failure.