FL BulletHell Game

FL_BulletHellGame is exactly what Fill-Nodes' own README calls it: "⚠️ Placeholder stub - reserved for future bullet-hell game functionality. Currently a no-op." There's no meaningful schema to document because there's nothing there yet - zero required inputs, zero optional inputs, zero outputs. Drop it on the canvas and it does nothing: no fields to fill in, nothing to wire in or out, no error on execution because there's no logic to error in.

Why a pack ships an empty node

filliptm/Fill-Nodes is a large, actively-iterated pack - dozens of nodes spanning image processing, VFX, audio-reactive effects, PDF handling, and half a dozen AI-API integrations, plus a "Game Nodes" section that currently holds exactly this node and a sibling, FL_TetrisGame, in the same placeholder state. Shipping a reserved class name ahead of the real implementation is a normal way an author holds a spot in the node registry - and in ComfyUI's node-browser category listing - for something planned, without the name colliding with anything used later. It costs nothing to leave in a release; it's not a broken feature, it's a not-yet-started one that happens to already have a menu entry.

What to actually do with it

Nothing, for now. If you spot FL_BulletHellGame under "🏵️Fill Nodes/games" while browsing the node menu, don't spend time hunting for inputs that don't exist - there genuinely aren't any. If you were hoping for an actual playable mini-game node (some packs do ship genuinely playable browser-style toys as novelties, and the category name suggests that's the eventual intent here), the honest status is: not yet. There's no published ETA, and stub nodes in fast-moving packs can sit unimplemented for a long time or land in the very next release - there's no way to tell from outside the repository which it'll be. Watching the pack's GitHub repo directly is the only reliable way to know when that changes.

Installing the pack anyway

If you're here because ComfyUI Manager or a shared workflow flagged FL_BulletHellGame as a missing node and you just want the "missing node" warning resolved: ComfyUI Manager → search ComfyUI_Fill-Nodes → install → restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/filliptm/ComfyUI_Fill-Nodes

then restart. Installing the pack makes the node available - so a workflow that references it will load without the missing-node error - it just won't do anything when it runs, because there's nothing implemented behind it yet. If the workflow you're loading actually depends on this node doing something, that workflow was built against a future version of the pack that doesn't exist yet; there's nothing to fix on your end.