Hunting Quest

# Hunting Quest 1.0.1

This is the first formal release after the `1.0.0-hotfix` test build.

Hunting Quest is a Monster Hunter-inspired quest board for Minecraft 1.20.1 Forge. Choose a slaying or gathering quest, travel to a prepared destination, complete the objective and return with your rewards.

## What is included

- Hunt quests and gathering quests.
- Main quests, side quests and one urgent quest per rank.
- Rank progression without a fixed three-star maximum.
- Per-player quest completion records. Completed quests can be replayed and remain marked as completed.
- Dimension, biome and structure destinations.
- Safe destination selection for surface, underground, ocean, Nether and End locations.
- Temporary camps with a camp marker, respawn anchor and supply chest.
- Temporary supply cleanup, battlefield restoration and quest-area cleanup.
- Quest loading screens with actual search, chunk-loading, safety-check and return progress.
- Target tracking, target glow and target health bars for non-vanilla-boss targets.
- Solo mode and party mode with confirmation from invited players.
- A visual quest editor with live preview, search, filters and scrollable lists.

## How to play

### Guild Core

The Guild Core is available in the Functional Blocks creative tab. It can also be obtained with:

```text
/give @s hunting_quest:guild_core
```

Place the core to create the quest board and the decorative guild receptionist.

Right-click the quest board to browse quests. Right-click the receptionist to switch between solo mode and party-confirmation mode.

To remove the complete counter, break the Guild Core. No special tool is required; it can be broken by hand or with any tool, drops itself and removes the linked board and receptionist models.

### Accepting a quest

1. Right-click the quest board.
2. Choose Main Quest or Side Quest.
3. Choose an unlocked rank.
4. Select a quest to open its details.
5. Review the objective, destination, target, reward, time and description.
6. Confirm the quest.

The server then searches for the destination, preloads chunks, finds a safe arrival position, prepares the temporary camp and waits for the destination to stabilize.

### Rank unlocks

- New players begin with rank 1 quests.
- Complete all enabled main quests in the current rank to unlock that rank's urgent quest.
- Complete the urgent quest to unlock the next rank.
- Side quests do not unlock the next rank.
- There is no fixed three-star limit. Higher ranks can be created in the editor.

### Hunt quests

Hunt progress counts matching entities killed by a participating player or their tamed pet during the expedition. The target does not have to be one of the mobs spawned by Hunting Quest. Spawned targets are only a fallback to ensure that the requested creature can be found.

### Gathering quests

Gathering progress counts newly obtained target items after the expedition begins. Items already carried before entering do not count. When the required amount is reached, the objective items are consumed and the quest is completed.

### Party mode

The leader confirms the quest while nearby players are within 16 blocks. Each invited player must accept the invitation before the party enters the expedition. Invitations expire after 30 seconds. The party shares the destination and objective, while each member receives their own reward and completion record.

## Quest end conditions

### Successful quests

Rewards and progression are granted when the objective is completed. Victory music then plays while the party can move freely for 30 seconds. During the final 10 seconds, a return countdown is shown. Afterward, the loading screen cleans the camp, drops, quest targets and recorded battlefield changes before returning each player to their original location and respawn settings.

### Failed quests and deaths

Hunting Quest keeps normal Minecraft death and respawn events intact. The temporary camp is used as the expedition respawn location. After three deaths by the same player, the expedition fails and returns through the cleanup loading flow.

### Abandoning a quest

At the temporary camp, right-click the wool flag or another camp abandon marker. The first click shows a warning. Right-click the same marker again within five seconds to confirm abandonment. Failed and abandoned quests skip the 30-second victory wait and begin cleanup immediately.

Disconnecting or leaving the quest dimension also removes the player from the expedition, restores the original respawn data and clears temporary supplies. If no party member remains online, the quest area is cleaned up.

## Visual Quest Editor

Players with permission level 2 or higher can open the editor with:

```text
/huntingquest editor
```

The editor can also be opened through a configurable key binding. The left side edits the task and the right side shows a live detail preview.

Available fields include:

- Rank, with no fixed maximum.
- Main, Side or Urgent role.
- Hunt or Gather type.
- Title and description.
- Dimension, biome and optional structure.
- Target entity or target item.
- Target quantity and hunt target distance.
- Reward item, reward quantity and experience levels.
- Preferred time of day.
- Enabled or disabled state.
- Requirements and `ALL`/`ANY` requirement logic.

Tasks are saved on the server at:

```text
config/hunting_quest/tasks.json
```

In multiplayer, the server copy is authoritative. Only operators can save task changes.

## Requirements and unlock conditions

Requirements are checked when the board is opened and again when a quest is accepted. A task that does not meet its requirements is hidden and cannot be started by a direct request.

Requirements can use:

- A completed Hunting Quest task.
- A minimum Hunting Quest rank.
- A completed vanilla or modded advancement.
- A completed FTB Quests task.
- A GameStages stage.
- A loaded mod ID.

Use `ALL` when every requirement must be satisfied. Use `ANY` when satisfying at least one requirement is enough. These requirements do not bypass the normal Hunting Quest rank and urgent-quest progression.

## Compatibility

### Modded content

Mobs, items, biomes, structures, dimensions and advancements are read from the active server registries. Modded content can therefore be selected in the editor when it exists and passes server-side validation.

### FTB Quests

When FTB Quests is installed, the editor can display the real FTB quest catalog and group quests by their actual chapter metadata. A Hunting Quest task can require a specific FTB quest to be completed. Completion follows the player's FTB team data.

This integration is a prerequisite check only. It does not create FTB objectives, advance FTB tasks, grant FTB rewards or edit FTB quest files.

To test it:

1. Install FTB Quests on the client and server.
2. Run `/huntingquest editor` as an operator.
3. Add an `FTB quest completed` requirement to a task.
4. Select an FTB quest and save.
5. Confirm that the Hunting Quest is hidden before the FTB quest is completed.
6. Complete the FTB quest and reopen the Hunting Quest board.
7. Confirm that the task is now available if its rank progression is also unlocked.

### GameStages

GameStages can be used as a task requirement by entering the exact stage ID. Hunting Quest reads the stage state but does not grant or remove stages.

### Monster Expansion

Monster Expansion is optional. When installed, compatible built-in high-rank hunts become available. Without it, those tasks are hidden and the rest of Hunting Quest continues to work.

## Configuration

Configuration file:

```text
config/hunting_quest-common.toml
```

Disable all built-in tasks while keeping custom tasks:

```toml
[tasks]
enableBuiltInTasks = false
```

Disable automatic Guild Core generation in newly loaded village chunks:

```toml
[world]
generateVillageGuildCores = false
```

## Community feedback

The requests for modded content, FTB Quests compatibility, clearer Guild Core removal and progression/stage compatibility are covered by this release through registry-based selectors, optional integrations and editor requirements.

A public Discord server is not available yet. It may be considered later if the project grows enough to justify a dedicated support community.