From 71f118f233bdd24b4fdadfa6f2f38ff2e6d6b246 Mon Sep 17 00:00:00 2001
From: LMBishop <13875753+LMBishop@users.noreply.github.com>
Date: Thu, 11 Jul 2019 22:46:01 +0100
Subject: Config split up

- Quests will now be in their own files
- New 'QuestsConfigLoader' class to handle this with error messages
- General refactorings
---
 src/main/resources/quests/example1.yml | 55 ++++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 src/main/resources/quests/example1.yml

(limited to 'src/main/resources/quests/example1.yml')

diff --git a/src/main/resources/quests/example1.yml b/src/main/resources/quests/example1.yml
new file mode 100644
index 00000000..7e38f01f
--- /dev/null
+++ b/src/main/resources/quests/example1.yml
@@ -0,0 +1,55 @@
+# The name of this file is the quest ID. It must be alphanumeric and unique.
+
+# Everything inside of this section defines tasks the player must complete to progress.
+tasks:
+  # This is the task ID ("mining"). This can share the same name as the quest ID but MUST be unique with all other task IDs in the same quest.
+  mining:
+    # This defines what type of task this is. In this instance, it is "blockbreak" (breaking blocks)
+    # NOTE: guides to set up each type of task is on the plugin page!
+    type: "blockbreak"
+    # This defines the amount of blocks which need to be broken
+    amount: 30
+  # You can have multiple tasks for each quest (example further down).
+
+# Everything inside of this section defines the display item.
+display:
+  # This is the name of the item. This allows color codes.
+  name: "&cExample I (Single Task)"
+  # This is the lore of the item if the player has not started the quest. This allows color codes and task/player placeholders.
+  lore-normal:
+    - "&cThis category is designed to show you the different"
+    - "&cattributes a quest can have."
+    - ""
+    - "&7This quest requires you to:"
+    - "&7 - Break 30 blocks."
+    - ""
+    - "&7Rewards:"
+    - "&7 - 10 diamonds."
+  # 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."
+  # This is the material of the item. It is recommended to stick to bukkit names.
+  type: "WOOD_PICKAXE"
+
+# List all commands to be executed by the server when the player completes the quest. Use {player} to get the players name.
+rewards:
+  - "give {player} diamond 10"
+
+# 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.
+  category: "examples"
+  # Set the quest IDs of required quests here, leave empty if none.
+  requires:
+    - ""
+  # Set if the quest can be repeated after being completed for the first time.
+  repeatable: false
+  # Define the cooldown on quests. The above (repeatable) must be true for this to take effect.
+  cooldown:
+    # If true, players will have to wait between repeating quests.
+    enabled: true
+    # Time (in minutes)
+    time: 1440
\ No newline at end of file
-- 
cgit v1.2.3-70-g09d2