1.0.0
Compatibility
Changes
First version published outside the platform.
- 9 triggers, 8 conditions, 14 actions. The full catalogue is public: https://nimblock.com/spec/catalogue-1.json, with its validation schema at https://nimblock.com/spec/plugin-1.schema.json
- Specs go in
plugins/NimBlock/specs/, one.jsonfile per plugin. /nimblock reloadre-reads specs without a restart./nimblock listshows what is loaded. A command created by a spec only appears after a restart: Paper only accepts new command names during startup.- A spec is accepted or rejected as a whole, never rule by rule. Rejections are one red line in the console.
- Nothing leaves the server: no telemetry, no stats, no license check. The only compile dependency is
paper-api.
specVersion is 1, and the engine refuses a spec whose specVersion it does not know rather than running half of it. A spec written today keeps running on later engines of the same specVersion.
Requires Paper 26.1.2 and Java 25.
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:FrUsTKwB:ENmWarcL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FrUsTKwB:ENmWarcL"
}

