Flockbay is not a VR game maker

Flockbay is a desktop app for Windows. You build a world by hand, Flockbay writes the code, and the game runs locally on the copy of Godot that ships inside the app, on a monitor. There is no headset preview, no controller mapping, no comfort or locomotion tooling, and nothing in the builder assumes a stereo camera.

A VR game is not a normal game with a different output. Locomotion, scale, hand presence, frame budget, motion sickness — those are the design problems, and a tool that does not think about them is not going to accidentally solve them for you.

So: if the headset is the point, use Unity or Unreal, or Godot directly with its XR support and the community toolkits that exist for it. Those are real answers and you deserve one rather than a page that hedges.

What Flockbay produces is a real Godot project on your disk, not a sealed file format. Godot itself is an open source engine with an XR story of its own. Somebody with the relevant skills could open a project made here and take it in a direction Flockbay does not support.

That is worth knowing and it is not a plan. Nothing in the builder, in Flockbay, or in the way a project is set up is aimed at VR, so treating that as a path is treating an open door as a road. If you need VR, start where VR is supported.

We would rather say that clearly than sell you a maybe. Never inventing a capability is worth more to you than a page that ranks.

Games on a monitor, on a Windows PC, 2D or 3D. You pick which when you create the project — two pictures, no default, nothing created until you choose — and both are the same app, the same builder and the same chat.

In 3D that means worlds with terrain, water, weather and a few hundred moving characters, the kind of thing that needs to run locally to be pleasant, which is exactly why the game runs on your machine rather than streaming from somewhere. In 2D it means ground you lay by dragging, with the tiles, the edges and the collision falling out of which cells are ground, a band of scenery behind it, and sprites placed at an exact position, turn and size.

Either way the work splits in two. You build the world with your hands in a builder that behaves like a level editor. Flockbay writes the GDScript for behaviour, inside your project, and you judge it by playing it.

That division is the whole design. Describing a hillside in a sentence is slower and worse than dragging it, and so is describing which cells are ground. Describing a rule is faster than writing four hundred lines. Each half goes where it belongs.

Some people searching for a VR game maker actually want an immersive world and assume a headset is the only way to get one. If what you want is a place that feels real to move through — light changing, weather arriving, somewhere that rewards looking around — a flat-screen game does that too, and it is a far shorter road.

Building that world by hand is the part Flockbay takes seriously. It is also the part that transfers if you later go to a VR-capable engine: knowing how to compose a space is not platform-specific knowledge.

The rest is the usual facts. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Building needs an internet connection because Flockbay, generation and world data come over the network. Playing what you built does not.

Decide what the headset is doing for your game. If the answer is presence — hand, scale, the feeling of standing somewhere — that is a design goal you cannot approximate on a monitor and you should go where the tooling is. If the answer is closer to "VR seemed like the modern way to do this", the flat-screen version of your idea is a much shorter project and a better first one.

It is also worth knowing that VR magnifies every mistake. A frame rate dip that is mildly annoying on a monitor makes people take the headset off. That is not a reason to avoid it, but it is a reason not to make it your first game while also learning everything else.

Whatever you choose, choose it before you build the world rather than after. Retrofitting a flat-screen game into VR is a rebuild, not a setting.