# Quests on your Minecraft server: daily, with rewards and no mods

> How to add quests to your Minecraft server with the Quests plugin: your first quest, repeating dailies, rewards and quest chains that unlock one after another.

Original page: https://napnodes.com/en/guides/minecraft-server-quests · Updated: 2026-11-07

Mine 64 stone, kill 20 zombies, catch 10 fish: quests with a reward that players open with /quests and that give them a reason to come back every day. They're done with a plugin, and players don't install anything. Here's how to set them up with Quests, free and open source, from the first one to dailies and chains that unlock one after another.

## What you need

A Paper server (or Spigot, Purpur): quests are a plugin. On NapNodes, Minecraft servers come on Paper, on the latest version. Players join with normal Minecraft Java and see the quests in a menu.

Quests (by LMBishop) is free and open source. Each quest is a text file with what has to be done (break blocks, kill mobs, fish, play for a while, talk to an NPC…), how it looks in the menu and the reward. It has no in-game editor: you write it in the file and reload.

If you want quests with a story, NPC dialogue and choices, look at BetonQuest: it's much more powerful and also quite a bit harder to configure. For “do this and I'll give you that” quests, Quests is the simplest.

## Installing Quests

1. **Make a backup**: In the panel, “Backups”. If you're on the free server, which has no backups, first compress the world folder in “Files” and download it.
2. **Find it in “Mods & plugins”**: Search for Quests and install the one by LMBishop (there are other plugins with similar names). If it doesn't show up for your version, download it from its website, quests.leonardobishop.com, and upload the .jar to the plugins folder from “Files”.
3. **Restart**: With “Restart”. On startup you get plugins/Quests with config.yml (the general settings), categories.yml (the menu groups) and the quests folder, where each quest has its own file. It comes with example quests and categories, with comments: read them and then delete them.
4. **Try it**: Join and type `/quests` (or `/q`): the menu opens with the categories. If it's empty, look at the “Console” on startup: file errors show up there, and in game `/quests admin config` tells you which file has problems.

## Your first quest

First, the category it will appear in. A quest without a category doesn't show in the menu (as long as categories are enabled, which is the default). Open plugins/Quests/categories.yml in “Files”, delete the examples and leave yours: the category's name (basic) is the one you'll use in your quests.

Then the quest: in the plugins/Quests/quests folder, create a file called miner.yml. The file name (without .yml) is the quest's ID: only letters and numbers, no spaces or accents. Inside go the task (break 64 stone), how it looks in the menu and the reward, which is a command that runs as if you typed it in the console, with {player} in place of whoever finishes it.

Colours use & and a code (&a green, &6 gold, &7 grey, &f white), as on signs. {mine:progress} is replaced by the player's progress on the mine task. Save and type `/quests admin reload` in game (in “Console”, without the slash): no restart needed.

File: `plugins/Quests/categories.yml`

```yaml
categories:
  basic:
    display:
      name: "&aBasic quests"
      lore:
        - "&7To get started on the server"
      type: "GRASS_BLOCK"
```

File: `plugins/Quests/quests/miner.yml`

```yaml
tasks:
  mine:
    type: "blockbreak"
    amount: 64
    block: "STONE"
display:
  name: "&6Novice miner"
  lore-normal:
    - "&7Break &f64 stone&7."
    - "&7Reward: &f16 iron ingots&7."
  lore-started:
    - "&7Progress: &f{mine:progress}&7/64."
  type: "STONE_PICKAXE"
rewards:
  - "give {player} iron_ingot 16"
rewardstring:
  - "&aQuest complete: 16 iron ingots."
options:
  category: "basic"
  repeatable: false
  sort-order: 1
```

## The most used tasks

Each task has a type and its options. A quest can have several tasks (mine and also fish) and it's complete when they're all done. The most useful ones, with their exact names:

blockbreak (break blocks; with block, only one kind), blockplace (place), mobkilling (kill mobs; with mob, only one kind, like ZOMBIE), fishing, farming (harvest), crafting, consume (eat or drink), walking (cover a distance), playtime (play for some minutes, with minutes instead of amount), inventory (have certain items, for “bring me…” quests) and citizens_interact (talk to a Citizens NPC, with npc-name).

Block, item and mob names are in uppercase, as in the game's internals: STONE, OAK_LOG, ZOMBIE, COD. The full list of tasks, with their options, is in the plugin's documentation; `/quests admin types` shows the ones you have active, because some only turn on if the plugin they need is there (Citizens, for example).

A well-known trick: if the quest is to break blocks, someone can place and remove the same block a thousand times. To stop that counting, set reverse-if-placed: true on the task (placing subtracts) or, if you have CoreProtect, check-coreprotect: true (what a player placed recently doesn't count).

## Daily quests

A daily is a quest that can be repeated with a wait in between. In options you set repeatable: true and a cooldown of 1440 minutes, which is a day. After completing it, the player has to wait 24 hours from that moment to do it again (it doesn't reset at midnight for everyone).

To keep dailies together, put them in their own category (daily) in categories.yml. And if you want a quest to expire when it isn't finished in time, time-limit works just like cooldown: enabled and the minutes.

Watch out for the limit: by default, each player can have at most 2 quests started at once (quest-limit in config.yml). If you have many dailies, raise it, or put counts-towards-limit: false in the dailies' options so they don't count.

File: `plugins/Quests/quests/dailyfishing.yml`

```yaml
tasks:
  fish:
    type: "fishing"
    amount: 10
display:
  name: "&bCatch of the day"
  lore-normal:
    - "&7Fish &f10 &7times. Repeats every 24 hours."
  lore-started:
    - "&7Progress: &f{fish:progress}&7/10."
  type: "FISHING_ROD"
rewards:
  - "give {player} cooked_cod 16"
  - "give {player} experience_bottle 8"
options:
  category: "daily"
  repeatable: true
  cooldown:
    enabled: true
    time: 1440
  counts-towards-limit: false
```

## Rewards and quest chains

Rewards are commands, so they can be almost anything: items with give, experience with `xp add {player} 100 levels`, a rank with LuckPerms (`lp user {player} parent add miner`), a crate key, or an announcement to everyone with tellraw. If you use an economy plugin with Vault, vaultreward: 500 gives 500 coins with no command.

To unlock some quests by finishing others, put requires in the second one's options with the first one's ID (its file name). That's how you build a path: miner, then expert miner, then the Nether one.

If you want a quest to be available only to some people (those of a rank, for example), permission-required: true in its options asks for the quests.quest.<ID> permission, which you give with LuckPerms.

As on any server with an economy, be careful not to give away too much: if dailies hand out diamonds by the fistful, within a week nobody values them. Better small, frequent rewards, and something special at the end of a chain.

## If something doesn't work

If a quest doesn't show in the menu, it almost always has no category, the category doesn't exist in categories.yml or the file has a format error (YAML is strict about spaces: always use two spaces per level, never tabs). `/quests admin config` shows the problems it found while loading.

If a task doesn't progress, check the name of the block or mob (uppercase) and whether the task is limited to a world with worlds. To see a player's progress: `/quests admin debug player Name`. To start or complete a quest for someone by hand (if something went wrong), /quests admin moddata start or complete with their name and the ID; those changes can't be undone.

Quests are stored in plugins/Quests/quests, each in its own file. To take them to another server, download that folder and categories.yml from “Files” and upload them to the new one.

## How it's done on NapNodes

Quests installs from “Mods & plugins” (or upload the .jar in “Files” if it isn't there), quest files are written in “Files” without any other program and `/quests admin reload` runs from “Console”. The RAM on your plan is yours alone, with no overselling.

To try it, you can start with the free server and move to a plan when you have regular players: with a plan it stays on even with nobody there, which is exactly what someone coming back each day for their daily wants.

## Questions

### How do I add quests to my Minecraft server?

With a plugin on a Paper server. Quests is free: each quest is a file in plugins/Quests/quests with the task, how it looks in the menu and the reward, and players open them with /quests.

### How do I make daily quests in Minecraft?

With Quests, in the quest's options: repeatable: true and a cooldown of 1440 minutes. After completing it, the player can repeat it 24 hours later.

### Why doesn't my quest show in the /quests menu?

It's almost always missing the category, that category isn't in categories.yml or the file has a spacing error. /quests admin config says what failed on load.

### Do players have to install anything for quests?

No. Quests is a server plugin: anyone who joins with Minecraft Java sees the menu and does quests without installing anything.

### Which quest plugin has NPC dialogue?

BetonQuest, with conversations and story quests; it's harder to configure. Quests can also ask you to talk to a Citizens NPC, but without dialogue.

---

NapNodes gives you a free Minecraft server, no card and no end date: it isn't always on (it switches itself off after an hour with nobody on, and you start it again with one click). How it works: https://napnodes.com/en/free. Paid plans, always on and with no commitment: https://napnodes.com/en/pricing.
