Pocket Deal Radar
Search

Polished Crystal Unown: open the locked door-shaped grooves

Separate a missing caught form from a missing follow-up conversation before revisiting the closed passage.

Creator FAQ checked 8 Oct 2026; compare your installed build

The two-part door requirement

Make two separate entries in your session plan: the collection and the conversation. Check all distinct caught forms first, then record the follow-up conversation. Revisit the door after the missing step is complete.

This answer concerns the named door-shaped grooves. Do not apply the requirement to every locked entrance, story obstacle or puzzle in Johto. Identify the location and the interaction text before choosing an Unown collection trip.

Audit the caught-form collection

  1. Inspect the in-game Unown record and the forms you have actually caught.
  2. Give each distinct form one consistent label in your notes. Avoid counting two copies of the same form twice.
  3. Separate an encountered form from a caught form; the stated requirement is catching.
  4. Compare the full collection again before marking the prerequisite complete.

Example: you have 28 captured Unown but two share the same form. The capture total has reached 28; the distinct-form collection has not. Identify the gap in your own record before treating another encounter as useful progress.

Keep your missing-form notes specific enough to recognise the target during a later session. A note such as “need one more” is easy to lose track of; a consistent form label makes the next inspection meaningful. For chamber locations and encounter rates, use the maker documentation for your build; this checklist tracks the forms you have caught.

Local collection checklist

Record labels you recognise from your caught forms, one per line. This is a local checklist, not a form-identification database or a save reader. A count of 28 labels still needs your in-game collection check.

Collection and scientist checks

Use the same short label each time you refer to a form. Different nicknames for the same form are still one form. Blank lines are ignored; repeated labels are flagged.

0 distinct labels entered

Compare your caught-form record with the in-game Unown Dex. Record one distinct caught form per line.

Entries remain in this open page and clear on reload. Editing the list clears both confirmations so a previous collection check is not reused. The checklist never verifies that a door has opened.

Speak to the scientist, then return

After checking the completed collection, revisit the scientist associated with receiving your Unown Dex. Record that follow-up interaction as its own step, then return to the intended groove and read the actual response.

Choose a small, observable endpoint for the session: “checked the full collection and spoke to the scientist” or “returned to the Route 47 groove and recorded its response.” That is more useful than a vague note saying the whole area is finished. The checklist records your prerequisites; the game supplies the outcome.

If your notes only show a conversation from before the collection was complete, do the follow-up after completing it. Keeping the order explicit avoids confusing receipt of the Dex with the later completion check.

If the groove stays closed

Your observationNext check
Many captures, uncertain distinct formsAudit the caught-form record, including duplicates
Complete collection, no follow-up noteSpeak to the scientist who gave you the Unown Dex
Both checks recorded, no opening observedRecord the exact location, interaction text, edition and build
A different entrance is blockedIdentify that obstacle’s own requirement before using this guide

When the reference and your game still disagree, retain the observed dialogue and prerequisite sequence. That creates a precise question for the project’s help channels. A screenshot of the relevant record can help you explain what you checked; include the missing-form audit and scientist dialogue so the maker can identify which step needs attention.

A closed passage alone is not evidence of an emulator failure. If you also have input or save symptoms, investigate those separately with the GBC emulator and save guide. Use the game profile for recorded runtime requirements.

Unown questions

Does entering 28 labels prove I completed the collection?

No. You supply the labels and confirm the actual caught forms in-game. The helper detects repeated labels but cannot recognise a form or inspect your save.

Should I keep searching after confirming all forms?

Check the follow-up scientist interaction before choosing another collection session. A missing conversation calls for a different task from a missing form.

Does this describe original Crystal’s puzzles?

This answer follows the checked Polished Crystal FAQ. Use the documentation for the game and build you are playing.

Source and related tasks

Maker FAQ: door-shaped grooves and Unown, checked 8 Oct 2026. The two-part requirement comes from that FAQ. The audit method and checklist record your own observations; no independent door-unlock playtest was performed.

For your next team adjustment, use the evolution-item source table or friendship service explanation. Return to the preparation guide for choosing a bounded exploration task.

Based on the creator's documentation, checked 8 Oct 2026. Not hands-on tested unless a section says 'We played it'.

How we check