SpriteFactory

• 

  GUI-2

• 

  Output-1

• 

  GUI-1

Inspiration

The hardest part of putting a game together is the art, because it's more than something you can just generate. Often, it's the interplay between gameplay and game art that gives a game its entire feel: the world is consistent, the motion reads instantly, and every tiny effect reinforces the fantasy. This is especially true in games that use sprite-based animations. A nanobanana png can't jump after all, so if you want all the supporting frames and variations (idle, run, hit, cast, directional, palette swaps, armor tiers) you end up needing an artist friend after all.

Until now.

SpriteFactory is my answer to that friction: a pipeline that automatically fills in all the different possible transitions that make sprite development so painful.

What it does

SpriteFactory is an end-to-end sprite-generation pipeline that generates static art direction, then expands that into a node graph of assets, with a rendered video for every edge in that graph.

At a high level:

• It generates a node graph

  • Each node is an asset specification: a character pose sheet, a weapon variant, a VFX burst, anything that can be either provided as a image or generated from a prompt

• Edges are transformations

  • “Base character → armored character”
  • “Neutral stance → wind-up”
  • “Wind-up → slash impact”
  • “Fire palette → ice palette”
  • “Day lighting → dungeon lighting”

• Every edge becomes a rendered video

  • Instead of hoping the transformation “works,” SpriteFactory renders a short video that shows the change across frames (or time), so you can instantly see:
  • does the silhouette read?
  • does the motion feel snappy?
  • are materials consistent?
  • is the style drifting?
  • Those videos are then down-sampled, either manually, with CLIP, or with fixed timings to preserve the animated feel.

The result: you don’t just get sprites—you get a map of your art system, plus demo sprites ready to use.

• Sprites aren’t files; they’re relationships. Most production pain isn’t “drawing the run cycle,” it’s keeping the run cycle consistent with the idle, the hit reaction, the weapon swap, the biome lighting, and the VFX layer.

• Previews are a superpower. Rendering a video for every edge lets developers understand the whole feel of the game in a single swoop, and at every stage of

• A state machine is already used to keep track of avatars. Using a state machine ensures compatibility with the state of the art in the industry.

• Iteration speed changes the kind of game you can make. When adding a “poison variant” is cheap—because it’s just a palette + VFX edge—you start designing more expressive systems.

What’s next for SpriteFactory

• Interactive graph UI

  • Click a node to inspect layers, masks, metadata, and exports.
  • Click an edge to instantly play the generated preview video and compare against previous builds.

• Style locks + drift detection

  • Define “style invariants” (line width ranges, palette families, silhouette constraints).
  • Automatically detect when new assets drift away from the project’s visual identity.

• Gameplay-ready export packs

  • Auto-export in engine-friendly formats (atlases, JSON metadata, named clips, directional sets).
  • Edge videos become optional “transition animations” for state machines.

• Multi-character consistency

  • Shared constraints across a roster so NPCs, enemies, and the hero all feel like they belong in the same world.

SpriteFactory is ultimately about letting game designers and artists stay in the creative flow—making choices at the level of systems and style—while the pipeline does what pipelines should do: produce consistent, inspectable, shippable assets at speed.

Built With

• hailuo
• nanobanana
• python
• react