Minecraft quests plugin guide: Quests, BetonQuest and BeautyQuests compared

The best quests plugin depends on one question: do you want to click or type? If you want to build quests in game with menus, BeautyQuests is the pick and it was updated this week. If you are happy writing YAML and want branching conversations, BetonQuest 3.2.0 is the most powerful thing on the list. If your server is built around NPCs handing out quests, PikaMug's Quests (5.3.2) works with Citizens and ZNPCsPlus. And if all you need is "mine 64 iron, get a reward, come back tomorrow", LMBishop's Quests does that with categories and cooldowns and nothing to learn.

All four are free. This guide compares them, covers the NPC plugins they lean on, and then gets into what actually matters: the first quest as your tutorial, daily quests for retention, rewards, writing that players read, and keeping all of it cheap on the server.

Which quests plugin

Version lines matter more than usual here. Quest plugins hook deep into events, so a build listed for 1.21.10 may or may not load on 26.x. Check the project page for your exact version, and check the last-update date: LMBishop's Quests is the oldest of the four, though still maintained on GitHub.

NPC plugins that pair with them

Quests given by a person at spawn land better than quests in a menu, and three NPC plugins cover it:

• Citizens. The long-standing one, with the most integrations (all four quest plugins above support it). It is listed as a premium resource on SpigotMC, but the project says the same builds are free from its own build server; pay if you want to support it.
• FancyNpcs. Packet-based (lighter on the server), free under MIT, Paper only, and now developed inside the FancyPlugins monorepo since the old repository was archived in July 2025. BetonQuest supports it fully.
• ZNPCsPlus. Packet-based, free under GPL, 1.8 through 26.2 on Spigot, Paper and Folia, and the community successor to ZNPCs. Supported by BetonQuest and PikaMug's Quests.

Packet-based NPCs exist only on the client's screen, so they cost the server almost nothing and cannot be pushed, killed or targeted by mobs. Citizens NPCs are real entities, which is what lets them walk, fight and be used by more plugins. For a quest giver that stands still at spawn, any of the three is fine; pick the one your quest plugin supports.

The first quest is your tutorial

Most servers lose players in the first five minutes because nobody told them what to do. A quest plugin fixes that better than signs, because it tracks the player and rewards them. Write one quest that starts automatically on first join and walks through the five things a new player has to learn on your server. For a survival or towny server:

1. Talk to the guide NPC at spawn (or just read the first objective). One line: what the server is.
2. Use the random teleport or walk out of spawn. Objective: reach a location outside the spawn radius.
3. Claim a plot with your claims plugin. Objective: run the claim command or place the claim tool. This is the step that stops griefing complaints on day two.
4. Set a home. Objective: run /sethome. Now they can leave and come back.
5. Vote once. Objective: a vote event or a PlaceholderAPI check on their vote total. Reward: a crate key, so they see the whole loop in one session.

Five steps, five minutes, one reward at the end that is actually useful (a starter kit, a key, currency). The first join guide covers the message and spawn side; the quest is the part that makes it stick. Test it with someone who has never seen the server, and cut any step they hesitate on.

Daily quests for retention

A daily quest is the cheapest retention feature you can add, because it gives the regulars a reason to log in that changes every day. The mechanics are the same in every plugin: a cooldown (LMBishop's Quests calls it exactly that; BeautyQuests and BetonQuest handle repeatable quests with their own timers), a small pool of quests, and a reward that is nice but not economy-breaking. Rules that hold up:

• Three a day, not ten. One gathering, one combat, one social or building task. A wall of quests is a wall.
• Ten to twenty minutes each. Enough to get someone into the game, short enough to finish before they log off.
• Reset at a fixed time in your players' evening, the same as daily rewards, so people are online together.
• Rotate the pool weekly. Twelve quests in rotation feel fresh for months.
• Reward with keys and currency, never gear. The daily rewards guide has the reasoning; a daily quest that drops power is a grind, not a habit.

Rewards and quests players actually read

Players read the objective line and the reward line. They do not read the paragraph you wrote in between, no matter how good the lore is. Write for that:

• Objective first, in game terms. "Mine 32 iron ore" beats "The blacksmith needs materials." Put the flavor in the NPC's greeting, where it costs nothing to skip.
• One verb per stage. Kill, mine, deliver, reach. A stage that needs two things is two stages.
• Say the reward up front. If the reward is hidden, half the players assume it is nothing.
• Name real places. "Reach the lighthouse at the east dock" beats coordinates, and it teaches the map.
• Conversations get three choices at most and every choice does something. BetonQuest's conversations are excellent when they branch and tedious when they are one long monologue split into clicks.
• Reward progression, not just completion. A chain of five quests with a title at the end gives a week of goals; a hundred unconnected quests give nothing to aim at.

Rewards work best when they hand players into the other loops you run: a vote key, a cosmetic from your store catalog, entry to a weekly event. They work worst as raw currency with no sink, for the same reason every reward does.

Performance: keep quests cheap

Quest plugins listen for events: every block break, every kill, every move can be a check. On a small server that is nothing; on a busy one it adds up. A few habits keep it off your lag list:

• Avoid location objectives that poll every tick. Use region-enter events where the plugin offers them.
• Use a database, not flatfile, past a few hundred players. All four support MySQL; BeautyQuests also supports MariaDB and PostgreSQL.
• Prefer packet NPCs for decoration and quest givers. Twenty Citizens NPCs are twenty entities; twenty FancyNpcs are none.
• Profile before you blame the plugin. A spark report shows whether the quest listener or the mob farm is the problem.
• Limit active quests per player where the plugin allows it. Fewer active objectives means fewer checks per event.

Once your tutorial quest works, mention it in your listing description: "a five-minute starter quest" is exactly what a player choosing between two similar servers wants to read, and the description counts toward your listing strength.

Quick questions