Buy me a coffee

NuzPoke editorial resource

A live workflow for Nuzlocke catches, evolutions and losses

Updating too early can distract or reveal information; updating late leaves viewers with an obsolete team. A short repeatable flow keeps game, commentary and overlay in sync.

Demonstration of team-change animations
Each change should communicate one event and then return to a calm state.
Pace

Update during a natural pause

Update the team once the game has resolved the catch, evolution or loss. Keep one admin tab active. Opening the same game in another tab disconnects the previous one so the two cannot overwrite each other.

The warning offers Carry on here to reclaim editing in that tab and disconnect the other, or Close this tab. If the browser cannot close it automatically, close it yourself. Stream views keep receiving saved changes.

Give viewers a short cue, make the change and check the result before returning to play. Saved updates reach the overlay and connected game views live.

Arrival

Introduce a catch with enough identity

Add species, variant and nickname once the game confirms them. If the nickname is undecided, wait rather than producing two immediate visual edits. Place the new member in its intended position so arrival is not followed by an unnecessary reorder.

Change

Keep continuity through evolution

Use Evolve when available to keep the nickname and position. The button appears only when at least one destination has a sprite in the active style, in the requested color or normal color. The picker applies the same availability rules to its branches.

For example, Aipom cannot offer Ambipom in the Gold style. Fan-game evolutions are not offered in HOME when their sprites are absent there. If the button is missing, check the style before assuming the species never evolves.

Choose the branch that happened in the game and confirm. NuzPoke checks the available representation; you decide whether the evolution follows your challenge rules. Let the sequence finish before making another change.

Exit

Give a removal its own narrative space

Finish the battle, explain what happened and remove the member once. Wait for that transition before reorganising the rest. Separating exit and reorder gives each movement a clear meaning.

Rehearsal

Practise one complete sequence before the series

  1. Add a nicknamed catch.
  2. Swap two positions.
  3. Edit a variant.
  4. Perform an evolution.
  5. Remove one member.

Measure the time and watch the recording rather than administration alone. Refine the flow until it can be completed without exposing private access or losing the conversation.

Next resourceWhat to check when an overlay stops updating in OBS