[1.2.0] - Unreleased

A major update focused on family quests, quest tracking, MCA: Reputation integration, and multiplayer-friendly target highlighting.

MCA: Reputation Integration

• Added a View Deeds link to village entries in the Journal when MCA: Reputation is installed.
• The link opens that exact village in Reputation's Standing screen.
• Reputation data is refreshed before the screen opens.
• The link is hidden when MCA: Reputation is not installed.
• Requires MCA: Reputation 0.2+.

Family Quests Now Use Real Villagers

Family quests now point to actual MCA villagers instead of only mentioning unnamed relatives in dialogue.

• Family quests remember the exact relative they are about.
• Quest dialogue, objectives, highlighting, and completion now stay focused on the same person.
• Deliveries meant for a relative must be handed to that specific villager.
• Existing quests automatically update without requiring a save migration.

Updated family quests include:

• A Family Feast
• In Loving Memory
• Mind the Apprentice
• Guest of Honour
• Meeting the Family
• A Parent's Plea
• Search the Old Tunnels
• Bring Them Home

Quest Target Highlighting

• Quest targets can now be outlined through walls while nearby.
• The outline is visible only to the player who owns the quest.
• Quests without a specific target highlight the quest giver instead.
• The older shared Glowing-effect behavior can still be enabled through configuration.

New Direction Tracker

The quest HUD can now point you toward the villager you need.

It shows:

• The target's name.
• Distance in blocks.
• A simple direction such as ahead, behind, left, or right.

If the target is too far away to be loaded, the tracker can point toward their last known home instead.

The direction hint disappears once the quest is ready to turn in.

Missing Relatives Can Now Be Found

Added a new find_missing_relative quest objective.

Certain quests can now involve family members who genuinely disappeared from the world.

When found:

• The original family member is restored as a real villager.
• Their name, identity, profession, and family relationships are preserved.
• They immediately become the quest target.
• They cannot accidentally spawn twice.
• An unloaded villager is no longer mistaken for a missing one.

Finding a missing relative is permanent, even if the quest is later abandoned or failed.

Family Quest Improvements

• Added support for grandparents.
• Family conditions can now properly target any relative.
• Quests that require a certain relative will no longer appear if that relative does not exist.
• Search and delivery dialogue has been rewritten to better match what the player is actually doing.

Fixed

• Fixed some family quest conditions being ignored.
• Fixed living villagers outside render distance being treated as missing.
• Fixed family-tree filler characters being mistaken for missing villagers.
• Fixed protection quests failing because a different relative died.
• Fixed the quest log, HUD, and highlight sometimes pointing to different villagers.
• Fixed titles being shared between villages in different dimensions when they had the same numeric ID.

Multiplayer Improvements

Quest highlights are now handled separately for each player.

Previously, Minecraft's normal Glowing effect could make one player's quest target visible to everyone on the server, including through some minimap and shader mods.

The new system keeps quest markers private.

Configuration

Added:

• highlightUsesGlowingEffect

  • Default: false
  • Restores the older shared Glowing-effect highlighting.

• showQuestTargetDirection

  • Default: true
  • Controls the new direction guide.

Brazilian Portuguese translations have also been updated for all new content.

Compatibility

• Requires MCA: Reputation 0.2+ for Reputation integration.
• Client and server must both use MCA: Quests 1.2.0.
• Existing world saves remain compatible.
• Add-ons using MCA: Quests' villager-target API may need a small update.

---

[1.1.0] - 2026-08-13

A major compatibility, reputation, localization, and quest-quality update.

MCA: Reputation Integration

MCA: Quests can now integrate with MCA: Reputation when installed.

• Reputation becomes the main source of village standing.
• MCA: Quests keeps a fallback copy so removing Reputation later does not erase your progress.
• MCA: Reputation remains completely optional.

Reputation Is Now Properly Per Player

Previously, everyone on a multiplayer server could accidentally share the same village reputation.

This is fixed.

• Every player now has their own standing with each village.
• Villages in different dimensions are tracked separately.
• Nether and Overworld villages with matching IDs no longer share reputation.
• Quest, project, situation, Journal, FTB Quests, and Reputation values now use the same system.

Reputation Rewards

Quests can now directly define reputation changes for:

• Completion.
• Failure.
• Abandonment.

Failure and abandonment remain penalty-free unless a quest specifically says otherwise.

Reputation rewards are also protected against accidental duplicate payouts.

Restitution Quests

Added support for quests that react to specific deeds recorded by MCA: Reputation.

This allows quests where players can:

• Be offered a chance to make amends.
• Complete restitution.
• Reduce the impact of a past deed without deleting it.

Legacy Reputation Migration

When MCA: Reputation is installed, old MCA: Quests reputation data can be imported automatically.

Existing:

• Village standing.
• Reputation tiers.
• Titles.

are carried over where possible.

Removed

Sneak-Right-Click Quest Shortcut

The old sneak-right-click shortcut for opening quests has been removed.

It could interfere with:

• MCA's villager editor.
• Trading.
• Villager inventories.
• Other mods using sneak-right-click.
• MCA: Quests' own progression detection.

The Quests button in the villager interface is now the intended way to open quests.

Fixed Quest Progress

• Fixed profession conversation objectives sometimes never progressing.
• Profession matching now properly follows the configured matching mode.
• "Talk to multiple villagers" objectives now require different villagers instead of counting repeated conversations with one person.
• Fixed the built-in cartographer search project being stuck at 0/3.
• Conversations reported through both normal interaction and MCA: Conversations are counted only once.
• Conversation progress now updates immediately.

Family Quest Fixes

• Babies and toddlers no longer offer inappropriate adult-style quests.
• Family quest objectives now clearly say that they refer to the quest giver's relative rather than the player's relative.
• Resolved relatives still display their actual name when available.

New Currency Reward System

Added a flexible mcaquests:currency reward.

Servers and datapacks can use:

• Emeralds.
• Create: Numismatics currency.
• A custom item.

Reward amounts are chosen once when the quest is accepted and stay fixed afterward.

Reloading, reconnecting, or reopening the menu can no longer reroll the reward.

Quest Difficulty

Quests can now optionally be marked:

• Easy
• Medium
• Hard

Difficulty can provide default reward ranges while leaving existing quests unchanged.

Reward Scaling

Added server configuration for:

• currencyRewardMultiplier
• xpRewardMultiplier

The amount shown on the quest card always matches the amount the player will actually receive.

Relationship Balance

Relationship rewards have been significantly reduced to prevent marriage progression from being farmed too quickly.

Built-in heart rewards are now approximately:

• Easy: 4 hearts
• Medium: 8 hearts
• Hard: 14 hearts

Hard repeatable quests also generally have longer cooldowns.

Servers can still adjust the overall speed using heartsRewardMultiplier.

More Accurate Conversation Detection

A "talk to villager" objective now requires an actual conversation.

Simply clicking a villager while holding:

• The MCA editor book.
• Another mod's interaction item.
• An item used for a different objective.

will no longer count as talking.

Brazilian Portuguese

Added complete Brazilian Portuguese (pt_br) localization for the built-in content.

This includes:

• Interface text.
• Quest dialogue.
• Quest titles.
• Objectives.
• Rewards.
• Projects.
• Situations.
• Relationship arcs.

The built-in quest pack was also converted to proper translation keys so additional translations are easier to create.

Compatibility

• Existing worlds remain compatible.
• Existing datapacks do not need to be updated.
• MCA: Reputation is completely optional.
• Clients and servers must use matching updated versions.

---

[1.0.0] - 2026-07-16

The first major release, introducing optional FTB Quests integration alongside several quest interface and dialogue improvements.

FTB Quests Integration

MCA: Quests can now connect with FTB Quests in both directions.

FTB Quests can track MCA progress including:

• Completed quests.
• Completed quest chains.
• Reputation.
• Reputation tiers.
• Titles.
• Village projects.
• Situation progress.
• Hearts.
• Marriage.

FTB Quests can also reward:

• Village reputation.
• Hearts.
• MCA: Quests titles.

MCA: Quests datapacks can likewise check or update FTB Quests progress.

FTB Quests remains completely optional.

Abandon Quests From the Quest Log

Active quests now have an Abandon button directly in the Quest Log.

This means you can remove a stuck quest even if the original villager:

• Died.
• Despawned.
• Is in an unloaded area.
• Is in another dimension.

A confirmation screen prevents accidental abandonment.

Interface Fixes

• Quest cards now scroll properly when a villager offers several quests.

• Fixed quest cards covering the Back and Project buttons.

• The same scrolling improvements were applied to:

  • Village projects.
  • The Quest Log.

• Quests whose datapack definition was removed are still shown by ID so they can be abandoned.

Dialogue Fixes

• Fixed template quests using {player} sometimes failing to load.
• Custom accept and completion dialogue now properly appears in chat.
• Players without an MCA character name now use their Minecraft username instead of being called "Unnamed Adventurer."

Admin Improvements

Admin title commands now show both the MCA character name and Minecraft username when useful, making it easier to identify the correct player.

Compatibility

• Existing worlds and datapacks remain compatible.
• Clients and servers must use matching versions.
• FTB Quests integration is entirely optional.

[0.9.1] - 2026-07-11

Address the player by their MCA character name (the name set in MCA's character-creation screen) instead of their Minecraft username wherever the mod names them. Existing saves and datapacks are unaffected — the new {player} token is optional, and every name lookup falls back to the Minecraft username when MCA is absent or no character name was set.

Added

• {player} dialogue token — quest authors can now write the player's MCA character name into any quest's dialogue, title, and chain arc/chapter text (e.g. "Well met, {player}!"), not just template quests. It is a reserved token that cannot be shadowed by a template variable named player, falls back to the Minecraft username when MCA is absent or no name is set, and is dialogue-only (never substituted into objective/reward JSON). Resolved server-side per recipient, so situation broadcasts name each nearby player correctly. Documented in DATAPACK.md.

Changed

• Admin command feedback uses the MCA name — the chat messages from /mcaquests title grant|list|clear now show the target player's MCA character name instead of their Minecraft username (with the username as a safe fallback). Debug logs continue to use the username for account-level troubleshooting.

[0.4.0] - 2026-06-19

Built for Minecraft 1.20.1 / Forge, requiring MCA Reborn 7.6.x and Architectury API. Save-data compatible with 0.1.0–0.3.0 worlds; the new village projects are additive and pre-0.4.0 worlds load cleanly. Datapack breaking change: chain.time_limit_ticks has been replaced by the new failure block (see Changed/Removed). Network protocol bumped to v2 — client and server must run matching versions (the project packets are rejected at handshake otherwise).

Added

• Quest failure states & deadlines — a new optional failure block makes a quest expire while it's active, with author-controlled triggers and outcomes. Failure is server-authoritative, persisted (the deadline is anchored to acceptance time, so it survives logout/restart), grants no rewards, and records a FAILED outcome that follow-up quests branch on via the existing mcaquests:quest_failed condition.
  • Triggers (combine freely; first to fire wins): deadline_ticks (relative deadline), deadline_time (fail at a Minecraft time-of-day, e.g. "before sunrise"), require_weather (fail when the weather stops matching, e.g. "while it's raining"), and fail_on_giver_death (per-quest, independent of the global failQuestIfGiverDies config).
  • Outcomes: failure_hearts (relationship penalty, or 0 for non-punitive), retry_after (cooldown before the quest can be offered again), and block_retry (permanent lock). The giver's dialogue.failed line is shown on failure; recovery quests are expressed with quest_failed.
  • A quest already complete ("ready to turn in") is not failed by a time/weather trigger — a grace window to hand it in. All failure paths route through one idempotent handler, so no quest ever double-fails or duplicates a completion.
• HUD deadline countdown — the quest tracker shows a live m:ss countdown for quests with a time deadline, turning red in the final minute. Weather/giver-death failures show no countdown.
• 3 built-in failure examples — guard/dawn_defense (kill zombies before sunrise), cleric/urgent_medicine (+ cleric/urgent_medicine_recovery, a recovery quest gated on quest_failed), and fisherman/rain_catch (fish while it's raining).
• Failure validation — /mcaquests validate reports a failure block with no trigger, a failure_hearts magnitude past the hearts clamp, and block_retry combined with retry_after.
• Village projects — a new, separate system of shared, multi-stage community goals loaded from data/<namespace>/mcaquests/projects/**.json. A project's progress is shared (stored in the world save, not per-player), so multiple players contribute toward one common objective. Fully additive and backward compatible — existing quests are unchanged and pre-0.4.0 worlds load cleanly.
  • 5 scopes decide who shares the progress: player, villager, family, profession, and village. The MCA-backed scopes (family/profession/village) resolve via MCA's village/ relationship data and fail safe (the project never appears) when that data is missing.
  • Phases run in order — a phase is entered only after every earlier phase completes — each with its own dialogue, objectives, rewards, and an optional unlock gate.
  • 4 project objective types that track shared progress: donate_item (items consumed and banked into the pool, with an optional per_player_cap), project_kill_entity, project_place_block, and project_talk_to_profession.
  • Shared rewards wrap any existing quest reward with a target (contributors, all_participants, sponsor_village, top_contributor) and add new reward types (hearts_with_sponsor, hearts_with_participants, village_reputation, unlock). Projects also carry independent mod-side village reputation deltas (on_phase_complete / on_project_complete / on_fail), and a new mcaquests:village_reputation condition tests a giver's reputation in any quest or project condition tree.
  • Sponsors (by profession) surface a project via a View Project button in the MCA villager menu; with oneSponsorPerProjectPerDay only one deterministically chosen villager per village offers a given project per day. Contributions are atomic and server-authoritative (items validated and consumed server-side, then banked, then synced); per-phase rewards distribute exactly once, with offline players' non-hearts rewards queued for next login and villager hearts queued via MCA.
  • 6 built-in example projects: guardhouse_stockpile, library_restoration, festival_preparation, well_repair, after_raid_recovery, and missing_villager_search.
  • Project commands — /mcaquests project list, info <id>, validate, reset <id>, advance <id> (test-only force-advance), and debug <id> (explains availability from the nearest villager); list/info/debug at op level 2, validate/reset/advance at op level 3.
  • Project validation flags unknown scope/objective/reward type ids, missing phases, and unknown/disabled or circular follow_up chains as errors, with warnings for empty non-final phases, MCA-dependent scopes while MCA is absent, disabled command rewards, and mismatched reward targets. Hard errors abort the load under strictJsonValidation.
  • A project menu, quest-log section, and HUD tracker (showProjectTrackerHud / projectTrackerMaxEntries) surface active projects and their shared progress.
  • Network protocol bumped to v2. Project sync/contribution packets require a matching client and server; mismatched versions are rejected at handshake.

Changed

• The chain.time_limit_ticks deadline is now failure.deadline_ticks — it works on any quest, not just chains, and gains the richer triggers/outcomes above. The two built-in chain quests that used it (farmer_family/3_apprentice, guard_safety/2_patrol) were migrated.

Removed

• chain.time_limit_ticks (replaced by the failure block). Datapacks still using it will fail validation; move the value to failure.deadline_ticks.

[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 / not composites 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 — McaQuestsApi for add-ons to register custom objective/reward/condition types; QuestAccepted/Ready/Completed/Abandoned/Failed events on the Forge bus.
• Commands — /mcaquests list, validate, reload, export-schema, and debug 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), and DATAPACK.md (full quest schema + a datapack-authoring walkthrough).