Installation
Getting zDailyQuests running takes a couple of minutes. The only thing you must have first is TheAPI.
Requirements
Section titled “Requirements”| Need | Detail |
|---|---|
| Server | Spigot or Paper, Minecraft 1.21 and newer |
| Java | 21 |
| TheAPI required | Runs the quest menu. Without it zDailyQuests will not enable, on purpose. |
| PlaceholderAPI optional | Only needed if you use placeholder quests. |
| Internet on first boot | The storage drivers download themselves once, see below. |
Install steps
Section titled “Install steps”-
Add TheAPI
Section titled “Add TheAPI”Download TheAPI and put it in your
plugins/folder if it is not there already. -
Add zDailyQuests
Section titled “Add zDailyQuests”Drop the zDailyQuests jar into
plugins/next to it. -
Start the server once
Section titled “Start the server once”On first boot the plugin pulls its storage drivers (HikariCP and the SQLite driver) through the built-in Bukkit library loader. This needs internet that one time. It then writes out
config.yml,lang.yml, and aquests/folder with six starter quests. -
Have a look, then tune
Section titled “Have a look, then tune”Open config.yml to set the reset window, claim mode, and bonus. Run
/dq reloadto apply changes without a restart. Only the storage section needs a full restart.
First run
Section titled “First run”Once it is up, any player can type /dq (or /dailyquests) to open their board. The first open hands them a random set of five and starts their timer. Try it yourself to confirm the menu draws and the quests show live progress.
Plugin folder layout
Section titled “Plugin folder layout”After the first boot your folder looks like this:
Directoryplugins/
DirectoryzDailyQuests/
- config.yml main settings
- lang.yml all player-facing text
- data.db SQLite storage (default)
Directoryquests/
- break_stone_64.yml
- catch_fish_10.yml
- craft_bread_16.yml
- deal_damage_200.yml
- kill_zombies_25.yml
- place_planks_32.yml
In RARITY mode the quest files sit in easy/, normal/, and hard/ subfolders inside quests/ instead. See Selection Modes.
Updating
Section titled “Updating”Drop the new jar in over the old one and restart. Your config.yml and lang.yml are kept, the plugin pours any new keys that build added into them and leaves your values and comments untouched. Nothing to copy across by hand. See auto-migration for how it works.