accept Action

Marks a quest as accepted/active. Use this when the party agrees to undertake a quest.

Syntax

accept:Quest Name

Usage

Add to the questActions array in a choice object:

{ "text": "Accept the quest", "nextScene": "ep1-scene2", "questActions": ["accept:The Missing Merchant"] }

What Happens

  1. Quest state changes from "available" to "active"
  2. The quest is logged to that party's local quest log
  3. It appears in the Party Sheet's "📜 Quest Log" section for the rest of the session

Requirements

Name Matching: Quest names are case-sensitive and must match exactly:
✓ accept:The Missing Merchant
✗ accept:Missing Merchant (missing "The")
✗ accept:the missing merchant (wrong case)

Complete Example

{ "sceneId": "ep1-scene1", "title": "The Quest Giver", "readAloud": "<div class='read-aloud'><p>The mayor of {nearestBurg} approaches you with a worried expression. 'We need brave adventurers to investigate strange disappearances on the road to {randomBurg:maxPopulation=300}.'</p></div>", "choices": [ { "text": "Accept the quest to investigate", "nextScene": "ep1-scene2", "questActions": ["accept:Investigate Disappearances"] }, { "text": "Decline and leave", "nextScene": null } ] }

Multiple Quest Acceptance

You can accept multiple quests in one choice (rare, but possible):

{ "questActions": [ "accept:Main Quest", "accept:Side Quest" ] }

Best Practices

Always Provide Decline Option

Give players the option to decline:

✓ Good: Offer both "Accept" and "Decline" choices
✗ Bad: Only "Accept" button (forces quest acceptance)

Accept Early in Episode

Typically accept quests in the first or second scene:

✓ Good: ep1-scene1 or ep1-scene2
✗ Bad: Halfway through episode

Provide Context Before Acceptance

Explain the quest before asking for acceptance:

"readAloud": "<div class='read-aloud'><p>[Explain the problem, stakes, and rewards]</p></div>"

See Also