MCA: Quests

[1.0.0] - 2026-07-16

The big new feature in this release is optional FTB Quests support, so MCA: Quests and FTB Quests can now talk to each other (details in the new FTBQUESTS.md). It's completely optional in both directions — you don't need FTB Quests installed, and if you do have it, nothing about your existing MCA: Quests setup changes.

This release also gathers up some fixes that had been waiting since 0.9.1, cleans up the quest screens, and adds a way to drop a quest that's gotten stuck.

Added

• FTB Quests support (optional). If you run both mods, you can now:
  • Complete FTB quest tasks by making progress in MCA: Quests — finishing quests and chains, gaining reputation or titles, contributing to village projects, resolving situations, earning hearts, or getting married (ten task types in all).
  • Earn MCA: Quests rewards straight from your FTB book — village reputation, hearts, or a title. If there's no villager or village to give the reward to at that moment, it's held and granted automatically later (on login, and once per in-game day while you're online).
  • Have MCA: Quests read and react to your FTB book, too — quests can check FTB progress and mark FTB tasks complete.
  • Pick FTB ids from a dropdown in the editor (built from what your server knows) instead of typing them by hand.
  • Use new /mcaquests ftbq status | validate | recheck commands and a new [compat.ftbquests] config section (see CONFIG.md).
• Abandon a quest from the Quest Log. Every active quest now has an Abandon button with a confirmation prompt. It works just like abandoning at a villager (no cooldown or penalty) but doesn't need the quest giver to be around.
• New tools for other add-on makers — extra events, a per-player progress snapshot, and several new helper methods behind the scenes. (Only relevant if you're building your own add-on.)

Changed

• Clients and servers must now match versions. The network version went up, so an older client can't connect to a newer server (or vice versa) — update both together. Your save files are fine and need no changes.
• Clearer admin messages. Title commands now show both the character name and the Minecraft username when they differ, so you can tell exactly whose title you changed.
• Naming a custom variable player is now blocked and flagged by /mcaquests validate, because it clashed with the built-in {player} and could behave inconsistently. Just rename the variable.

Fixed

• Quest cards no longer spill off the screen. When a villager offered several quests, the cards used to run past the bottom and cover the buttons — sometimes even stealing your clicks. The list now scrolls with the mouse wheel and has a scrollbar. Same fix applied to the village project screen and the Quest Log.
• Stuck quests can always be cleared now. Previously, if a quest giver died, despawned, or wandered off, you had no way to abandon their quest — it sat in your log forever. The new Quest Log Abandon button fixes this. A quest whose definition was removed from a datapack also still shows (under its raw id) so you can drop it.
• {player} in template quests works again — it no longer trips the validator or blocks loading.
• Custom accept/complete messages now show up in chat even without the Conversations add-on, instead of only the generic "Quest accepted/completed" text.
• Players without an MCA name are called by their username again instead of "Unnamed Adventurer."

Compatibility

• Fully save-compatible — existing worlds and datapacks load as-is, no migration needed. New progress tracking simply starts fresh from your first load on 1.0.0.
• Older clients (0.9.x and earlier) can't connect — this is intentional. Update client and server together.