1.0.15
Compatibility
Changes
What's new in v1.0.15
Auto-Updater
MCSL now checks Modrinth for new releases automatically and downloads updates in the background — no manual JAR swapping required.
How it works:
- On startup (2s after load) MCSL queries the Modrinth API for the latest release
- If a newer version is found, ops receive an in-game notification with the version number and changelog snippet
- The new JAR is downloaded into
plugins/update/— Bukkit's standard update folder — which is applied automatically on the next restart - Ops are notified to restart when ready
Periodic checks: By default the check also runs every 6 hours while the server is online, so long-running servers don't miss updates.
Manual check: /mcsl update triggers an immediate check on demand.
Cancel a pending restart: /mcsl update cancel — if auto-restart is enabled and counting down, this aborts it cleanly.
New config keys (under auto:):
| Key | Default | Description |
|---|---|---|
update-check |
true |
Enable/disable the updater entirely |
update-channel |
release |
Track release, beta, or alpha builds |
update-check-interval |
6 |
Hours between periodic checks (0 = startup only) |
update-restart-delay |
60 |
Countdown seconds before auto-restart (when enabled) |
update-auto-restart |
false |
Auto-restart the server after downloading — off by default |
Auto-restart is disabled by default. When off, MCSL downloads the JAR silently and tells ops to restart at their convenience. Enable auto.update-auto-restart: true if you want a fully hands-off update flow with a 60-second countdown and automatic shutdown.
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:PvG9MjJ3:wLQOAKMZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PvG9MjJ3:wLQOAKMZ"
}

