Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 4 months ago
Updated last month
All versions
0.1.0
Release
MCA: Quests 0.1.05 months ago 27
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
[0.1.0] - 2026-06-18
First public release. Built for Minecraft 1.20.1 / Forge, requiring MCA Reborn 7.6.x and Architectury API. Prod-tested against MCA Reborn 7.6.20.
Added
- In-menu Quests button injected into MCA Reborn's villager interaction screen (client mixin), gated by config.
- Conversation UI — multi-offer cards showing each quest's title, dialogue, objectives, and reward summary, with inline Accept / Decline / Complete / Abandon.
- Quest engine (server-authoritative, datapack-driven):
- 10 objective types: item delivery, obtain, craft, fish, kill entity, break block, place block, visit biome, visit dimension, talk to profession.
- 7 reward types: item, XP, XP levels, status effect, loot table, command (disabled by default), and MCA hearts.
- 12 condition types +
all_of/any_of/notcomposites for gating offers. - Profession matching (strict / normalized / loose), 5 turn-in modes, cooldown/once repeat rules, and weighted, per-day-deterministic offer selection.
- 69 built-in quests across every vanilla profession (4 each), jobless villagers and nitwits (6, shared), the MCA guard (5), and bonus quests for MCA archers, adventurers, and mercenaries.
- Quest tracking — keybind-toggled Quest Log, a fully repositionable HUD tracker (anchor + X/Y offset) that names the quest giver, and a toast + sound when a quest is ready to turn in.
- Persistence — quest state lives on the player (Forge capability), surviving death, dimension changes, villager unload, and restarts.
- Java API + Forge events —
McaQuestsApifor add-ons to register custom objective/reward/condition types;QuestAccepted/Ready/Completed/Abandoned/Failedevents on the Forge bus. - Commands —
/mcaquests list,validate,reload,export-schema, anddebug villager. - Configuration — common (gameplay) and client (visual) config, including a villager auto-follow toggle (off by default), chat confirmations, hearts-reward scaling/clamps, offer/cooldown tuning, and HUD placement.
- Documentation —
README.md,CONFIG.md(every option), andDATAPACK.md(full quest schema + a datapack-authoring walkthrough).
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:7Cq2Y0Rq:qeuBAbUu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7Cq2Y0Rq:qeuBAbUu"
}

