Convert to multi module project

- Common module to provide an abstract Quests plugin
- Api is still todo

8 files changed, 0 insertions, 357 deletions

diff --git a/src/main/resources/quests/README.txt b/src/main/resources/quests/README.txt
deleted file mode 100644
index 779dd6bb..00000000
--- a/src/main/resources/quests/README.txt
+++ /dev/null
@@ -1,40 +0,0 @@
-# !! READ ME - IT WILL NOT TAKE LONG !!
-#
-# Each file ín the 'quests' folder defines a single quest.
-# The name of the file is the quest ID. These must be alphanumeric and unique.
-# Quest files must be in the .yml format.
-#
-# A quest is a series of tasks which players must complete for a reward and may require a previous quest to start.
-# A task is an objective such as breaking blocks or obtaining items.
-# A reward is a command executed by the SERVER. Use {player} to get the players name.
-#
-# Most task types will allow you to restrict them to a certain world. Check out the wiki for which ones.
-#
-# A quest can have a 'startstring' (this is optional). They will be sent to the player when they start the quest.
-# A quest can have a 'rewardstring' (this is optional). They will be sent to the player when they complete the quest.
-# An example of the startstring/rewardstring in use can be seen in the quest example4.
-#
-# Each quest will have ONE "display" item, this is the item shown to the player in the GUI.
-# The display item will have a "name", a "type" and TWO lores.
-# The name is the name of the item, the type is the material and the lore is the text underneath the item (when mouse-over-ing).
-# The first lore you must give is called 'lore-normal'. This is the lore seen if the player has not started the quest.
-# The second lore you must give is 'lore-started'. This will be APPENDED to the first lore IF the player has started the quest - useful for putting progression.
-# Within the lores you can get the players progress for each task. Use {TASKID:progress} (replace TASKID with the ID of the task).
-# You can also get if a task is complete. Use {TASKID:complete} (replace TASKID with the ID of the task).
-#
-# Quests can be put inside a category. When a player runs /quests they will first see a menu of categories.
-# They can click one and another menu of quests under that category will show up.
-#
-# ===============================================================
-#
-# You can see other task types here:
-# https://github.com/LMBishop/Quests/wiki/Task-Types
-#
-# ===============================================================
-#
-# Need help?
-# Find the Discord link in the README.md, or open an issue on GitHub
-# https://github.com/LMBishop/Quests/issues
-# https://github.com/LMBishop/Quests/blob/master/README.md
-#
-# ===============================================================
diff --git a/src/main/resources/quests/example1.yml b/src/main/resources/quests/example1.yml
deleted file mode 100644
index ca57f714..00000000
--- a/src/main/resources/quests/example1.yml
+++ /dev/null
@@ -1,61 +0,0 @@
-# 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 wiki (see README)!
-    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 &f30 blocks&7."
-    - ""
-    - "&7Rewards:"
-    - "&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 - &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"
-
-# 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"
-
-# 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.
-  category: "examples"
-  # 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
-  # This is the relative position in the GUI
-  sort-order: 1
\ No newline at end of file
diff --git a/src/main/resources/quests/example2.yml b/src/main/resources/quests/example2.yml
deleted file mode 100644
index 7ad82bea..00000000
--- a/src/main/resources/quests/example2.yml
+++ /dev/null
@@ -1,47 +0,0 @@
-# This is a quest which requires the previous quest to be complete to start.
-
-tasks:
-  # Unlike the previous quest, this quest has multiple tasks.
-  mining:
-    type: "blockbreak"
-    amount: 100
-  building:
-    type: "blockplace"
-    amount: 100
-display:
-  name: "&cExample II (Multiple Tasks)"
-  lore-normal:
-    - "&cThis category is designed to show you the different"
-    - "&cattributes a quest can have. This quest requires"
-    - "&cmultiple things to be done, unlike the previous one."
-    - ""
-    - "&7This quest requires you to:"
-    - "&7 - Break &f100 &7blocks."
-    - "&7 - Place &f100 &7blocks."
-    - ""
-    - "&7Rewards:"
-    - "&7 - &f15 diamonds&7."
-    - "&7 - &f$50&7 added to your in-game balance."
-  lore-started:
-    - ""
-    - "&7Your current progression:"
-    - "&7 - &f{mining:progress}&7/100 blocks broken."
-    - "&7 - &f{building:progress}&7/100 blocks placed."
-  type: "GRASS_BLOCK"
-rewards:
-  - "give {player} diamond 15"
-  - "eco give {player} 50"
-placeholders:
-  description: "&7Break and place &f100 blocks &7of any type."
-  progress: " &8- &f{mining:progress}&7/100 broken, &f{building:progress}&7/100 placed"
-options:
-  category: "examples"
-  # Unlike the previous quest, this quest has "example1" as a required quest. You cannot start this quest without "example1" quest complete.
-  requires:
-    - "example1"
-  repeatable: false
-  cooldown:
-    enabled: true
-    time: 1440
-  # The sort order has been changed so this quest will appear after in the GUI
-  sort-order: 2
\ No newline at end of file
diff --git a/src/main/resources/quests/example3.yml b/src/main/resources/quests/example3.yml
deleted file mode 100644
index dbd893e4..00000000
--- a/src/main/resources/quests/example3.yml
+++ /dev/null
@@ -1,49 +0,0 @@
-# This is a quest which requires the previous quest to be complete to start.
-# Unlike the previous quest, this one can be re-done but it has a 10 minute cooldown.
-
-tasks:
-  # Unlike the previous two quests, this quest specifies a specific block to be broken.
-  mining:
-    type: "blockbreakcertain"
-    amount: 81
-    block: GOLD_ORE
-  building:
-    type: "blockplacecertain"
-    amount: 9
-    block: GOLD_BLOCK
-display:
-  name: "&cExample III (Repeatable, 10 minute cooldown)"
-  lore-normal:
-    - "&cThis category is designed to show you the different"
-    - "&cattributes a quest can have. This quest can be replayed"
-    - "&cafter a cooldown, unlike the previous one."
-    - ""
-    - "&7This quest requires you to:"
-    - "&7 - Break &f81 gold ore&7."
-    - "&7 - Place &f9 gold blocks&7."
-    - ""
-    - "&7Rewards:"
-    - "&7 - &f30 diamonds&7."
-    - "&7 - &f$10&7 added to your in-game balance."
-  lore-started:
-    - ""
-    - "&7Your current progression:"
-    - "&7 - &f{mining:progress}&7/81 gold ore broken."
-    - "&7 - &f{building:progress}&7/9 gold blocks placed."
-  type: "GOLD_ORE"
-rewards:
-  - "give {player} diamond 30"
-  - "eco give {player} 10"
-placeholders:
-  description: "&7Break &f81 gold ore &7and place &f9 gold blocks."
-  progress: " &8- &f{mining:progress}&7/81 gold ore, &f{building:progress}&7/9 gold blocks"
-options:
-  category: "examples"
-  requires:
-    - "example2"
-  # This quest is repeatable, it has cooldowns enabled (meaning the player must wait before repeating it) and the time set to 10 (minutes).
-  repeatable: true
-  cooldown:
-    enabled: true
-    time: 10
-  sort-order: 3
\ No newline at end of file
diff --git a/src/main/resources/quests/example4.yml b/src/main/resources/quests/example4.yml
deleted file mode 100644
index 4e9c27a8..00000000
--- a/src/main/resources/quests/example4.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# This is a quest which requires the previous quest to be complete to start.
-# Unlike the previous quests, this quest has a reward string and a start string.
-
-tasks:
-  mobkilling:
-    type: "mobkilling"
-    amount: 3
-display:
-  name: "&cExample IV (Reward String)"
-  lore-normal:
-    - "&cThis category is designed to show you the different"
-    - "&cattributes a quest can have. This quest has a 'reward string'"
-    - "&c(a series of messages sent when a quest is complete),"
-    - "&cunlike the previous one."
-    - ""
-    - "&7This quest requires you to:"
-    - "&7 - Kill &f3 &7mobs."
-    - ""
-    - "&7Rewards:"
-    - "&7 - &f$50 &7added to your in-game balance."
-    - "&7 - &f1 diamond&7."
-  lore-started:
-    - ""
-    - "&7Your current progression:"
-    - "&7 - &f{mobkilling:progress}&7/3 mobs killed."
-  type: "STRING"
-# Here you can list messages which will be sent to the player (if they are online) upon the quest starting.
-startstring:
-  - "&7Upon completion of this quest, you will be rewarded with"
-  - " &8* &c$50"
-  - " &8* &c1 diamonds"
-rewards:
-  - "eco give {player} 50"
-  - "give {player} diamond 1"
-placeholders:
-  description: "&7Kill &f3 &7mobs."
-  progress: " &8- &f{mobkilling:progress}&7/3 mobs"
-# Here you can list messages which will be sent to the player (if they are online) upon completion.
-rewardstring:
-  - " &8* &c$1000 &7was added to your in-game balance."
-  - " &8* &c1 diamond &7was added to your inventory."
-options:
-  category: "examples"
-  requires:
-    - "example3"
-  repeatable: true
-  cooldown:
-    enabled: true
-    time: 10
-  sort-order: 4
\ No newline at end of file
diff --git a/src/main/resources/quests/example5.yml b/src/main/resources/quests/example5.yml
deleted file mode 100644
index cb92f0f1..00000000
--- a/src/main/resources/quests/example5.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-tasks:
-  building:
-    type: "blockplace"
-    amount: 10
-display:
-  name: "&cExample V (Permission)"
-  lore-normal:
-    - "&cThis category is designed to show you the different"
-    - "&cattributes a quest can have. This quest requires"
-    - "&ccertain permissions."
-    - ""
-    - "&7This quest requires you to:"
-    - "&7 - Place &f10 &7blocks."
-    - ""
-    - "&7Rewards:"
-    - "&7 - &f$10 &7added to your in-game balance."
-  lore-started:
-    - ""
-    - "&7Your current progression:"
-    - "&7 - &f{building:progress}&7/10 blocks placed."
-  type: "GRASS_BLOCK"
-rewards:
-  - "eco give {player} 10"
-placeholders:
-  description: "&7Place &f10 &7blocks of any type."
-  progress: " &8- &f{building:progress}&7/10 blocks"
-options:
-  category: "examples"
-  requires:
-    - "example4"
-  # Unlike the previous quests, this one requires you to have the permission "quests.quest.example5" to start.
-  # The permission for other quests is: "quests.quest.<id>".
-  permission-required: true
-  repeatable: false
-  cooldown:
-    enabled: true
-    time: 1440
-  sort-order: 5
\ No newline at end of file
diff --git a/src/main/resources/quests/example6.yml b/src/main/resources/quests/example6.yml
deleted file mode 100644
index 0913a7cb..00000000
--- a/src/main/resources/quests/example6.yml
+++ /dev/null
@@ -1,35 +0,0 @@
-tasks:
-  building:
-    type: "blockplace"
-    amount: 10
-display:
-  name: "&cExample VI (Different category, permissions)"
-  lore-normal:
-    - "&cThis category is designed to show you the different"
-    - "&cattributes a quest can have. This quest requires"
-    - "&ccertain permissions."
-    - ""
-    - "&7This quest requires you to:"
-    - "&7 - Place &f10 &7blocks."
-    - ""
-    - "&7Rewards:"
-    - "&7 - &f$10 &7added to your in-game balance."
-  lore-started:
-    - ""
-    - "&7Your current progression:"
-    - "&7 - &f{building:progress}&7/10 blocks placed."
-  type: "GRASS_BLOCK"
-rewards:
-  - "eco give {player} 10"
-placeholders:
-  description: "&7Place &f10 &7blocks of any type."
-  progress: " &8- &f{building:progress}&7/10 blocks"
-options:
-  category: "permissionexample"
-  # This quest has no specific permission, however its category does. The permission for the category is "quests.category.permissionexample"
-  repeatable: false
-  cooldown:
-    enabled: true
-    time: 1440
-  # The quest is in a different category so the sort order is 1.
-  sort-order: 1
\ No newline at end of file
diff --git a/src/main/resources/quests/example7.yml b/src/main/resources/quests/example7.yml
deleted file mode 100644
index 32bb7e04..00000000
--- a/src/main/resources/quests/example7.yml
+++ /dev/null
@@ -1,37 +0,0 @@
-tasks:
-  building:
-    type: "blockplace"
-    amount: 10
-    worlds:
-      - "world"
-display:
-  name: "&cExample VII (Different category, world restricted)"
-  lore-normal:
-    - "&cThis category is designed to show you the different"
-    - "&cattributes a quest can have. This quest requires"
-    - "&chas a task which requires you to be in a world called 'world'."
-    - ""
-    - "&7This quest requires you to:"
-    - "&7 - Place &f10 &7blocks."
-    - ""
-    - "&7Rewards:"
-    - "&7 - &f$10 &7added to your in-game balance."
-  lore-started:
-    - ""
-    - "&7Your current progression:"
-    - "&7 - &f{building:progress}&7/10 blocks placed."
-  type: "GRASS_BLOCK"
-rewards:
-  - "eco give {player} 10"
-placeholders:
-  description: "&7Place &f10 &7blocks of any type in world &fworld."
-  progress: " &8- &f{building:progress}&7/10 blocks"
-options:
-  category: "permissionexample"
-  # This quest has no specific permission, however its category does. The permission for the category is "quests.category.permissionexample"
-  repeatable: false
-  cooldown:
-    enabled: true
-    time: 1440
-  # The quest is in a different category so the sort order is 1.
-  sort-order: 1
\ No newline at end of file