aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLMBishop <13875753+LMBishop@users.noreply.github.com>2019-09-05 15:00:14 +0100
committerGitHub <noreply@github.com>2019-09-05 15:00:14 +0100
commit861dbd278700f98244374c0f0f0ad417e46336a6 (patch)
tree2406b87776f511aafb958647ba9989742fd3528e
parentfe97cd429b6234090a315c34701ead26a76fd24d (diff)
Update README.txt
-rw-r--r--src/main/resources/quests/README.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/src/main/resources/quests/README.txt b/src/main/resources/quests/README.txt
index fa0f0186..9a607a6d 100644
--- a/src/main/resources/quests/README.txt
+++ b/src/main/resources/quests/README.txt
@@ -8,8 +8,9 @@
# 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.
#
+# 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 rewardstring in use can be seen in the quest example4.
+# 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.
@@ -27,4 +28,4 @@
# You can see other task types here:
# https://github.com/LMBishop/Quests/wiki/Task-Types
#
-# =============================================================== \ No newline at end of file
+# ===============================================================