All versions
1.1
Release
Quests Cobb 1.19 months ago 64
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Changelog (1.1)
Added
- Custom quests (data-driven) loaded from:
config/quests/categories/*.json(one JSON file per category)- toggleable via
config/quests/quests.json:enableBuiltInCategoriesenableCustomCategories
- Custom rewards per quest:
- multiple items
- money
- multiple server console commands (perm level 4) with
{player}placeholder
- Auto-generated documentation:
config/quests/CUSTOM_QUESTS_API.txt(English)- includes JSON format, supported quest types, params, reward format, examples
- Expanded “quest type” API (Cobblemon integrations) for custom quests:
- berries harvested, fossils revived, trades completed
- XP gained (sum), EV gained (sum)
- healing count + heal amount (sum)
- Pokémon fainted count
- Pokémon sent/recall counts
- level-up count
- friendship update count
- Expanded “quest type” API (RCT integrations, best-effort via reflection):
- total defeats, distinct defeats
- defeated trainer IDs count
- defeats for a specific trainer ID
- series progress (remaining / completed)
- “current series is …” boolean (1/0)
Changed
- Quest menu payload now optionally merges custom categories with built-in categories (config-controlled).
- Reward claiming now supports custom reward IDs:
reward_custom_<categoryId>_<questId>
Fixed
- FR translation for shoulder quest: escaped apostrophe so
{0}is formatted correctly (MessageFormat). - Reward claim “Impossible de donner la récompense”:
- corrected waystone ID to
fwaystones:waystone - made the waystone reward optional (does not block claim if missing)
- corrected waystone ID to
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:6suiXghS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AE9CEHCV:6suiXghS"
}

