Unbound Mission Log, Dowsing Machine and mining guide
Check recorded collection progress, set up exploration shortcuts and separate postgame ADM tasks from the next objective in your campaign.
Use the Mission Log to separate found items from missing ones
The creator FAQ says collectible details, including Zygarde Cells, Legendary Portals and TMs, are recorded in the Mission Log when you find them. Treat it as your run’s record, not as proof that an unvisited place has already been checked.
| Your question | Start with | Useful observation |
|---|---|---|
| Did I already find this collectible? | The relevant Mission Log entry | What the game has recorded in this run |
| Which nearby task should I do next? | Current location and an accessible objective | One task with a clear completion check |
| Why is this objective still open? | The entry’s conditions and your actual progress | The missing condition, not only the objective name |
| Does another player’s route apply to me? | Your game edition and current access | Which prerequisite their route assumes |
Before returning through several areas, list what you already know: objective, recorded progress, places you actually checked, and the condition that remains unresolved. This is particularly useful when a broad walkthrough mixes a first campaign with postgame exploration.
Example: a collection objective remains unfinished after a long session. Review recorded finds before searching the same place again. If the log does not establish the missing location, keep that location open as a question; this page does not invent a complete coordinate list.
Keep the Dowsing Machine on a convenient registered input
The FAQ addresses the Dowsing Machine disappearing when a text box opens: register the Motorcycle first and Dowsing Machine second, then set L-Button Mode to 2nd Reg Item in Options.
- Check the order of your registered items.
- Select the intended L-Button Mode in the game’s Options.
- Return to a suitable exploration area and try the mapped GBA L input.
- After a conversation closes, invoke the tool again through that input.
- If it does not respond, check whether the same input works elsewhere.
The setting names refer to GBA commands, which may differ from the labels on your handheld. If a system shortcut captures L before the game receives it, changing registered-item order alone will not fix the input path. Use the GBA control diagnosis to investigate that symptom.
Example: the tool works when selected from the menu, but not with the shoulder button. That result narrows the problem to registration, the selected button mode or mapping. It is a different problem from a tool you have not obtained.
Dive and mining: check ADM access first
The creator’s route to the ADM is postgame purchase from Captain Davy in Seaport City’s shipyard. With an ADM, select Mining Scan as R-Button Mode and press R while exploring KBT Expressway, underwater or Crystal Peak’s left side room.
| Task | First check | Then check |
|---|---|---|
| Use the documented Dive route | Campaign clear and ADM access | The place where you intend to dive |
| Scan for mining | ADM ownership | R-Button Mode and the mapped input |
| Try mining in another area | Whether it matches a documented scan area | The result of the scan |
| Make a detour for postgame treasure | Whether the service is available in this run | One reachable objective rather than a whole route assumption |
Do not make a postgame tool the required answer to an early-story obstruction. Read the current objective and choose the route available to you now. If the goal is optional exploration after clearing the game, the ADM route belongs in that later plan.
The table is an access and controls guide. It does not establish exact treasure odds, scan intervals, mining rewards or every usable tile. Check the in-game response before extending a route based on an assumption.
Field eligibility before spending a move slot
The creator describes field HM use through a Pokémon that can learn the move, without requiring it to occupy a battle move slot. The postgame ADM provides a separate route. Do not turn the later tool into a prerequisite for every earlier journey.
| Question | Check | What it tells you |
|---|---|---|
| Can the party supply this field action? | The relevant member’s eligibility and the game’s current prompt | Whether the current team fits this task |
| Is the action available at this stage? | The actual progression and access requirement | Whether a route condition remains |
| Does the offered command respond? | The mapped GBA input in the named context | Whether controls require investigation |
| Are you relying on the ADM? | Postgame access and actual ownership | Whether that later route applies now |
Example: you are about to replace a useful attack only to pass a field obstacle. First check whether an eligible party member already supplies the documented field action. If the option is absent, investigate eligibility and progression before spending the move slot. This is not a complete badge-by-badge HM table.
Keep the battle team’s jobs separate from the field task. The party review describes your checked battle roles; it does not verify HM eligibility. A member can solve one task without being the answer to the other.
Treat save missions as progress over real sessions
The maker says save-count missions are intended to reward normal play and recommends enabling save prompts. They are not an instruction to stand still repeatedly saving instead of progressing.
- Read the mission’s actual progress in your own run.
- Choose a real exploration or battle objective for the session.
- Use the game’s save prompt or a deliberate in-game checkpoint as you progress.
- At the end, inspect the mission separately from the ordinary save’s Continue check.
Example: you finish a tool-configuration session and save. Your immediate result is a working shortcut and preserved progress; the save-count goal can continue across later sessions. Do not replace the objective you wanted to play with a repetitive counter exercise just because the mission remains open.
On a handheld, emulator quick-resume and saving inside Unbound are separate operations. This guide does not claim a state file counts toward the mission. Use the GBA save workflow to verify ordinary progress, and the Mission Log to inspect the game’s own objective record.
Plan one exploration session with an observable finish
Choose a goal small enough to verify: inspect one recorded collection entry, configure the Dowsing shortcut, or try Mining Scan in one named area after obtaining the required tool. Write the starting location and required access beside that goal.
Worked example: you return after a break and remember wanting to mine, but have not recorded the relevant tool. First inspect your key items and campaign progress. If the ADM is missing and its documented access is still unavailable, choose a current mission or recruitment goal. If it is present, configure the scan input and test a listed area. Both branches end with a concrete next action.
Finish by noting what changed: a log entry, a working shortcut, an obtained prerequisite or a question that remains. That is more useful for the next session than “explored for a while.” The local session notebook can store that note; it does not inspect your save or count collectibles.
For battle preparation, use Unbound difficulty, EXP and scaling. For the separately documented original TrimUI Brick software path, use the game/device guide. Neither is evidence that every handheld configuration behaves identically.
Exploration questions
The Dowsing Machine closes after talking to someone. Is my save broken?
The maker FAQ specifically addresses that interface behavior with the second registered-item shortcut. Try the documented invocation before treating it as save corruption.
Can I use an ADM route before finishing the story?
The purchase route checked here is postgame. Do not plan an early-story task around access the reference does not establish.
Is this a complete collectible walkthrough?
It explains recorded progress, documented tools and a session plan. It does not list every collectible location or promise an exact completion route.
Sources and version scope
Mechanics are paraphrased from these maker references. Worked examples and the order of checks are Pocket Deal Radar’s interpretation, not independent playtests or hardware results. Compare the reference with your installed game. The game profile retains its separate release and patch evidence.
For emulator, storage and save-file setup, use the platform handheld guide. This page provides no ROMs, BIOS files, prepatched games or mirrors.
Based on the creator's documentation, checked 8 Oct 2026. Not hands-on tested unless a section says 'We played it'.
How we check