What is a Nuzlocke?

Nick Franco introduced the two original rules in his Pokémon: Hard-Mode comic about a Pokémon Ruby playthrough. The opening episode sets out the restrictions before showing the first encounters. The comic remains available on the creator’s website.

The name describes a way of playing, rather than a separate Pokémon release. A standard run does not need a modified game or a special Nuzlocke setting. The player keeps the record and follows the agreed rules even when the game would allow a revival or another catch.

The original rules restrict catches to the first wild Pokémon in each area and require releasing a Pokémon that faints. Permanently storing a fallen Pokémon in a separate box is a common alternative to releasing it; it cannot rejoin the run.

Nicknames are a widespread convention, often presented as a third rule. They were not one of the original two restrictions. Nuzlocke University also notes that nicknames are optional. A run that follows the two core rules is still a Nuzlocke without them.

This hypothetical run has no duplicate or shiny exceptions. Encounter restrictions begin when Poké Balls become available, only the first encounter in each named area may be caught, and a full party defeat ends the attempt. These are the rules for this example, not requirements for every run.

The first eligible Pokémon on one route is caught. No further Pokémon may be caught there, even on a later visit. On the next route, the first Pokémon is knocked out while being weakened for capture. Nothing can be caught there now, so the record marks the encounter as missed.

Later, a party member faints in a trainer battle. The example run treats that Pokémon as lost permanently and puts it in a memorial box. A living reserve from an earlier route can replace it. The replacement is not a new catch and does not reopen the route where it was obtained.

With unrestricted catches, a missing team role can often be filled by searching for a preferred species. In a Nuzlocke, a different Pokémon from the available roster may have to fill that role. A reserve that seemed unnecessary can become the only remaining option for a planned battle. Even if a favourite species appears on a route, it can only be caught if the encounter rules allow it.

Winning one battle can leave a team without the Pokémon planned for the next one. Looking up a major opponent, where the rules allow research, and planning a fallback reduces dependence on a single team member. Nuzlocke University’s strategy guide recommends both opponent research and backup plans.

Some players record the journey as a story; others concentrate on battle planning. The record keeps track of what happened and which Pokémon remain available for the next battle.

A familiar game makes it easier to plan around its progression and major battles. Nuzlocke University’s first-game guide also recommends considering previous experience. No single edition is the right choice for everyone.

Games with visible overworld Pokémon need a rule for choosing the encounter. The same guide discusses this issue in Sword and Shield and Scarlet and Violet. One possible rule is to randomly select an eligible species for a named area before searching for it. Another is to accept the first Pokémon that initiates a battle. These methods can produce different teams. The original rule for random grass encounters does not specify which one to use.

For any edition, write down which locations count separately. A cave with several floors should not gain extra catches just because another floor has a different species. If subareas are being treated separately, name them before the first encounter so the boundary does not change after a disappointing result.

Write the goal as a specific milestone: for example, the first Champion victory, with later content outside the attempt. Decide separately whether losing the whole active party ends the run or whether living reserves may continue it. In the second version, Pokémon in the box can keep the attempt going. Record which rule applies.

Additional restrictions can be introduced for a later attempt. Hardcore commonly adds level caps, a ban on bag items during battle and Set battle style. A ban on using storage is a separate restriction, not the definition of Hardcore. Any additional rules should also be settled before playing.

A short rule sheet can answer the situations that otherwise interrupt a run: