How quests work
What a player does, and the rules the plugin applies along the way.
On this page
Browsing and accepting
/quests opens the category menu. Each category opens a paged quest list (up to 18 quests per page), and each quest opens a detail view with an accept button and a reward preview. All menus are 27 slots with Back at slot 21.
- Quest and category permissions are checked when a quest is accepted.
- With
features.gui-close-after-accept, the menu closes once a quest is accepted. - With
features.quest-autotrack, the quest you just accepted becomes the tracked one.
Progress
- Every objective has its own counter, and all of them must finish before the payout.
- Exact targets. A target such as
STONEorZOMBIEmatches that material or entity only, ignoring case. A quest with no target matches any event of its type. An explicit target never matches an event that has none. - Completion pays once. Rewards cannot be paid twice for the same completion.
- Brewing credits the online player who last opened that brewing stand during the session.
Tracking
One quest at a time can be tracked, and its progress shows on screen.
tracker.display | Shows |
|---|---|
bossbar | A boss bar with the quest name and current/goal. This is the default. |
actionbar | An action bar line. |
both | Both of the above. |
off | Nothing. Players still see progress in the menu. |
Players switch quests with /quests track <quest> and stop with /quests untrack.
Quest limit
A player can have a limited number of quests active at once. The default is 1, and a rank raises it. A rank is a key under quest-limit, and a player gets it with the permission alphaquests.limit.<rank>. The highest matching value wins. See Configuration.
Repeating and cooldowns
- Repeatable quests can be done again after finishing. A non-repeatable quest is done once.
- Cooldown makes a repeatable quest wait a set time after each completion. The wait is in seconds and is shown by the
cooldown_<quest>placeholder.
Chains
A quest can list other quests under requires. It stays locked until every listed quest has been completed. On startup and on reload the plugin checks for missing references and circular chains, and logs any problem it finds.
Streaks
- A daily streak counts consecutive UTC calendar days with a completed quest. A weekly streak counts consecutive weeks, with weeks starting on Monday.
- Several completions in one period count once. They do not multiply the streak.
- With
features.streak-bonuson, money rewards are multiplied by1 + 0.05 per streak step, using the higher of the two streaks, capped at 2.0x. A streak of 20 reaches the cap. - The bonus applies to
eco giverewards only, not to XP, items or commands.
Races and the leaderboard
- Race. Staff run
/aquests race <quest> <duration>to open a timed race on one quest. The first completion of each player during the race is recorded./aquests race stopends it. An active race survives a restart. - Leaderboard. Every completion adds one point to the player weekly total, shown with
/quests leaderboard. The totals reset when a new week starts and survive restarts. - Races are controlled by
features.races.
features.parties is false by default, leave it that way.