NuzPoke tips and tricks

The five-minute checklist

• Open the run from the saved admin link.
• Check trainer, style and all six slots.
• Open OBS and confirm the source is visible.
• Make a reversible change—such as moving two members—and check it arrives.
• Review the overlay over a bright and dark part of the game.
• Restore the final order and start the broadcast.

Four recipes that work

Use one recipe as a starting point and change one variable at a time. It becomes easier to see what truly improves the scene.

Test the worst background, not the best

Check a bright area, a dark area and a highly detailed area. If the team disappears:

1. Add a medium-opacity fill.
2. Increase name color contrast.
3. Reduce decorative pattern opacity.
4. Increase spacing slightly.
5. Hide types or names before shrinking sprites too far.

Viewers glance at overlays on screens of many sizes. Prioritize clear silhouettes and short text.

Protect admin access and backups

Reduce work before sacrificing quality

1. Reuse one Browser Source across scenes.
2. Use 30 FPS unless extremely smooth motion is important.
3. Fit the source width and height to the area the overlay occupies.
4. Disable repeating entrances when they add no value.
5. Turn off Animate sprites or use static HOME for minimum load.
6. Avoid duplicate hidden sources in the same scene collection.

Test while recording and with the game under load. Performance problems rarely appear in an empty scene.

Turn changes into moments in the run

Update the team when viewers can look: after a catch, on returning from battle or during a break. Motion works best when it supports narration instead of competing with it.

• Remove the lost member first, then introduce the replacement.
• Keep a stable order: active first, catch order or narrative importance.
• Use a transition scene for several variant changes.
• After an evolution, let the sequence finish before another change.
• If something fails, do not rebuild the source: open the URL in a browser and refresh OBS cache once.

Keep the run ready throughout the series

A reliable setup needs small periodic checks, especially after updating OBS, changing computers or redesigning scenes.

1. Keep a recent .nzpk file away from the streaming computer.
2. Check OBS still uses the view URL rather than a captured browser tab.
3. Inspect the overlay after changing resolution, system scaling or output canvas.
4. Remove duplicate sources left hidden in old scenes.
5. Test one addition and one removal after major style changes.
6. Write down the visual recipe so it can be rebuilt quickly.