I built a live Twitch overlay for Pokémon Soul Links & Nuzlockes
▲ 4 r/PokemonDe+2 crossposts

I built a live Twitch overlay for Pokémon Soul Links & Nuzlockes

Hey everyone,

I've been working on a new feature for Soullinks.app: a Twitch overlay for Pokémon Nuzlocke and Soul Link runs.

The goal was to make Soul Links easier to follow for both streamers and viewers without having to manually maintain overlay graphics during a run.

Features:

  • Automatic Soul Link visualization
  • Team, Box and Graveyard support
  • Browser source for OBS / Streamlabs
  • Shareable run links for you and your partner
  • Shareable links for your viewer to get all informations
  • One player updates the run, and the changes are instantly visible on all players' streams
  • Built-in badge tracking and level caps
  • Direct integration with runs managed on Soullinks.app

You can see it here:
https://soullinks.app/de/pokemon-nuzlocke-twitch-overlay

I'm looking for feedback from Nuzlocke players, Soul Link creators and Twitch streamers:

  • What information do you want visible on stream?
  • What annoys you about current overlay solutions?
  • What features would make Soul Links easier to follow for viewers?

Would love to hear your thoughts and ideas.

u/Darius_die — 13 hours ago

I’m building a web app on Cloudflare Workers and I’m struggling a bit with the architecture.

Requirements are pretty mixed:

  • Public pages → should be SEO-friendly and statically generated (SSG)
  • App part → fully dynamic with authentication
  • Real-time features → WebSockets required
  • Database → D1 (Cloudflare)
  • Runtime → Cloudflare Workers

So basically: hybrid app with marketing pages + real app in one project.

Right now I’m considering two approaches:

Option 1: React (with tanstackrouter) + Hono

  • Full control over routing and APIs
  • Easy to integrate WebSockets (e.g. via Durable Objects)
  • But I’d have to build SSG / SEO handling myself

Option 2: TanStackStart

  • Better structure for routing + data fetching
  • Potential for SSG / SSR hybrid
  • But unclear how well it plays with Workers + WebSockets + D1 in real production setups

What I care about:

  • Clean separation between static (CDN cached) and dynamic routes
  • No unnecessary Worker invocations for static pages
  • Good DX without fighting the platform
  • WebSocket support without hacks

What I don’t want:

  • Next.js/OpenNext style setup where everything goes through the Worker anyway

Has anyone built something similar on Cloudflare Workers?

  • How did you structure SSG vs dynamic routes?
  • Did you split into multiple deployments (static + app)?
  • Any real-world experience with TanStack Start on Workers?
  • Or is Hono + custom setup just the more realistic approach here?

Would appreciate honest opinions, especially from people who actually run this in production.

Note: Yes, I used AI to help write the post — my English isn’t strong enough to express everything clearly on my own.

reddit.com
u/Darius_die — 4 months ago