What VPlay AI actually does when you describe a game

2026-10-01

"Describe a game and get a playable prototype" sounds like it should mean an AI writing and running arbitrary code on your behalf. That's not what happens, and the actual mechanism is more interesting than that would be — it's closer to a very capable form-filler than a code generator, and that's a deliberate constraint, not a limitation we're apologizing for.

The model never writes code

When a real AI model is available, your description goes to it and comes back as structured data, not a script: a gameplay template (one of a fixed handful — think space-shooter, platformer, endless-runner, racer, clicker, puzzle, top-down-shooter), a sprite choice from a fixed set, a palette, and a batch of numeric tuning values like speed or difficulty. Every one of those fields gets clamped and validated after the model answers — colors have to be real hex values, numbers get pinned inside sane min/max ranges, any text labels get stripped of characters that could do anything funny in a browser. The model can rearrange the knobs and pick from the menu; it can't hand back something that isn't on the menu, and nothing it returns is ever executed as code. That's also what "safe" means here specifically — not a content filter bolted on top, but a response shape that structurally can't be anything other than data.

No model available? It still works

If the AI backend isn't reachable — rate-limited, timed out, whatever — generation doesn't just fail. It falls back to an offline matcher that reads your description for keywords and picks the closest template itself, and the page tells you plainly when that's what happened rather than pretending a real model made the call. It's a lower-effort result, but it's a real fallback, not a silent error.

What happens after it boots

The generated config gets handed to a sandboxed player — an iframe with scripting allowed but no access back out to the rest of the site — and only once that player actually confirms it booted does a "Save your game" option appear. You can keep talking to refine it; follow-up messages patch the existing config rather than starting over. Saving keeps it as your own project. If you want other people to actually play it, that's a separate step — submitting it sends it into a real review queue, and it only becomes publicly playable under your name once that review clears. Nothing you generate is quietly public by default.

A concrete run-through

Type "a fast neon runner where you dodge lasers," and the response comes back as an endless-runner template with a runner sprite, a dark-and-neon palette, and speed/ difficulty numbers nudged up from their defaults — not a hand-written runner game, a specific configuration of one. It boots in the sandbox, you tweak the palette in chat, save it, and if you submit it for review and it's approved, it shows up as your own published game, earning you a small VCoin reward the first time someone plays it through. Skip the submit step, and it just stays yours — still playable by you, never listed for anyone else.