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

The best moment is usually after the game resolves the event: once a catch completes, the evolution screen finishes or a loss battle closes. Opening tools during a critical decision increases mistakes and divides attention.

Use a short verbal cue, change the team and verify the result before returning to play. The operation should be shorter than an improvised explanation.

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

An evolution is not a removal and a new catch. Use the evolution action to retain nickname, position and history. When branches exist, verify the destination; the tool should represent the player decision rather than guess it.

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