All versions
1.1.3
Release
Quests Cobb 1.1.39 months ago 86
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Changelog (v1.1.3)
Added
-
New RCT-API (rct-api) quest tracking (best-effort, reflection-based):
- Tracks RCT-API battle lifecycle events:
RCT_API_BATTLES_STARTEDRCT_API_BATTLES_ENDED
- Tracks trainer registry lifecycle events (player trainers only):
RCT_API_TRAINERS_REGISTEREDRCT_API_TRAINERS_UNREGISTERED
- Tracks RCT-API battle lifecycle events:
-
New persistent counters stored in QuestsSavedData.PlayerProgress
rctApiBattleStartedCountrctApiBattleEndedCountrctApiTrainerRegisteredCountrctApiTrainerUnregisteredCount
Changed
- Docs updated:
CUSTOM_QUESTS_API.txtnow documents the new RCT-API quest types under a dedicated “RCT-API quest types (best-effort)” section.
Notes
- Integration is optional and safe: if
rct-apiis not installed/available, listeners are not registered and nothing breaks.
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:AE9CEHCV:x4xucffn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AE9CEHCV:x4xucffn"
}

