2.0.0-rc.1
Compatibility
Changes
Commands
All commands require serversteady.admin (operators by default). In the panel console, omit /.
Command
Purpose
/steady status
Current health, sample age, memory, tick-window statistics and sampler timing
/steady worlds
Read current world view and simulation distances
/steady history
Up to 30 recent incident/recovery messages
/steady report
Queue a local diagnostic report; limited to one request per 30 seconds
/steady reportstatus
Check whether a report saved or failed
/steady pause
Stop monitoring and tick collection; no gameplay settings need restoration
/steady resume
Resume read-only monitoring after a fresh warmup
/steady reload
Validate settings.yml and restart warmup; invalid settings leave the current state active
/steady help
Show command help
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:9DNHe7uv:j20CSmJA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9DNHe7uv:j20CSmJA"
}
