Storage & Data

Player quest data is saved through one storage layer, so the plugin does not care which database is behind it. Pick one with storage.type in config.yml.

Caution

Switching storage type needs a full server restart, not just /dq reload.

SQLite (default)

Works out of the box, nothing to set up. Data lives in a single data.db file inside the plugin folder.

storage:
  type: sqlite

Good for a single server. To start fresh, stop the server and delete data.db.

MySQL

Point the plugin at a MySQL server to share data across servers or keep it in your own database.

storage:
  type: mysql
  mysql:
    host: localhost
    port: 3306
    database: zdailyquests
    username: root
    password: "your-password"
    use-ssl: false
    pool-size: 6

Create the database in your panel first. Keep use-ssl off unless your server really uses SSL.

Note

If the details are wrong (a bad password, say), the plugin disables itself with a clear log line rather than spamming errors, and the rest of your server keeps running.

What is stored

For each player the plugin keeps:

• Their current five quest ids
• Progress and completion count on each
• The phase each quest is in
• Whether each quest is locked as done
• When the current set was assigned (for the timer)
• Whether the all-five bonus has been claimed for this set

Performance

All database work runs off the main thread. Loads happen when a player joins, saves happen in the background off a snapshot so live play is never blocked. You should see no lag spike from joining, quitting, or progressing quests. On a clean shutdown the plugin saves everyone before it stops.