Quests

Quests are tasks for your members, such as building a house or finding diamonds. A member starts a quest, does it in Minecraft and says they finished. Your staff check it, and the member gets the Minecraft XP (and a rank, if the quest gives one). Every reward is given once.

Set it up

On the dashboard, open Quests and add your quests: a name, what members need to do, and how much XP it gives. No ideas yet? The empty page offers six example quests with one button; change them as you like.
Under Settings, Quests, choose a quest review channel that only staff can see. Finished quests are posted there with two buttons. Without one, the bot uses your staff alert channel, or else the admin alerts channel. Finished quests are always listed on the dashboard too.
Tell your members: they type /quests to see the quests and start one.

How a member does a quest

Not started. In /quests the member sees every quest with what it gives. Only they see their list.
Doing it. They press Start (or type /quest start). A member can have 3 quests going at once unless you change it.
Waiting for staff. When they finished it in Minecraft, they press I'm done (or type /quest finish) and may add a short note, such as where it is or a link to a screenshot.
Done. A staff member presses Confirm: the XP and the rank are given, once. Or they press Send back and say what is missing; the member is doing it again and sees the reason in /quests.

The member gets a private message either way, unless you switch that off under Settings, Quests. Members who do not accept private messages still see how it went in /quests.

For staff

Confirm and Send back are on the message in the review channel and on the dashboard under Quests, Waiting for review. Whichever is pressed first counts; pressing it twice, or two staff at once, gives the reward only once.
/quest sendback member: quest: reason: does the same as Send back.
/quest done member: quest: confirms a quest for anyone directly, whether they started it or not.
/quest track member: shows one member's quests: doing, waiting for staff, done and not started. /quest track quest: shows who is doing one quest, who waits for you, who finished it and how many linked players have not started it. On the dashboard: Quests, Progress, each quest's page and each member's page.
Nobody confirms their own quest: another staff member has to, so every reward is seen by two people.

Confirming and sending back need the same level as /quest done (Admin, unless you changed it on the Commands page). You can let your moderators review quests by lowering quest done and quest sendback there.

Smarter quests

Each of these is optional. A new quest is visible, done once and open to everyone, as before.

Repeatable: a quest can be done again every day, every week, or after any number of days up to a year. It gives the XP each time; a member who already has the rank it gives keeps it.
Needs a rank first: only members who have that rank can start it, for example a harder quest for Knights. A rank earned with XP counts when the member reached it or a higher one.
Hidden while you write it: members do not see a hidden quest. Members already doing it can still finish it.

Change a quest on its page on the dashboard, in one form, or with /quest edit. Changes count from now on: XP and ranks members already got stay.

What is kept

The quests themselves, who completed each one, when, who confirmed it and how often (for a repeatable quest).
For a quest a member is doing or finished: when they started and finished it, their note, and the reason it was sent back if it was. The note is removed when staff send the quest back or confirm it; the whole entry is removed when staff confirm it.
All of it is in the server data download and is removed with the server, or with the quest when you remove it.