Independent guide based on upstream documentation reviewed October 10, 2026. Installation routes and tool capabilities below are documented by their authors; this site has not tested every agent or asset workflow.
Start with the game’s asset contract
Before generating anything, record frame dimensions, animation layout, pivot, facing direction, transparency and accepted file format. The upstream asset-pipeline guide treats the game’s drawing code as the authority. A large attractive image can still be unusable as an item sprite or animation strip.
Use one small original placeholder in the first build. Inspect it in the game next to existing content, checking scale and orientation. Once that works, replace the placeholder through the same repeatable conversion steps instead of asking for an entire polished asset pack at once.
fal: an optional hosted generation route
The upstream fal tools cover images and sprites as well as selected 3D, audio and video tasks. Calls can use its MCP integration or um fal. A provider key is required, and current model prices and inputs should be checked before a batch. Keep keys outside mod files and do not publish them with a release.
For downloaded results, the upstream CLI records generation details in a manifest. Save the inputs, model, seed where supported and output filenames so you can trace what produced an asset. A provider result still needs local conversion and an in-game check; generation alone does not make it ready for the loader.
ComfyUI: local images with a separate setup
At the reviewed commit, um comfy connects to a running ComfyUI server, using localhost port 8188 by default. um comfy status checks the server and available checkpoints. The image helper supports a basic text-to-image graph; more complex setups can use an API-exported workflow with um comfy run.
This route does not need a fal API key. It does need ComfyUI, appropriate model files and a machine that can run your selected workflow. Consult ComfyUI’s requirements rather than assuming a fixed GPU minimum. Local processing uses your hardware, storage and time; it is not a promise of zero cost or identical output. The upstream integration does not supply equivalent audio, 3D and video recipes.
Convert one asset, then test it
- Inspect dimensions and transparency before cutting out a flat background. Keep originals so you can redo the conversion.
- Fit pixel art once to the target frame using nearest-neighbor scaling, then check edges, pivot and empty padding.
- Build sheets or strips with the exact expected frame count and layout. Check the first and last frames in the game.
- For 3D-to-sprite work, use the documented Blender rendering route and inspect camera angle and facing before rendering every direction.
Keep source and distribution records
Record which art is original, generated or used under a separate license. Do not ship extracted game assets merely because you inspected them locally. Keep a short acceptance record: expected file format, actual dimensions, observed game behavior and changes made. With one asset passing these checks, you can expand the set without confusing image quality with mod correctness.
A starter prompt for your agent
List the exact asset requirements for my first mod item: size, frame layout, facing, pivot, transparency and format. Use an original placeholder first. Compare optional fal generation with my local ComfyUI setup without making paid calls. Propose a repeatable conversion recipe and one in-game check. Keep source records and credentials separate, and do not package extracted game assets.