DUXPLIMA Documentation

Quests and tasks

A quest, its tasks, amounts and spans, filters and draws, and how names are found.

{
  id          = mine-stone
  name        = "@quest.mine-stone.name"
  description = "@quest.mine-stone.description"
  rarity      = common
  tasks = [
    { id = dig, type = block-break, block = ["STONE", "DEEPSLATE"], amount = "64-128", reverse = true }
  ]
  rewards = [ "[message] @quest.mine-stone.reward", "[console] give {player} bread 4" ]
}
KeyMeaning
idThe quest's id, typed in commands
name, description@key or plain words; without them the id
rarityWhich bucket it is drawn from
rulerequired and order, overriding the group's
tasksA list; each needs id, type and amount, and may carry description and feedback
rewardsAction lines
category, requires, cooldownCatalogue quests only
feedbackThis quest's own feedback

Amounts

A number, a span such as "10-25", or a block with least and most. A span is drawn once when the quest is handed out and stored with it, so a reload never changes the number under a player halfway through.

Options

Every other key of a task is an option its type understands. Three shapes, three meanings:

WrittenMeans
block = STONEOne block
block = [STONE, GOLD_ORE] or block { any-of = [...] }A filter: any of them counts, and the quest is one count
block { one-of = [STONE, GOLD_ORE] }A draw: one is chosen per player when the quest is handed out and stored with it

Values are upper-cased, except placeholder, permission and value, which are read as written. reverse = true takes a count back when an event undoes what the task counted, such as a block put back after it was broken.

Names

A quest or task without a name or description is called by its id, or by the sentence its type carries under task.<type> in messages/. Block, item and mob names are translated through the vanilla table of messages/; a name the table lacks is spelled out from the server's own, so DEEPSLATE_DIAMOND_ORE reads "Deepslate Diamond Ore".

Related: Task types, Group files