### Fixed
- **Each jar now refuses to load on the next Minecraft line.** The NeoForge, Forge and Fabric metadata
declared only a minimum Minecraft version, so a jar built for one line (e.g. 26.2) would load on the
next (26.3) and crash at runtime on a changed method signature. Every build now caps its range at the
next minor line (26.1.2 → `<26.2`, 26.2 → `<26.3`, 26.3 → `<26.4`), so the loader shows a clear
version mismatch instead.
### Changed
- **Recovered saved data no longer reports as a crash** (MC-NEROSPACE-S). When a corrupt `.dat` is
recovered from backup or restarted fresh, the handled report is now sent before the error is logged,
so the handled event wins the per-session de-duplication instead of an unhandled duplicate.
- **Registration failures on NeoForge and Forge are reported at their source** (MC-NEROSPACE-R / -8).
A block or item whose constructor throws during registration is now captured with its real exception
before being rethrown, instead of surfacing only as the follow-on "Trying to access unbound value"
errors that named the victim rather than the cause. Loading fails exactly as before.
Crash reports stay anonymous and opt-out (`telemetryEnabled = false`); see [PRIVACY.md](PRIVACY.md).
Developer information
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle.
maven { name = "Modrinth"; url = "https://api.modrinth.com/maven" }