Control quest assignment

Assignment rules decide which quests a player can receive and how they begin.

Option order

BDQ reads options in this order:

1. A value set on the quest.
2. A value set on the quest group.
3. The plugin default.

This lets a group use one rule while a special quest uses another.

quests:
  training-stone:
    group: "training"
    options:
      repeatable: true
      sequential-tasks: true

Automatic assignment

When automatically-given is true, BDQ tries to fill the group to the player's assignment limit after player data loads and after a scheduled group reset.

A quest is not eligible when:

• the player already has it;
• it is complete and not repeatable;
• it belongs to another group;
• another rule makes it unavailable.

Manual bdq give does not fill the whole group. It gives one selected quest.

Repeatable quests

Use repeatable: true only when the quest and its rewards are safe to complete more than once. A non-repeatable Quest ID in completion history is not selected again.

Waiting assignments

need-starting: true creates an assignment that cannot progress until it is started:

bdq start questID
bdq start-others PlayerName questID

Players can also run bdq quests and left-click a waiting assignment. Give players betterdailyquest.command.start when they should start their own assignments by command or click. Reserve betterdailyquest.command.start.others for trusted staff. Both start paths require the target player to be online and loaded.

Keep need-starting: false when assignments should receive progress immediately.

Check the design

Test with a new player and a player who already completed some quests. Confirm:

• the group fills to the correct limit;
• completed non-repeatable quests stay excluded;
• repeatable quests can return;
• sequential tasks do not progress early;
• rewards cannot be repeated in an unsafe way.

For role limits and reset behavior, see Manage assignments and resets.

Next step

Add progress conditions.