INDEPENDENT BY DESIGN

The shared notebook

Terms, event literacy and memorable competitive history. This is an editorial community desk, not an open forum, registration service or invented live community.

Community reading

Researchers

How to read a Pokémon event calendar without missing the time zone

Identify the game or competition, location rules, exact start/end zone, registration deadline and source. A recurring event explainer is not a live schedule.

Read the guide
Researchers

Community glossary: shorthand is context, not a universal rule

Terms such as VGC, meta, shiny, raw, slab, comp and master set describe different parts of the hobby. Ask which game, format, language and era the speaker means.

Read the guide
Researchers

Myths, cut content and Easter eggs: the evidence ladder

A repeated story is not confirmation. Separate released-game behavior, developer statements, documented unused material, hypotheses and folklore before calling something a secret.

Read the guide
Researchers

The 2014 Pachirisu lesson: team fit beats a species stereotype

Se Jun Park’s championship Pachirisu is a documented example of support value in doubles. It is a historical case study, not proof that one species is optimal in every format.

Read the guide
Researchers

Ruins of Alph: the radio detail hiding beside the puzzles

The official Johto retrospective documents mysterious Pokégear radio transmissions inside the Ruins of Alph. It is a confirmed atmospheric detail—not evidence of a secret evolution or an invented hidden encounter.

Read the guide
Researchers

Johto’s hidden schedule: the world keeps a weekly rhythm

Johto’s clock affects more than day and night. The official retrospective documents weekday visitors and the Bug-Catching Contest’s Tuesday, Thursday and Saturday schedule in its historical Johto context.

Read the guide
Researchers

Johto after the Champion: why the credits are not the whole map

The official retrospective documents the journey from Johto to Kanto after the League, with another set of Gym Leaders and a later challenge at Mt. Silver. It is a major progression spoiler, not an invented secret region.

Read the guide
Researchers

Hoenn’s Feebas puzzle: six tiles are not a whole route

The official Hoenn retrospective describes Feebas in Ruby/Sapphire as available on six changing fishing spaces on Route 119. That historical mechanic should not be generalized to every later game or remake.

Read the guide
Researchers

Hoenn’s legendary puzzle: Braille, prerequisites and version discipline

Official Hoenn history confirms that the Regirock, Regice and Registeel quest uses Braille and involves Wailord and Relicanth. It does not validate every circulating party-order or movement instruction for every version.

Read the guide
Researchers

FireRed & LeafGreen: read the Braille clue, not the neighboring game’s solution

Official guidance confirms Braille messages in FireRed and LeafGreen and supplies a chart. The chart can help decode text; it is not proof that a Hoenn puzzle solution applies to Kanto.

Read the guide
Researchers

Mew and the 300-byte story: development history, not a truck walkthrough

Nintendo’s indexed Iwata Asks interview describes Mew being added after removed debug features freed 300 bytes. Direct-page retrieval needs rechecking; the account does not establish a normal in-game truck encounter.

Read the guide
Researchers

Delta Reign vs Storm Emeralda: compare evidence, not translated names

Delta Reign and Storm Emeralda have different dates, languages and catalog namespaces. Related themes do not prove a one-to-one set translation.

Read the guide
Researchers

MissingNo.: when encounter data stops meaning what it should

MissingNo. is a glitch encounter, not an established hidden-story quest. This article summarizes the well-known old-man encounter glitch in the original Red and Blue games from secondary references. It does not explain every MissingNo. encounter, variant or version.

Read the guide

Contribute a correction, not a password

Send a page URL, the disputed detail and a public source to support@dexvoyage.com. No automatic public contributions, profiles, location-sharing, marketplace, chat or uploads are enabled. Permission and moderation terms must be reviewed before any community submission system is introduced.