aboutsummaryrefslogtreecommitdiffstats
path: root/src/main/resources/quests/example1.yml
diff options
context:
space:
mode:
Diffstat (limited to 'src/main/resources/quests/example1.yml')
-rw-r--r--src/main/resources/quests/example1.yml13
1 files changed, 10 insertions, 3 deletions
diff --git a/src/main/resources/quests/example1.yml b/src/main/resources/quests/example1.yml
index d0d44203..ca57f714 100644
--- a/src/main/resources/quests/example1.yml
+++ b/src/main/resources/quests/example1.yml
@@ -21,16 +21,16 @@ display:
- "&cattributes a quest can have."
- ""
- "&7This quest requires you to:"
- - "&7 - Break 30 blocks."
+ - "&7 - Break &f30 blocks&7."
- ""
- "&7Rewards:"
- - "&7 - 10 diamonds."
+ - "&7 - &f10 &7diamonds."
# This lore will be appended to the bottom of the above lore when the player starts their quest.
# To get the players progress through a task, use {TASKID:progress} and replace TASKID with the ID of the task.
lore-started:
- ""
- "&7Your current progression:"
- - "&7 - {mining:progress}/30 blocks broken."
+ - "&7 - &f{mining:progress}&7/30 blocks broken."
# This is the material of the item. It is recommended to stick to bukkit names.
type: "WOODEN_PICKAXE"
@@ -38,6 +38,13 @@ display:
rewards:
- "give {player} diamond 10"
+# These placeholders are accessible using PlaceholderAPI, for example %quests_tracked_p:description%
+# They are useful for putting information about the players tracked quest on a scoreboard
+# You may want to keep the names of them the same for ALL quests for this use-case
+placeholders:
+ description: "&7Break &f30 blocks &7of any type."
+ progress: " &8- &f{mining:progress}&7/30 broken"
+
# Everything inside this section define quest-specific options
options:
# This is the category for the quest, it will appear under the "examples" category. Categories can be disabled.