New to web development. I want there to be 16 players with their own boards. When they match up against each other, I'm...
Solo developers and indie hackers building browser-based autobattlers or similar multiplayer games with Node.js and SSE, who are new to web development and need a clear pattern for splitting simulation work across processes while keeping one event channel.
A Node.js package that exposes three functions: createMatch(eventId), spawnSkirmish(matchId, playerA, playerB), and streamSkirmishes(matchId). The first spawns a worker per 1v1, the second returns an SSE endpoint that multiplexes all skirmishes for that match, and the third provides an HTTP route for ability casts that forwards to the right worker. Ship with a runnable example of 16 players and one shared event channel.
No existing project in the evidence addresses this exact gap. The Reddit thread shows the developer has to design worker isolation, SSE multiplexing, and input handling from scratch. General-purpose worker pools and SSE libraries exist, but they do not combine per-match simulation isolation with a single multiplexed event channel and an ability-input bridge. This library fills that gap by packaging the three concerns together for autobattler-style games.
Platform: Node.js with Server-Sent Events (SSE) and worker processes. Hardest problem: keeping multiple isolated 1v1 simulations in sync while multiplexing them into one SSE stream and applying periodic HTTP ability inputs to the correct worker without blocking. Reusable open-source pieces: Node.js built-in worker_threads or child_process for isolation, and any standard SSE library for streaming; the evidence does not name specific packages beyond Node.js and SSE.
One-time purchase for the library source with example project, or subscription for updates and support. No prices or revenue estimates are given.
The main risk is that the pattern is simple enough that experienced developers build it themselves, limiting adoption. Another risk is that SSE multiplexing and worker isolation behave differently under load, and the library must stay small enough to audit. The evidence does not show competing projects, so the market is unproven beyond this single thread.
No project in the evidence builds this exact combination. The Reddit thread shows the developer planning to build it manually with Node.js and SSE. General worker pools and SSE libraries exist but do not address per-match simulation isolation with a shared event channel and ability inputs.
A Node.js package with three functions: spawn a worker per 1v1 skirmish, expose one SSE endpoint that multiplexes all skirmishes for a match, and provide an HTTP route that forwards ability casts to the correct worker. Include a runnable 16-player example.
Keeping multiple isolated simulations in sync while streaming them over one SSE channel and applying periodic HTTP ability inputs to the right worker without blocking the simulation. The evidence shows the developer is unsure whether the entire simulation must play out at once.
The need appears in a single Reddit thread from a developer new to web development. The problem is specific to autobattler-style games with many concurrent 1v1s, so general-purpose tools overlook it. No existing project in the evidence targets this combination.
Every quote on this page was matched against its original post on Hacker News, GitHub, DEV.to or Product Hunt, and each claim links to that thread. Unverifiable items are discarded before publication.
See all 20 evidence-backed needs this week β updated daily, every trend traced to original posts and exact quotes.
Subscribe $19.99/mo βNot sure what to build first? See the ten worth a look →