An RPG-style, datapack-driven quest system for MCA:Reborn villagers. Right-click a villager, open the new Quests menu, accept a job, complete it out in the world, and turn it in for sweet rewards and hearts.
New Quest Button
Example Quest
Turn your MCA villages into places where people actually need your help.
Credit to TheWiggleDuck for the awesome Curseforge project icon!
MCA: Quests adds a full RPG-style quest system to Minecraft Comes Alive: Reborn. Villagers can offer jobs based on their profession, relationships, circumstances, surroundings, and the state of their village.
Right-click an MCA villager, open the integrated Quests menu, choose an offer, complete its objectives out in the world, then return for your reward. Helping villagers can earn items, experience, currency, status effects, village reputation, titles, and most importantly, MCA relationship hearts with the villagers you help.
With more than 260 built-in quests, long-form quest chains, village-wide projects, dynamic situations, extensive quest tracking, and optional integrations with other major mods, MCA: Quests is designed to make MCA villages feel less like collections of NPCs and more like communities you can become part of.
MCA: Quests requires Minecraft Comes Alive: Reborn and Architectury API.
It is an add-on and does not function without MCA Reborn.
Villagers across the entire village can have something for you to do.
Quest content covers:
The built-in quests range from everyday errands to dangerous expeditions and community problems.
You might gather supplies for a farmer, hunt monsters for the guard, deliver something to a villager's relative, repair part of the village, cure an infected resident, explore a distant structure, escort someone home, or help an entire settlement recover from a crisis.
Quests are not limited to basic item collection.
Objectives can involve:
Optional integrations can add even more objective types.
Individual quests can connect into multi-stage relationship quest chains.
A villager might begin by asking for a simple favor, then eventually involve you in larger parts of their life or community. Chains remember what happened during earlier stages and can branch depending on whether you completed, failed, or abandoned previous quests.
Progress is associated with the villager involved, allowing different villagers to have their own ongoing stories with the player.
The interface clearly identifies the current chapter, such as Part 2 of 4, so longer quest lines remain easy to follow.
MCA: Quests can use information from MCA Reborn when deciding which quests make sense.
Quest offers can account for things such as:
This allows quests to be about the actual villagers in your world instead of anonymous placeholders.
When a quest refers to a particular family member or villager, that specific person is bound to the quest. Their name, location, objective tracking, and turn-in behavior all continue referring to the same NPC.
Villages can react to events happening around them through situations.
Situations are temporary circumstances that can generate appropriate quests when something goes wrong, such as:
Instead of every quest existing forever as a static job board entry, some opportunities appear because something actually happened.
Situations are saved with the world, throttled to avoid spam, and fully configurable through datapacks.
Some problems are bigger than a single villager.
Village Projects are shared, multi-stage community goals that players can work toward together.
Projects can involve tasks such as:
On multiplayer servers, contributions from different players can all advance the same project.
Projects can reward:
Progress is stored in the world save, making village projects suitable for long-running multiplayer worlds and modpacks.
Your actions can affect your standing with an entire village.
MCA: Quests includes its own configurable reputation progression:
Stranger -> Acquaintance -> Friend -> Honored -> Revered
Higher reputation can unlock new quests, and reaching milestones can award titles.
The built-in Journal lets you review:
Both reputation tiers and titles are datapack-driven, so modpack authors can replace or expand the progression system.
MCA: Quests includes several ways to keep track of what you are doing.
A dedicated Quest Log displays your active quests and their progress.
You can also abandon quests directly from the log, even if the original quest giver is no longer nearby.
Follow a quest to place its current objective on the HUD.
The tracker can display:
Its position can be configured by the player.
Objectives with a location can display a compact marker directly in the world.
The marker follows the objective you currently need to complete. As a quest progresses, the destination automatically changes with it.
For example, a quest might point toward a Nether portal first, then toward the actual destination once you reach the Nether, and finally back toward the villager when the quest is ready to turn in.
An optional screen-edge indicator can also show the direction of objectives that are behind you or outside the current view.
Villagers who are currently relevant to a tracked objective can be outlined for that player, making it much easier to find the correct person in a crowded village.
Quests support multiple reward types, including:
Command rewards are disabled by default for safety.
Quest rewards do not have to be hard-coded to emeralds.
MCA: Quests supports a semantic currency system where pack authors can decide what "money" means for their pack.
Currency can use:
Quests can also use difficulty levels such as easy, medium, and hard to determine appropriate payout ranges.
The reward amount is rolled when the quest is accepted and does not change afterward, so the reward shown to the player is the reward they actually receive.
MCA: Quests is designed to work as part of larger modpacks. Integrations are optional and disable themselves cleanly when the related mod is not installed.
With Townstead installed, quests can interact with much deeper village simulation.
Quest content can use:
Townstead support includes a large additional collection of quests, village projects, and dynamic situations.
Long-term objectives can follow actual Townstead simulation instead of using arbitrary timers. A quest asking a villager to work for a week, for example, can track completed work shifts rather than requiring the player to stand nearby watching a countdown.
If Townstead is removed while one of its quests is active, the quest can suspend instead of failing. Its progress is preserved until the dependency becomes available again.
With MCA: Conversations installed, quest dialogue can take place through the conversation system instead of relying only on static quest text.
Conversation-driven objectives can also require the player to actually speak with the appropriate villager.
Without MCA: Conversations, normal quest dialogue continues to work.
When MCA: Reputation is installed, the Journal can link directly to the corresponding village standing and deed information.
Without it, MCA: Quests continues using its own built-in village reputation system.
Optional FTB Quests integration allows quest books to interact with MCA: Quests progression.
FTB Quests content can read or reward things such as:
MCA: Quests datapacks can also interact with FTB Quests progression.
FTB Quests is not required.
With JourneyMap 6.0.0+, active quest destinations can automatically appear as map waypoints.
Quest waypoints move as objectives change and are removed when they are no longer needed.
Players can also create persistent JourneyMap waypoints from quest destinations.
Xaero's Minimap 26.0.0+ is also supported for quest destinations.
Automatic waypoints follow quest progress in the same way as the built-in tracker.
On Xaero-only installations, manually pinned quest destinations are session waypoints and do not persist after closing the game.
Install Create: Numismatics and configure MCA: Quests to use its coins as the global quest currency.
This allows existing and custom quests to use a modpack's economy without rewriting every quest.
Almost the entire quest system is datapack-driven.
Pack authors can add their own quests without writing Java code.
Custom quests are loaded from:
data/<namespace>/mcaquests/quests/
Village projects can be added through:
data/<namespace>/mcaquests/projects/
Situations can be added through:
data/<namespace>/mcaquests/situations/
Quest authors have access to a large collection of objectives, conditions, rewards, relationships, progression rules, quest history checks, composite conditions, dialogue pools, and integrations.
Useful commands include:
/mcaquests list
/mcaquests validate
/mcaquests reload
/mcaquests export-schema
/mcaquests export-schema generates a working quest example that can be used as a starting point for custom content.
Full datapack and configuration documentation is available in the project's GitHub repository.
Separate server/common and client configuration files are generated automatically.
Pack authors and server owners can configure gameplay behavior such as:
Players can separately configure visual features such as:
For developers, MCA: Quests exposes a Java API for registering additional:
Forge events are also available for major quest lifecycle events, including:
This makes MCA: Quests suitable as a foundation for additional MCA-focused mods and modpack-specific integrations.
Quest validation, progress, and rewards are handled server-side.
Reward delivery is designed to be atomic and resistant to packet spam or duplicate turn-ins, while shared Village Projects provide server-wide cooperative objectives.
Player-specific tracking and villager highlighting remain personal to each player.
MCA: Quests currently includes full translations for:
All built-in interface text, quest dialogue, objectives, rewards, projects, situations, and other content use translation keys, making additional community translations possible.
| Requirement | Version |
|---|---|
| Minecraft | 1.20.1 |
| Mod Loader | Forge 47.4.10 or newer |
| Minecraft Comes Alive: Reborn | Required, supports the 7.6.x and 7.7.x lines |
| Architectury API | Required |
| Mod | Purpose |
|---|---|
| Townstead | Expanded village simulation, quests, projects, situations, needs, professions, skills, buildings, and calendar integration |
| MCA: Conversations | Conversation-based quest dialogue and objectives |
| MCA: Reputation | Reputation and deed screen integration |
| FTB Quests | Two-way quest book integration |
| Create: Numismatics | Alternative quest currency |
| JourneyMap 6.0.0+ | Quest map waypoints |
| Xaero's Minimap 26.0.0+ | Quest map waypoints |
Install Minecraft Comes Alive: Reborn, Architectury API, and MCA: Quests.
Launch your world.
Right-click an adult MCA villager.
Select Quests from their interaction menu.
Choose an available quest and accept it.
Follow the Quest Log, HUD tracker, or world marker to complete the objectives.
Return to the appropriate villager and complete the quest to receive your rewards.
MCA: Quests is built to make helping villagers feel like part of living in their world rather than a separate quest system placed on top of it.
Whether you want a few extra reasons to interact with your neighbors, long-running character stories, cooperative village projects, or a foundation for a heavily customized RPG modpack, the entire system is designed to grow with the world around it.
Source, documentation, configuration reference, and datapack guide:
https://github.com/otectus/MCAQuests
MCA: Quests is an independent add-on for Minecraft Comes Alive: Reborn.