ScrollQuest - Paper Quests 1.6.0

🌐 Cross-Server Storage

Quests, progress, completions, claims and stats can now live in a shared database, so they follow players between the servers of a BungeeCord or Velocity network.

• Storage: MySQL, MariaDB or MongoDB (4.2+), set in the new storage.yml
• Instant sync, optional: add Redis or RabbitMQ and changes show up on other servers straight away instead of on the next sync
• No duplicate rewards. Only one server can ever win a claim, even if a player switches servers mid claim or two admins force-claim at once
• Progress adds up. Progress earned on two servers at the same moment is combined, never overwritten
• Claim history is kept for 30 days by default
• Fails safe. If the database can't be reached at startup, the plugin stops rather than splitting your data

Single server? Nothing changes. type: YAML stays the default and works exactly like 1.5.4.

New /quest storage command for admins shows the backend, server name, cached quests, unsaved progress and messaging status.

Find out more about setting up network storage here → greenarrowlol.github.io/ScrollQuest

📦 Moving From YAML to a Database

Set type to your database, set migration.migrate-yaml- true and restart. Your quest and stats files are imported and renamed to .migrated. On a network, each server migrates its own files and stats are added together.

This can't be undone. Once migrated, the server stays locked to that database. Take a backup first.

Switch to a database without turning on the migration and the plugin stays on YAML and tells you what to do, so nobody's quests get stranded.

🔧 Recover Dupe Fixed

/quest recover could hand out a second working scroll when the original was out of reach, like on another server, in another Multiverse-Inventories group or in PlayerVaults. Now recovering a scroll makes every older copy stop working. This applies on single servers too, and existing scrolls keep working.

🗺️ Multiverse-Core

worlds.blacklist now takes server:world entries, so one shared config.yml works when several servers have a world with the same name. Plain entries still apply everywhere.

📦 Upgrading

Drop in the jar and restart. storage.yml is created for you and the new messages are added to messages.yml on their own.

The jar is still small. MongoDB and RabbitMQ support downloads once, only on servers that pick them. YAML, MySQL, MariaDB and Redis download nothing.