Buy me a coffee

NuzPoke editorial resource

An editorial kit for organising a Nuzlocke series

A Nuzlocke series is easier to follow when the rules are written down, the log is up to date and every stream starts with the same checks. This kit gathers those materials for you to adapt to your run.

Six-Pokémon Nuzlocke team in an overlay strip over a dark scene
The log keeps the run's history; the overlay only shows the current team.
Downloads

Kit files

These files are free and contain no personal data. The example rows are invented: delete them before you start.

Ruleset

Copy-ready ruleset

The ruleset follows the order of the Nuzlocke rules: core rules, conventions, areas, special cases, deaths and difficulty. Copy it from the rules template or download it as text. If you use hardcore rules, add the block from the hardcore template.

Keep a change log at the end: if a new question forces you to clarify a rule, note it with the date before you keep playing.

Log

Encounter and death log

The spreadsheet has three tabs: Encounters, Deaths and How to fill it in. The drop-down lists for Method, Result and Current status are suggestions: you can type another value.

FieldWhat to noteExample
AreaThe name used in your ruleset, always spelled the same way.Route 2
MethodHow the encounter appeared.Grass
EncounterThe first Pokémon that appeared, even if you did not catch it.Rattata
ResultCaught, Fled, Fainted before catch, Rerolled (duplicate)…Fled
Nickname and levelOnly if caught; the level is the level when caught.Spark · 5
Current statusTeam, Box, Dead or Not caught. Update it after each session.Team
Pair (Soul Link)Only in a Soul Link: your partner's linked Pokémon.Cinder (Ponyta)
Episode and notesWhere it happened and which rule you applied.Ep. 2 · duplicates clause

The Deaths tab records nickname, species, level, area caught and cause. The CSV contains encounters only; if your spreadsheet does not split the columns on opening, import it and choose the comma as separator.

The log and the overlay are different things

If you use NuzPoke, the .nzpk file only keeps access to your run on the server: it is not a copy of the team or of this log, and it cannot restore an earlier state.

Checklist

Pre-stream checklist

PRE-STREAM CHECKLIST · NUZLOCKE

THE RUN
[ ] The ruleset is published and matches the latest version.
[ ] The encounter and death log matches the saved game.
[ ] The save is where the last stream ended.
[ ] You know the next required battle and its level cap, if you use one.

CAPTURE AND SOUND
[ ] The game looks sharp, with no unexpected black bars or crops.
[ ] Game, microphone and alerts are balanced.
[ ] No private window (admin pages, passwords, email) is inside the capture.
[ ] A holding scene is ready for emergencies.

TEAM ON SCREEN
[ ] If you use a team overlay, OBS loads the view URL, not the admin URL.
[ ] Members, nicknames and order match the game.
[ ] Last episode's deaths are no longer shown.
[ ] If you also stream vertically, that output uses its own composition.
[ ] You have checked readability on a phone or a scaled-down capture.

FINAL TEST
[ ] You recorded one or two minutes and checked picture, sound and sync.
[ ] The title names the game, episode and challenge.

Go through the list before each session. The PDF version is meant to be printed and ticked by hand.

Communication

Texts for the description and chat

Adapt these texts to your ruleset and use the same link to the full ruleset in all of them. That way anyone arriving mid-stream understands why you skip a Pokémon or retire another.

TEXTS FOR EXPLAINING THE RULES ON STREAM
Adapt the [brackets] to your ruleset. Use the same link to the full ruleset everywhere.

SHORT DESCRIPTION (title, profile or social post)
[Game] Nuzlocke: one encounter per area, and every fainted Pokémon is gone for good. Rules: [link]

FULL DESCRIPTION (channel panel or video description)
This series is a Nuzlocke challenge in [game]:
- I may only catch the first Pokémon I meet in each area.
- If a Pokémon faints, it leaves the team for good.
- Every Pokémon gets a nickname.
- Clauses: [duplicates / shiny / none].
- If the whole team faints, [the run ends / I continue with the box].
Full ruleset and death log: [link]

CHAT COMMAND (for example, !rules)
Nuzlocke: first encounter per area, fainted = dead, nicknames required. Clauses: [list]. Blackout = [consequence]. Full ruleset: [link]

ANSWER TO A COMMON QUESTION (why not catch it?)
I already used this area's encounter: only the first Pokémon that appears counts. [If relevant: the duplicates clause lets me reroll because I already have that species.]

DEATH NOTICE (optional, for a pinned message or a bot)
[Nickname] ([species], level [N]) fainted against [opponent or area]. It moves to the graveyard box.

SOUL LINK (only if you play as a pair)
Linked run with [player]: Pokémon from the same area form a pair, and if one falls its partner is retired too. Shared rules: [link]
Use

How the kit fits the series

  1. Before the first episode: choose the game with this comparison, complete the ruleset and publish the texts.
  2. During each session: log encounters and deaths as they happen.
  3. At the end: update Current status and check the on-screen team matches.
  4. Before the next stream: go through the checklist.
Next resourceWhat is a Nuzlocke and how do you play one?