Vibe jam: what the format rewards, and what it rules out

The vibe jam idea came with rules attached, and the rules mattered more than the theme. Entries had to be playable immediately in a browser, usually with no sign-up and no waiting, and most of the code was expected to be written by an AI rather than typed by hand.

Those rules produce a particular kind of game. Small, immediate, readable in ten seconds, cheap enough to run in a tab that a phone can handle it. That is not a criticism. It is a deliberate design of the competition, and it is why the entries were so easy to share.

Flockbay cannot enter a jam like that. It is a desktop app for Windows and Linux, its Export makes a native Windows build, and the game runs locally on the copy of Godot bundled inside it. There is no browser preview, no streaming and no hosted link. If your jam requires a URL, stop here and use a web framework.

More on this: The 2026 Cursor Vibe Jam: what the rules asked, what won, and how to prepare for the next

Strip out the browser rule and what is left of the vibe jam idea is: make something quickly, do not write the code yourself, be honest that AI wrote it. That describes plenty of jams that accept a downloadable Windows build, and it describes how Flockbay works day to day.

Flockbay builds the world and writes the GDScript inside your project. You say what you want, it asks, you approve a brief, it builds the game and plays it to check it runs, and then you play it and say whether it is right. That is the same trade the format is built on, applied to a game that runs on your own machine instead of in a tab.

The clock is the other thing a jam cares about, and the brief is where it is won. Flockbay asks one round of questions at a time, each with a recommendation, and writes down what gets built first, what comes after and what is not in this version. On a Friday night, a brief that already says what you are not making is a better place to start than an empty scene.

What is different is the ceiling, and it is worth being precise about what raises it. A browser game is limited by the tab: a download the player waits through, an object count that has to survive a phone, and a framerate you do not control. A game that runs locally is limited by your machine instead. On the 3D side that is what makes terrain, weather, water and a few hundred moving characters reasonable things to attempt. In a flat game it is the same fact from another direction: how big the world is and how much is moving in it is a question for your machine, not for a download budget.

So the honest version of the trade is not that browser games are flat and desktop games are not. It is that a tab has a budget and your own machine has a different one. A flat game built here is flat because you chose it, not because something else ran out.

More on this: What is an AI game maker?

In the browser-jam version of this, everything goes through one prompt and whatever comes back. In Flockbay the world is built from the brief you approved, with world tools, as real Godot nodes and resources. In a 3D world that means terrain sculpted and painted, water, weather and the buildings where the brief puts them.

In a flat world it means ground. Flockbay paints cells, and the tiles, the edges and the collision all fall out of which cells are ground — there is no corner piece to pick out of a palette, and painting the same cells in a different order gets you the same world. On top of that go sprites, placed at an exact position, rotation and scale, mostly out of the Catalogue Flockbay builds from: 55,073 of its 60,648 objects are sprites, and the Place tool's Asset Browser in the editor searches it by name, with a picture of each, when you want to put one down yourself.

This is the part that separates a game with a place in it from a game with a level in it. Describing a location in a paragraph and taking what comes back gets you a plausible guess. Answering questions first, then dragging the one thing that is still wrong in the Godot editor, gets you the one you had in mind.

So the split is: words for what you want, a brief before the build, and your hand for the call that is pure taste. Prompting is used where it beats clicking, and a drag is there where it beats prompting.

More on this: A no-code game maker where the code still gets written

An install. Flockbay is downloaded onto a Windows or Linux PC, so a jam judged on someone else's locked-down machine is out of reach. Do the install before the jam starts.

A connection while you build. The chat, asset generation and world data all come over the network, so building is an online activity. Playing the finished game is not.

No money. The download is free and so is the platform, so building, playing and exporting the entry cost nothing. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

More on this: What is vibe coding?

If the point is that anybody can click a link and be playing in three seconds, this is not your tool and no amount of enthusiasm changes that.

If the point is that you want to make a game quickly on free AI or your own Claude or ChatGPT plan, and the people playing it are willing to download a build, then the trade runs the other way: you get a real engine, a world built from your brief, and a game that is not limited to what a tab can render.