Wrote new examples and updated config and pom.xml

1 files changed, 13 insertions, 4 deletions

diff --git a/src/main/resources/quests/README.txt b/src/main/resources/quests/README.txt
index 9a607a6d..779dd6bb 100644
--- a/src/main/resources/quests/README.txt
+++ b/src/main/resources/quests/README.txt
@@ -8,6 +8,8 @@
 # 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.
@@ -16,12 +18,12 @@
 # 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).
+# 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 does /quests they will first see a menu of categories. They can click one and another menu of quests
-# under that category will show up. Categories can be disabled.
+# 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.
 #
 # ===============================================================
 #
@@ -29,3 +31,10 @@
 # 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
+#
+# ===============================================================