Volt01Start playable
A blank canvas is the wrong start for a slot. Every game in Volt begins as one that spins, pays and passes, and stays that way while you change it.
Slots deserve a real engine
Every other kind of game has an editor you can open and play in. Slots are still built across a math script, a front-end repo, an art folder and a spreadsheet of timings, held together by whoever remembers how. Volt is the editor slots never had.
Four rules we build by
02The preview is the game
If the editor shows something players won't see, it's lying. Build plays your game's own front end on its own math, every time.
03Feel before art
Players feel a slot's timing before they notice its art. Timing, motion and math get the same care as pixels.
04Ship without guessing
Requirements you can read can be checked. If Engine would reject a game, Volt should tell you first, and say what to fix.
05Quiet by default
Panels show the few settings people change. The rest is a section's + or a workspace you open on purpose.
06An agent beside you
It edits the same game you do, through the same values, and every change it makes is one undo.
A calm editor with an engine underneath
Volt looks and works like a modern design tool: workspaces that each do one job, panels that stay quiet, a game window instead of a canvas you drag things around on. Underneath it behaves like a game engine: play, pause, step, overrides on a template, an asset set for every game.
- Slotted, not dragged. Everything in the game has a slot and a place it goes.
- One job per workspace. Studio, Build, Math and Ship, switched from one menu.
- Plain words first. "How often it pays" before "hit rate".
Laser Bear's symbols: our own game, in Volt.
A small beta, on purpose
We're letting studios in a few at a time so we can watch real games get made, fix what slows them down, and decide what comes next from what they need, not what we guess.