Following a quest

Admission

• Automatic — every member follows the quest as soon as it is open, without asking; all their activity in the occurrence counts.
• OnAcceptance — only the activity after the member accepted the quest counts, and only the activity of members who accepted it is kept.

A team quest and a duel are always joined by acceptance: the first under a team, the second when a member accepts a challenge.

$quests->accept($member, 'winter-reading');
$quests->accept($member, 'raid', ResourceReference::of('team', 'red'));
$quests->abandon($member, 'winter-reading');

Accepting is refused when the quest is a duel, closed, locked behind the quest it follows, accomplished already in its occurrence, a team quest without a team or another quest with one. Accepting a quest followed already returns the enrolment as it is; a team member who wants another team abandons the quest first.

Abandonment

Abandoning stops the member's activity from counting from that moment. Abandoning a quest followed automatically writes an enrolment for it; accepting it again takes it up with everything it counted. Abandoning a quest accepted, then accepting it again, counts from the new acceptance. An accomplished quest can no longer be abandoned.

Where a quest stands

Quests::status($member, $code) reads a QuestStatus: the quest, its QuestState, its occurrence open now, the progress of its subject — the member, the member's team or the community —, the completion that accomplished it, and the team.

Quests::board($member) reads the status of every quest but the duels; Quests::completions($subject) reads the journal of the quests a member, a team or the community accomplished.