> For the complete documentation index, see [llms.txt](https://enchantedmobs.superiormc.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enchantedmobs.superiormc.cn/for-ultimatequest/information/faq.md).

# FAQ

## Why does a task not count?

Accept a normal task first; periodic and battle-pass tasks are assigned automatically, and milestones accumulate without acceptance. A scroll must be carried in the inventory or offhand and fit the [task limits](/for-ultimatequest/features/task-limits.md). Check the trigger is available on your platform, event conditions select the intended entity/item, the time window is active, and [anti-abuse](/for-ultimatequest/features/anti-abuse.md) permits the event. Cancelled events do not count through normal event routing.

## Why do edits not change an accepted task or its reward?

Instances store resolved objectives and rewards. Random rewards are drawn on normal acceptance, periodic instance creation, or first scroll activation; stage rewards are drawn when unlocked. Reloading or reconnecting does not draw again. See [rewards](/for-ultimatequest/configuration/rewards.md).

## Why is a completed task still using a slot?

Completion and claiming are separate states. Completed tasks occupy slots until claimed or removed through a permitted operation. Lowering a cap does not remove existing tasks.

## Why did deleted default files return?

Missing bundled definitions are extracted again. Keep the file and set `enabled: false`.

## Why can I not claim a reward?

Check completion, the claim window, the selected track, and premium access. `CLAIMING` or `REVIEW` indicates a reward claim that needs administrator review; an administrator must inspect delivery before resolving it. Permission bypass on a menu does not bypass reward checks.