RaindropCentral — Server monitoring for Minecraft operators

RDQ Quest SystemBuild connected progression paths with 100 ready-to-run quests, automatic gameplay objectives, persistent progress, configurable rewards, and per-player tracking.

Available in both editions

RDQ Free and RDQ Premium use the same quest runtime and bundled definitions. Quest content loads from plugins/RDQ/quests/definitions/.

Bundled ContentRDQ installs 100 active quest definitions containing 114 tasks across 11 categories. Fourteen daily and weekly quests are repeatable. The bundled progression graph uses prerequisites to connect tutorials, professions, weekly goals, and master capstones.

Builder10 quests

Collector10 quests

Combat12 quests

Crafter10 quests

Daily8 quests

Farmer10 quests

Lumberjack8 quests

Master8 quests

Miner12 quests

Tutorial6 quests

Weekly6 quests

Player Flow

Open /quest or /q to see the quest dashboard, active quests, completed quests, and the category browser.

Open a quest to review its difficulty, objectives, requirements, prerequisite chain, and rewards.

Accept the quest from its detail view or with /quest accept <quest>. RDQ creates fresh task-progress rows.

Play normally. Matching server events update every active quest and cap each task at its configured target.

When every task is complete, RDQ completes the quest automatically, persists the result, and grants its quest-level reward.

Track one active quest to publish its progress through the shared display system, or inspect progress in chat at any time.

Objective TypesThe built-in progression listener handles six objective types from ordinary gameplay events.

block-breakAdds one for each matching block the player breaks. Use a Bukkit material name or any/*.

block-placeAdds one for each matching block the player places. Use a Bukkit material name or any/*.

entity-killAdds one when the player is the killer of a matching Bukkit entity type.

item-craftCounts the number of result items produced, including the full result of a shift-click craft.

item-pickupCounts the picked-up stack amount. Player-thrown items are ignored to prevent drop-and-pickup farming.

player-joinAdds one for each player join event; the built-in listener does not deduplicate logins by calendar day.

Quest YAMLStore each definition beneath a category directory. Identifiers must remain unique; category defaults to the containing directory when omitted. RDQ upserts definitions into its database whenever content loads.

identifier: miner_first_diamonds
category: miner
displayName: "<gradient:#67e8f9:#2563eb>First Diamonds</gradient>"
difficulty: MEDIUM
repeatable: false
enabled: true
prerequisites: [tutorial_first_block]
icon: { material: DIAMOND_PICKAXE }
reward:
  type: composite
  children:
    - { type: xp, amount: 250 }
    - { type: currency, currency: coins, amount: 500 }
    - { type: item, materialKey: DIAMOND, amount: 2, nbt: "{}" }
tasks:
  - identifier: mine_diamonds
    displayName: "<gray>Mine <white>8</white> diamond ore</gray>"
    orderIndex: 0
    objective: { type: block-break, material: DIAMOND_ORE, target: 8 }
  - identifier: craft_pickaxe
    displayName: "<gray>Craft a <white>diamond pickaxe</white></gray>"
    orderIndex: 1
    objective: { type: item-craft, material: DIAMOND_PICKAXE, target: 1 }

This example is intentionally non-repeatable. Set repeatable: true when a completed quest should be accepted again.

Requirements & RewardsA prerequisites list becomes one or more quest-completed requirements at load time. An explicit quest-level requirement can be combined with those prerequisites. Acceptance is blocked until the complete requirement evaluates successfully.When all tasks finish, RDQ completes the quest automatically and grants its quest-level reward. Composite and choice flows use the shared selection system when player input is needed.

Requirement referenceReward reference

Tracking & CommandsEach player can select one tracked quest. The shared display provider renders that quest and its task progress, while the same progress remains available through chat commands.

/quest or /q

Open the quest dashboard.

/quest list [category]

Open the quest browser, optionally focused on one category.

/quest info <quest>

Show quest details and live task progress.

/quest accept <quest>

Accept an available quest.

/quest abandon <quest>

Abandon an active quest.

/quest track [quest]

Track a quest, or clear tracking when no quest is supplied.

/quest progress [quest]

Show the tracked or specified quest progress.

/quest sidebar [on|off]

Toggle or explicitly control sidebar visibility.

/quest board [on|off|hide]

Use the alternate quest-sidebar command.

/rq quest [arguments…]

Forward the singular quest area through the compatibility facade.

See the complete RDQ command reference and permission reference for every route and gate.

Operations & Current Limits

Use /rdq reload after editing quest YAML. One invalid file is logged and skipped without preventing other definitions from loading.

Files anywhere below quests/definitions/legacy/ remain available as examples but are deliberately skipped by the loader.

The built-in listener does not advance custom objective types. An external integration must own and dispatch that progress.

cooldownSeconds, maxCompletions, and timeLimitSeconds are stored in the current model, but the quest service does not yet enforce their cooldown, cap, or expiry policies.

Only quest-level rewards are granted by automatic completion. Do not rely on task-level reward blocks for payouts.

Return to the RDQ setup guide for installation, database configuration, and integration guidance.

ON THIS PAGE

Bundled Content Player Flow Objective Types Quest YAML Requirements & Rewards Tracking & Commands Operations & Limits

identifier: miner_first_diamonds category: miner displayName: "<gradient:#67e8f9:#2563eb>First Diamonds</gradient>" difficulty: MEDIUM repeatable: false enabled: true prerequisites: [tutorial_first_block] icon: { material: DIAMOND_PICKAXE } reward: type: composite children: - { type: xp, amount: 250 } - { type: currency, currency: coins, amount: 500 } - { type: item, materialKey: DIAMOND, amount: 2, nbt: "{}" } tasks: - identifier: mine_diamonds displayName: "<gray>Mine <white>8</white> diamond ore</gray>" orderIndex: 0 objective: { type: block-break, material: DIAMOND_ORE, target: 8 } - identifier: craft_pickaxe displayName: "<gray>Craft a <white>diamond pickaxe</white></gray>" orderIndex: 1 objective: { type: item-craft, material: DIAMOND_PICKAXE, target: 1 }