Creators
Details
3.0.6
Compatibility
Changes
ProgressiveStages 3.0.6
Quest and integration rewards
Trusted server integrations can now use ProgressiveStagesAPI.grantStageFromSourceWithDependencyBypass to award one stage even when its prerequisites are unmet.
- ๐ฏ The override affects only the requested stage. It does not award prerequisite stages or independent ownership.
- ๐ The call requires an online level-3 operator, the server thread, a stable source identity, and a printable audit reason. The server log records the actor, owner, stage, source, reason, and mutation revision.
- ๐ก๏ธ Stage existence, slot limits, ownership, purchase rules, and source policy still apply. Repeating the same source grant creates no new mutation.
- ๐ฆ No configuration migration is required.
For the API signature and integration details, see the ProgressiveStages API documentation.
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:rY4mdP4Q:BTzuIQDe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rY4mdP4Q:BTzuIQDe"
}

