Plugins
5 sets, 19 plugins.
Free on your own hardware. Open where it counts.
What this exists to solve
The assets that make a design playable — the reach for the panel, the spoken line, the face that carries it — are the expensive part of an early game. So designs queue behind asset production, and the answers arrive after the money is spent. These sets make the playable version cheap enough to throw away: generate it, play it, keep what earns its place.
They also repair a divided landscape. Every generative model arrives with its own format, its own workflow and its own failure modes, and none of it is built to be automated. Here, providers plug into one registry and are chosen per asset — free and local, rented, or hosted — every step is priced before it commits, and the whole surface is native Model Context Protocol, so your agents run the same pipeline you do.
And they keep generated content from quietly becoming debt. Every asset is ledgered from the moment it is made — what produced it, what it cost, what depends on it — and the moment your team hand-edits one, it graduates and the tooling never touches it again. Generation is for finding the game; graduation is how you keep it.
The sets
Pipelines you can leave running.
The umbrella the other sets plug into: wire any of them into one pipeline, leave it running for hours, and trust the result — it skips what is done, prices what is not, and stops where you would want to be asked.
4 plugins
Animation at the speed of the idea.
The move you just described, playing on your own character in seconds — generated on your GPU, a rented card, or a hosted provider, and imported as an ordinary AnimSequence.
6 plugins
Every line in the game, spoken.
A voiced scene for cents — every line generated with character-level timing attached, priced before you commit, and cached so an unchanged script never pays twice.
2 plugins
The face that goes with the voice.
Spoken audio becomes a performing face — solved locally on CPU for nothing or on NVIDIA Audio2Face-3D, with emotion you set or emotion read out of the delivery, retargeted into the vocabulary your rig actually reads, and baked ready to play.
5 plugins
From clip to gameplay, without the busywork.
A clip becomes something an ability can play: the montage built from a recipe, notifies exactly where you authored them, and hand-tuning that survives every rebuild.
2 plugins
Each set ships its capability and, separately, a toolset that exposes it to an agent and holds no logic of its own — delete the toolset and the capability behaves identically. Any of them can be run by hand, or wired into a pipeline that runs them for hours without a person watching.
Find your work
Nobody arrives shopping for a set name. Start from the work you do, and take the shortest route to playing it.
Ten readings of an interaction verb before lunch, on your own skeleton, and recipes that rebuild without eating your hand-tuning.
The scene voiced, faced and paced end to end — heard today, not re-keyed by a technical artist next sprint.
One pipeline over all of it — costed, cached, resumable, agent-drivable — and utilities for the unglamorous problems in between.
Every asset accounted for — what it cost, who approved it, where it landed — and a brief your vendors can record against.
Coming
The same spine — providers pluggable, everything ledgered, agents first-class — extended to the rest of what a playable design needs.
3D generation, on the same spine.
Props, set dressing and staging geometry from a description — generated into the project, iterated as the layout changes, and swapped for the final asset as a reference change the game never notices.
Images and textures, in the pipeline.
Concept boards, placeholder UI and textures on the same provider registry and the same pipelines — generated against the project’s art direction rather than one prompt at a time.
The creative direction layer.
One versioned style source — palettes, references, rules — that every other Forge generates against, so a thousand generated assets read as one game instead of a thousand prompts.
A different thing
Nothing on this page knows what a quest is, or a dialogue node, or an inventory slot. That is deliberate — it is what lets the same plugin serve a project that shares nothing with ours.
The binding lives in add-ons — ready-made bridges into the framework you already use, filtered by framework and by what they do, so a new framework adds a filter rather than a page. And the same conventions are yours to build on, so your own bridge is an ordinary plugin away.