Pokebert's Canonical Guidelines for Pokémon Playthroughs

Rule 0 — The Grant Principle

An outcome is canonical if and only if the game granted it.

Legitimacy is a question of authorship, not tooling. Hardware, software, and external services are proxies - negotiable whenever they stop serving the experience. What is never negotiable: every Pokémon, item, stat, and event in a canonical save must have been generated by the game's own behavior, never specified by the player — except where the game itself officially solicits player input (naming your Pokémon, choosing a starter, answering an NPC). Input the game asks for is part of the grant.

0.1 — Scope of judgment. More specifically, these guidelines judge claims, not artifacts. Nothing is forbidden in itself; a save, tool, or technique is only ever prohibited relative to the class it claims (see Rule 6). The sole true violation in this canon is misrepresentation: presenting a non-canonical artifact as Canon.

0.2 — Advantage neutrality. This canon judges authorship, not advantage. Material gain neither legitimizes nor delegitimizes any act; content that passes Rule 0 remains canonical however profitable, and content that fails it remains excluded however harmless. (Precedent: Emerald RNG manipulation is pure material gain and fully Canon; a record-mixed EXP-farm base is authored cargo whether or not it enriches the recipient. See In re Toto's Base, Appendix.) Advantage does, however, trigger heightened audit under 3.6.

0.3 — Definition of "the game." "The game" means any authentic instance of it, including its officially designed cross-save channels (trades, record mixing, Mystery Gift, Pokéwalker strolls). Content received through those channels is game-granted. This defines what counts as granted — how granted content may be moved is governed solely by Rule 3.

All rules below are applications of Rule 0. Where a new situation arises that these rules don't cover, resolve it by Rule 0.

---

Rule 1 — Platforms & The Realizability Principle

1.1 Within 12 years of a game's release, play on authentic cartridges and original hardware.

1.2 Exceptions at any time, playable via emulation or homebrew sideloading:
- Pokémon Gold Spaceworld 1997 demo
- Pokémon Diamond and Pearl prototypes
- Authentic event distribution ROMs
- Official Virtual Console releases
- Leaked official builds and prototypes generally (see 4.3)

1.3 Sunset clause: once 12 years have elapsed since release, all platform distinctions dissolve. Original hardware degrades and secondhand prices become exclusionary; authenticity of platform was always a proxy for authenticity of experience, and expires when it stops serving it.

1.4 Realizability Principle: a method is legitimate if it can be performed end-to-end on original hardware, whether or not you personally perform it that way. If authentic consoles, link cables, and a flash cart could accomplish it physically, executing the equivalent in emulation changes the means, not the meaning.

1.4a — Methods, not end states. Realizability blesses methods, never outcomes. A save editor is not a realizable method regardless of hardware, and an edit does not become legitimate merely because its resulting bytes are identical to a state an official act could reach — end-state equivalence would legitimize fabricating any plausible content. Transport of actually-existing game-granted data is governed by Rule 3, not by this rule. (In re Toto's Base, Holding 1.)

---

Rule 2 — Infrastructure Restoration & Distribution

2.1 External services and tools that restore or replicate deprecated official functionality are legitimate.

2.2 Restorations must faithfully reproduce the original presentation and behavior - restoration, not enhancement.

2.3 Accessing them through built-in console features (e.g., DNS settings) is legitimate.

2.4 Recognized examples: Poke Classic Network as a replacement for the GTS and Nintendo WFC.

2.5 Mystery Gifts and event items are valid when the receiving game accepts them through its own unmodified reception code, with no external tools and no modification to the receiving game. The game vouches for what it accepts through its own front door. Unofficial distribution ROMs are therefore legitimate as senders.

2.6 Spirit clause: Rule 2.5 must not function as a PKHeX substitute. Distribution through official channels does not launder arbitrary content into canon; distributed items and Pokémon must be consistent with what official event infrastructure would plausibly carry. The same applies to the Pokéwalker: unofficial tools can technically push any gift or Pokémon to it, but doing so violates the spirit of authenticity.

2.7 Community events: Rule 2.5 extends limited but legitimate blessing to non-official events distributed in official event format - e.g., the July 2026 Anthrocon BPSHOP Seaking.

---

Rule 3 — Save Maintenance, Repair & Migration

3.1 External save tools are legitimate when they preserve, repair, or transport game-granted content:
- Backing up saves off degrading media
- Restoring a save after a cartridge battery replacement (including RTC repair, e.g., reviving Emerald's berry clock)
- Repairing malformed or residual data - e.g., removing stale Trainer House records left behind by Pokéwalker experimentation
- Migrating Pokémon or saves forward when official transfer infrastructure no longer exists

3.1a — Reasonable availability. An official channel is treated as unavailable under 3.1 when performing it would require participation, hardware, or access not reasonably obtainable at the time of the act - not merely inconvenient, but genuinely beyond reach (e.g., the sole counterpart save is held by someone with no means to dump or link it). Availability is assessed at the time of the act; rulings under this clause carry a date and lapse when the channel becomes reasonably available, after which the official act is obligatory for future transports. (In re Toto's Base, Holding 2.)

3.2 The edit may act on the container, never the contents. Fabricating or altering items, species, shininess, stats, IVs, ribbons, met-data, or event flags is prohibited — regardless of tool.

3.3 Interoperability exception: editing trainer record data only (name, TID, SID) is legitimate when its purpose is to unlock officially designed functionality obstructed by an incidental technical limitation - e.g., altering trainer identity so one save's Trainer House can receive distinct teams from multiple Pokéwalkers. The teams themselves remain game-granted; the edit adjusts the addressing, not the cargo. This exception is void the moment identity edits touch a Pokémon's provenance - TID/SID manipulation to alter ownership, legality, or shininess is content fabrication under 3.2.

3.4 Intergenerational transfer: moving Pokémon between Gen 2 and Gen 3 (e.g., via Poke Transporter GB) is legitimate under the Realizability Principle (1.4): the fan-made transfer ROM can be run on a flash cart across real GBAs and link cables, so the transfer is physically achievable on authentic hardware. Content is transported, never authored - Rule 0 is satisfied.

3.5 Litmus test: after the edit, does the save contain anything the game did not generate? If yes, the save leaves Canon class.

3.6 — Heightened audit. When a transport under this rule confers material advantage, the verbatim requirement is inspected with elevated scrutiny: the transported data must be byte-perfect as originally granted, and any deviation - however small - is authorship under 3.2 and misrepresentation under 6.6. Advantage never changes the law (0.2); it changes how carefully compliance is verified. (In re Toto's Base, Holding 4.)

---

Rule 4 — In-Game Actions & External Knowledge

4.1 Any action achievable through sanctioned inputs alone is presumptively legitimate (subject to Rule 5).

4.2 External knowledge is always legal. Guides, damage calculators, Feebas tile calculators, RNG timers, disassembly research, pen and paper - knowledge is not a tool acting on the game. Frame-precise execution informed by external computation (e.g., Emerald RNG manipulation) remains vanilla input and is fully canonical.

4.3 Provenance of knowledge is out of scope. This canon evaluates the authorship of game-state, not the real-world chain of custody of information. Knowledge and data originating from the games' official creators - Nintendo, Game Freak, Creatures Inc., ILCA - is first-party truth about the games and fully canonical as knowledge, regardless of whether it reached the public through official publication or leak. Leaked source code, design documents, and debug material are authored by the same hands as the retail ROMs; the canon does not distinguish how they escaped the building. Leaked playable builds are governed by 1.2 as prototypes. (Canon status is a statement about legitimacy within these guidelines, not a legal opinion about anything else.)

---

Rule 5 — Glitches & The Authorship Line

5.1 Legitimate: glitches in which the game misbehaves on its own terms - misread data, corruption, underflow, stale memory. The game remains the author of the outcome; the player merely triggers the fault.
- Examples: MissingNo., trainer-fly Mew glitch, Pomeg glitch, bad clones, glitch Pokémon generally.

5.2 Excluded from Canon: Arbitrary Code Execution. ACE is excluded not because the code is "unprogrammed" - the CPU only ever executes bytes legitimately present in memory — but because the player deliberately arranges memory to encode instructions of their own design. The game becomes an interpreter for a player-written program; authorship transfers from game to player, violating Rule 0. ACE saves and products are Feat-class (6.4), never Canon.

5.3 Litmus test: could the player have specified the outcome's content in advance? A glitch hands you whatever the fault produces. ACE produces whatever you wrote. The former is discovery; the latter is authorship.

5.4 Consistency note: hand-performed ACE and an Action Replay both write player-chosen values to memory. A canon that admits one and excludes the other is ranking convenience, not legitimacy. Both are excluded from Canon for the same reason.

---

Rule 6 — Classes of Record

Fabrications hold no class (6.7). Per 0.1, the only violation is claiming a class you don't hold.

6.1 — Canon. Playthroughs satisfying Rules 0–5 in full. The only class in which outcomes count as obtained.

6.2 — Restoration class. Playthroughs of works assembled exclusively from official content, where the unofficial contribution is editorial, not creative:
- Bug-fix-only ROM hacks
- Re-enablement of dormant or regionally removed official content (e.g., an English-language Game Corner restoring HGSS slot machines)
- Reconstructions of unreleased canonical content from official material (e.g., Super Gold 97 completing the Spaceworld-era game)

Restoration is to Canon what a critical edition is to an original manuscript: every word is the author's; only the assembly is the editor's. Closest class to Canon - but the text is not the retail text, so its saves are Restoration-class, never Canon. Whether Restoration-obtained content may migrate into Canon saves is a recognized grey area: no official ruling is made, and the question is left to individual judgment. Restorations claiming fidelity are held to that claim: content not traceable to official material demotes the work to Apocrypha.

6.3 — Apocrypha. ROM hacks and modified works generally. Fully valid as works and as playthroughs - a completed ROM hack save is a real accomplishment - but they make no canonical claim and their contents never migrate into Canon saves.

6.4 — Feat class. Performance records: hand-executed ACE, TAS-verified routes, and similar acts of mastery. The act is honored; the resulting save and its products are Feat-class, never Canon, permanently.

6.5 — Research class. Any technique whatsoever - ACE, memory editing, debugger use, prohibited tools - is valid when conducted for documentation and research (e.g., TCRF contributions, glitch research, preservation work). Research produces knowledge, and knowledge is always canonical (4.2, 4.3). Research saves are Research-class - a sibling of Feat, not a subclass of it; the findings they generate are Canon-usable by everyone.

6.6 — Misrepresentation. The only prohibited act in this canon: presenting a save, Pokémon, or outcome as Canon when it is not - fabricated content in a claimed-legitimate save, TID/SID provenance laundering, distribution-ROM injection posing as an event, an Apocrypha or Feat product traded as caught. Class fraud, in every form, is the crime. Everything else is just a different shelf in the library.

6.7 — Fabrications hold no class. Genned and hacked content is never valid — not as Canon, not as anything. Content authored directly by the player without play - PKHeX'd Pokémon, Action Replay products, genned items - is not a record of anything, and the classes of this rule classify records. An honestly labeled fabrication is therefore not prohibited as an object (0.1), but it is null: it holds no class, documents no act, and can never validly claim one. It is a book-shaped object with blank pages - not a lesser shelf, but unshelvable. Purpose can redeem the save around it: fabrication performed in service of a documented act takes that act's class (fabricated test subjects for mechanics research are Research-class per 6.5). The bytes alone, absent an act, are nothing - and any downstream claim of class for them, by anyone, is misrepresentation under 6.6 committed at the moment of the claim.

Appendix — Case Law

In re Toto's Base (July 2026)

Facts. Petitioner held a Secret Base record legitimately obtained from a friend via Gen 3 record mixing, and sought to transplant it by save editor into a new save. The friend's originating save existed but was ~2,800 miles away; no authentic-hardware remote link existed at time of ruling, and the emulated official route required the friend to possess save-dumping capability, which was unverified. The base contained a six-Blissey EXP-farming team.

Holdings.

1. Advantage neutrality.

1. Material gain is legally irrelevant; the canon judges authorship. The farm's utility was authored cargo. Codified as
2. Heightened audit. Advantageous transports face elevated verification of the verbatim requirement.

Disposition. Transplant ruled Canon as of July 2026, conditional on factual verification that the friend lacks dump capability; ruling lapses if the official channel (including emulated record mixing under 1.3) becomes reasonably available. Preferred remedy noted for the record: perform actual record mixing remotely where possible - the canon favors playing the game.

I really don't know, the luck's been looking up today

HM Enjoyer threw hands

Found it on my 342th reset and a had an master ball to but I chose to gamble like a fool.

Had to squeeze my eyes just to catch this little shit but was worth it at least

Still can't velieve I got the hidden ability btw

FINALLY!!! After 7 days of hunting it's now finally here!! Now I can finally leave this place and continue the solo gym challenge for Dunsparce! 🥹✨

To be honest I wasn't planning to shiny hunt this Electrode but I figured out that they will never respawn again so that's why I ended up trying anyways.

I'm also glad that this Electrode doesn't know self destructing moves as if they were meant to be shiny hunted. 🫠

So this copy of platinum only has 7 badges and so only pokemon up to level 70 will listen to me if they're from another game. So I sent a shroomish egg to platinum, hatched it so it would have platinums trainer ID, and then trained it in another game to level 80. I did all this with the future Giratina hunt in mind. One thing I gave too little consideration towards was the ability it had, effect spore, I saw it could poison but in all the training I did it never did that so I figured I could run those odds. Well on the third sneasel I false swipe it, it hits me, gets poisoned, dies. Then the same thing happened again with the 4th sneasel. So the shinies shown in the video are actually the 1st, 2nd, and 5th shiny sneasel from the hunt. Needless to say I'm training up a new breloom with poison heal instead of effect spore.

TLDR I lied in my last post, I do in fact not still have it

What is the worst shiny encounter?

Riiiight a shiny that's impossible to catch.

I play the battle factory for over a year to beat it. It was one of my hardest pk challenges. Got me finally my gold pass so it was worst the time~

The shiny was a nice suprise but it makes sense cause the ev values are not fixed.

Started hunting for this Turtwig on the 17th of April this year, today it finally shined at 2574 encounters!

Since I was hunting on a single console, the estimated hours for this hunt was approximately 85hrs.

It's been an hour later since I found this, and I'm still in disbelief that the dreaded briefcase simulator is finally over!

I love Torkoal, I set up this savannah zone in order to maybe get one for the at least the last three Safari Weeks I’ve participated in.
I was fully prepared for it to run, especially after 3 balls with no shakes. But I actually caught him!

First ever completely random shiny in SwSh, one of my favourite shinies too! Very happy, very surprised

Was hunting in great marsh for Safari Week and decided to hatch eggs at same time. This was less than 30 eggs. I wasn’t counting eggs hatching, Only safari encounters which after 1400 we still got nothing there. Looking for psyduck as main goal

I failed a first chain with like 140 or sum

Then did a second one and got it with only a chain of 28

The same thing kinda happened with mankey

Trials and tribulations. Lapras was one of the most challenging ones I’ve done recently since they take a good bit of time to hatch. I also stopped counting after 10,000 eggs lol. After finally breaking through, my next 2 (Alolan Vulpix and Bagon) were blessed by the shiny Gods n came up in less than about 200. Shoutout determination :’)