Quest Tracking¶
Track field research quests by their rewards — pokemon encounters, items, stardust, pokecoins, mega energy, and candy.
Filter syntax
Filters use key:value form — d:500, area:downtown, template:2, stardust:1000, energy:charizard. Legacy d500 / stardust500 are still accepted. Multi-word item names can be typed with spaces or underscores: rare candy, golden_razz_berry. See Pokemon Tracking — Filter Syntax.
Pokemon Encounter Rewards¶
!quest spinda # Quests rewarding Spinda
!quest pikachu # Quests rewarding Pikachu
!quest everything # All quest rewards
!quest pikachu charmander d:500 # Either pokemon as reward, within 500m
!quest vulpix form:alola # Alolan Vulpix encounters only
!quest all_pokemon # Every pokemon-encounter reward
Shiny-Eligible Quests¶
all_pokemon (and all_items, below) must be typed with the underscore. Together with everything they are bulk options: if the admin sets everything_flag_permissions = "deny", only admins can use them.
Stardust Rewards¶
Pokecoin Rewards¶
Mega Energy Rewards¶
Candy Rewards¶
Item Rewards¶
Track specific item rewards. Multi-word names work with spaces or underscores:
Use !info items to see every item name the bot recognises.
Every reward you name in one command becomes its own rule, so you can mix kinds:
!quest stardust pikachu pokecoins # Three rules: stardust, Pikachu encounters, pokecoins
!quest energy:charizard spinda # Charizard mega energy + Spinda encounters
!quest energy candy pikachu # Pikachu mega energy + Pikachu candy (no Pikachu encounter rule)
A bare energy or candy takes the pokemon named in the same command as its target, so those pokemon don't also become encounter rules; use energy:<pokemon> / candy:<pokemon> if you want both. everything already covers every reward type, so anything named alongside it is ignored.
Only one item is recognised per command. To add several items at once, separate them with |:
amount:<n> sets a minimum quantity for item, candy and mega energy rewards (and acts like stardust:<n> / pokecoins:<n> with those keywords). It applies to every reward in the command that has an amount, and is ignored for pokemon encounters. It is rejected only when pokemon encounters are the only reward named (!quest pikachu amount:5).
5.3+
Before 5.3 a command with several reward kinds kept only the first one (stardust, then pokecoins, energy, candy, pokemon, item) and dropped the rest without saying so: !quest stardust pikachu tracked only stardust.
Distance and Areas¶
See Areas & Locations for the full area: / location: rules.
All Quest Options¶
| Option | Description | Example |
|---|---|---|
<pokemon> |
Quest rewarding a pokemon encounter | spinda |
form:<name> |
Pokemon-encounter form | form:alola |
all_pokemon |
Every pokemon-encounter reward | all_pokemon |
stardust / stardust:<n> |
Stardust reward (any, or minimum amount) | stardust:500 |
pokecoins / pokecoins:<n> |
Pokecoin reward (any, or minimum amount) | pokecoins:10 |
energy / energy:<pokemon> |
Mega energy (all, or specific) | energy:charizard |
candy / candy:<pokemon> |
Candy (all, or specific) | candy:lapras |
<item_name> |
Specific item reward | rare_candy |
all_items |
Every item reward | all_items |
amount:<n> |
Minimum quantity (items, candy, mega energy) | amount:3 |
shiny |
Shiny-eligible encounters | shiny |
d:<n> |
Distance in metres | d:500 |
location:<name> |
Distance from a named location (requires d:) |
location:Home |
area:<name>[,<name>] |
Restrict to specific areas | area:downtown |
template:<n> |
Alert template | template:2 |
clean |
Auto-delete expired alerts | clean |
summary |
Buffer matches for grouped delivery on a schedule | summary |
everything |
All quest rewards (pokemon, stardust, pokecoins, energy, candy, items) | everything |
remove |
Remove tracking | remove |
edit is not accepted on !quest.
Legacy no-colon forms (stardust500, pokecoins10, energycharizard, candypikachu, d500) still work.
Buffered Summary Delivery¶
Instead of receiving a separate message for every matched quest, you can opt a rule into summary delivery: matched quests are held in memory and dispatched as grouped messages on a schedule you set (e.g. one digest at 07:30 each weekday morning, grouped by reward).
Add summary to any !quest rule:
!tracked shows summary next to each rule that uses it.
A grouped message lists every pokestop with the same reward in one embed, with a multi-pin static map showing all of them. Large groups split into multiple messages automatically so they stay under Discord's embed limits.
Schedule when those grouped messages fire — and flush the buffer on demand — with the !summary command. Without a schedule, matched quests accumulate but are never dispatched until you either run !summary quest now or set a delivery time.
Note
Summary delivery is currently supported only for quest tracking. Other alert types (raids, invasions, etc.) may gain summary support in future releases.
Removing Tracks¶
!quest remove spinda # Stop tracking Spinda quests
!quest remove stardust # Stop tracking stardust quests
!quest remove all_items # Every item-reward rule
!quest remove all_pokemon # Every pokemon-reward rule
!quest remove pokecoins # Stop tracking pokecoin quests
!quest remove pikachu summary # Only the summary-mode Pikachu rule
!quest remove everything # Remove all quest tracking
!quest remove id:12 # One rule by ID (see !tracked)
!untrack quest id:12 # Same as !quest remove id:12
Unlike adding, !quest remove still handles one reward kind per command: !quest remove stardust pikachu removes only the stardust rule. Remove each kind separately, or join them with | (!quest remove stardust | remove pikachu).
!quest remove with nothing else removes all your quest tracking. form: is not accepted on remove (removal is species-wide) — remove a single form's rule by its ID. Plain !untrack id:12 removes a pokemon rule, not a quest rule.