Rulesets
None of these are official rules — every one has clauses the community disagrees about. Pick yours, put them in your run notes, and the shared page will make sense to anyone who opens it.
✓ Verified vs Self-verified
Every run on RunLocke carries one of two badges. A run created here and tracked live from the start — catches, deaths and badges logged as they happen — is Verified. A run logged after it already happened is Self-verified: still counts, still welcome, just honest about being on your word. The badge is decided when the run is created and can never be changed afterwards, whichever ruleset you play. The Hall of Fame lists Verified champions first, and profiles count Verified wins separately.
Nuzlocke
A faint is a death — box it permanently. One catch per area, and nickname everything.
- Dupes clause: a species you already own doesn't count as your encounter for that area.
- Shiny clause: shinies are usually allowed as a free catch.
- Static and gift Pokémon are the classic grey area. Decide before you start.
Hardcore Nuzlocke
Nuzlocke plus level caps and no items in battle.
- Level cap is the next gym leader's ace; nothing may exceed it.
- Set battle style — no free switch when the opponent faints.
- No healing or X-items during a battle. Held items are still fine.
Soul Link
Two players run in parallel; linked Pokémon live and die together.
- Catches are linked by area order — your first catch on a route pairs with theirs.
- If one half of a pair faints, both are dead.
- If one player fails to catch on an area, that pairing is skipped for both.
Wedlocke
A Nuzlocke where Pokémon are paired and only fight alongside their partner.
- One male and one female per pair; only the active pair may battle.
- If one partner dies the other is widowed — usually boxed or re-paired.
- Gender-locked and genderless species need a house rule.
Monolocke
A Nuzlocke restricted to a single type.
- Only catches of the chosen type count as your encounter.
- Sections before your type is available usually get an HM-slave exemption.
Kaizo
A Nuzlocke of a Kaizo-difficulty hack.
- Set mode and no in-battle items are effectively part of the hack's design.
- Level caps to the next gym leader's ace are the norm.
- Expect trainers with full EVs, competitive items and real AI.
Randomizer
Encounters, trainers, moves or all three are shuffled.
- State what was randomised — species only, or moves and abilities too.
- Similar-strength randomisation is a very different run from full random.
- Dupes clause matters more here, not less.
Monotype
The whole team is a single type. Not necessarily a Nuzlocke.
- Dual types usually count if either type matches.
- HM slaves are the usual exemption.
Speedrun
Beat the game as fast as possible.
- Say whether it's any%, glitchless, or a category with its own ruleset.
- Timing method belongs in your run notes.
Casual playthrough
No restrictions — you're just logging the run.
Other
Your own rules. Write them in the run notes so the shared page makes sense.