Vibe coding a game jam entry in a weekend

Do this before anything else, because it can decide whether this tool is usable for your jam at all. Many jams require a browser-playable build at a URL so judges can try entries without installing anything. Stage Engine builds a game that runs locally on the copy of Godot bundled with the app, on Mac or Windows. If the rules say web-playable, that is a hard mismatch and you should pick a different tool rather than find out on submission night.

Jams that accept a downloadable PC or Mac build are a straightforward fit. So are jams judged from a video, and internal or informal jams with no distribution rule at all.

The other rule worth reading is the one about AI. Some jams require disclosure, some cap how much of the entry can be generated, and a few ban it. Director 1 writes the GDScript in your project, so you are within scope of any of those rules and you should know which one applies.

The jam entries that finish are the ones with one mechanic and one place. Not one mechanic and a world — one mechanic and a place you could describe in a sentence: a flooded quarry, a single street at night, one long staircase.

That shape suits how this tool divides the work. The place is the part you build by hand, and hand-building one strong location in a few hours is realistic. Building three is not.

Spend the first block on the world, not on behaviour. Terrain, water, weather, the buildings, where the light falls. Once the place exists you can feel what the game should be in it, which is faster than deciding in the abstract and then trying to build a world that agrees with you.

Give Director 1 one change, then play it. The temptation under time pressure is to fire off five requests and wait, and it reliably costs you more time than it saves, because when something is wrong you now have five candidates for why.

Be specific in the way you would be with a person. "Enemies should stop chasing once I am two rooms away, then go back to patrolling" is workable. "Make the AI better" is a request for a guess.

The game runs locally when you press play, so testing costs you nothing but the seconds. Under jam pressure that is the difference-maker: play constantly, and let the build tell you what to do next rather than the plan you wrote at hour one.

Ordinary jam advice, and it holds here. The last block goes on the beginning of the game, the readability of the goal, and the one bug that will make a judge quit. Not on a new mechanic.

Build early, not at the end. Make a build at the halfway point and run it, so that packaging is a known quantity rather than a discovery you make at 2am.

Write your AI disclosure while you still have your notes. If the jam asks what was generated, "Director 1 wrote the GDScript; the world was built by hand in the editor" is an accurate and easy sentence to give them.

Stage Engine is a desktop app for Mac and Windows and it has to be installed. Do that before the jam starts, along with making a throwaway project, so that hour one is not setup.

You need an internet connection to build. Director 1, asset generation and world data all come over the network. Playing what you have already built does not need one, but a jam without connectivity is not a jam you can do here.

The free plan exists and is a fine way to try the loop. Indie is $10 a month and Pro is $50, and what they buy is more usage — useful over a jam weekend precisely because a jam is the densest few days of requests you will ever make.