1.0.1
Compatibility
Changes
SunManhunt 1.0.1
Release summary
SunManhunt 1.0.1 is a bugfix release focused on match lifecycle reliability and saved-hunt recovery. It fixes the permanent Hunter freeze after the grace period and hardens startup, teardown, reset, mode resume, and reconnect handling.
Added
- No new commands or gameplay modes.
Changed
- Active-match checkpoints now include original game modes, disconnect deadlines, remaining grace, and mode resume state.
- Imposter identity and detective state are restored across a restart.
- Shrinking Border restores its current size, milestones, pause timing, and original world borders.
- Rotating Prey rebuilds rotation candidates from the saved initial roles.
- Advancement objectives re-check player advancement progress when a saved hunt is resumed.
Fixed
- Hunters no longer remain frozen forever after the grace period. The shared tick clock was clearing its own subscribers when the hunt started.
- A throwing state-change listener can no longer abort a lifecycle transition halfway.
- Match teardown now always stops the clock, clears the checkpoint, restores players, and leaves the ending state.
/sm resetcan recover a match that was left in the ending state.- Reentrant start and stop calls can no longer activate a cancelled match or leak a tick task.
- Disconnect deadlines are checked during grace, so a Runner quitting during the freeze no longer leaves Hunters frozen until grace expires.
- A failed resume no longer blocks
/sm start,/sm join, and/sm joinallforever. - Resuming with an offline Runner now arms a reconnect deadline.
- Saved disconnect deadlines are rebased after server downtime instead of ending the hunt immediately.
- Resume preserves remaining grace and paused state.
- Resume preserves original game modes for participants who are offline at resume time.
- Resume uses saved initial roles for result settlement and statistics.
- Benched Rotating Prey Runners no longer stay spectators permanently after a resume.
- Restarting no longer re-rolls the Imposter or Detective.
- Restarting no longer resets the Shrinking Border to its starting diameter.
/sm resetno longer discards queued game-mode restores for offline players.- Queued game-mode restores are applied when a player rejoins during a later hunt.
/sm stopand/sm pauseno longer print a missing message key.- A checkpoint is no longer offered when
persistence.save-active-matchis false. - The resumed hunt now records the correct initial roles, so end-of-match statistics do not treat a Ghost or eliminated Runner as their mid-match role.
Migration notes
- No configuration or permission changes.
- Existing 1.0.0 checkpoints load with default values for the new resume fields. Mode-specific state saved by 1.0.0 is not present, so that state initializes on resume.
- Replace the old jar with
SunManhunt-1.0.1.jarand restart the server.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:pRuIm2CL:UmVq9d07"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pRuIm2CL:UmVq9d07"
}

