Skip to content

Make a first person game where the world holds up close

By Eduardo Orellana · Updated

First person is the perspective that punishes a fake world, because the player can walk up and look at everything. Flockbay builds that world and its code, walks it at eye height to check, and leaves every placement open to your hand. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.

The main page on this subject is What is an AI game maker that writes a real Godot project?.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

The camera changes what you have to get right

From above, a room is a layout. From inside it at eye height, a room is proportions, sightlines, and whether the doorway is tall enough that you do not feel like you are ducking. Players notice all of it without being able to say why.

This is the reason first person projects stall. The systems work, the world feels like a set, and there is no single bug to fix. The fix is a hundred small placements, and those are done by looking rather than by describing.

Flockbay does the first pass of those placements itself: it builds the terrain, buildings, props and light from the brief, then runs the game and captures the viewport from the player's eye height to check what it built. The rest you find by walking it. When a doorway is too low, say so, or fix it yourself in Godot's 3D view. The correction loop is seconds long, which is the only reason a hundred small placements is a realistic amount of work.

More on this: AI horror game generator: fear is a timing problem

Movement is felt, not specified

Nobody can tell you the right walk speed. They can only tell you when it is wrong. Same for acceleration, head bob, jump height, how long a crouch transition takes and whether the mouse feels heavy.

Flockbay writes the controller as GDScript in your project, and then the work is you playing it and saying it feels sluggish or floaty or too twitchy. Each pass is a sentence and a replay. You are not editing values in a file unless you want to.

Interaction sits in the same place. Picking things up, opening doors, reading a note, a torch that runs down. All code, all written for you, all judged by you playing it.

Scale is the thing that goes wrong first

Everything in a first person world is measured against the player, and most beginner worlds are slightly too big. Corridors that read fine in the editor take four seconds too long to walk. Rooms feel like halls.

The way out is not a rule of thumb, it is walking your own world early and often. Because the game runs locally on the copy of Godot bundled with the app, pressing play is quick, and quick is what makes people actually do it.

Terrain, water and a sky come from a Godot plugin or from nodes the AI writes, not features you unlock, so an outdoor first person game is as normal a project here as an indoor one.

What the app actually is

A desktop app for Windows, macOS and Linux. You download and install it. The engine underneath is Godot, which is open source, and your project is a real Godot project rather than a document only this tool can read.

Building needs an internet connection, because the chat and asset generation come over the network. Playing what you built does not need one.

Free to download. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

More on this: AI dungeon crawler maker: rooms laid out on purpose, written systems

Sound is half of first person

In first person the player cannot see behind them, which makes sound do more work than in any other perspective. Footsteps that change with the surface, a room that sounds enclosed, something audible before it is visible.

It is also the most commonly skipped part of a first person project, and the reason a technically fine world feels dead. A corridor with no footstep sound is a corridor nobody believes they are walking down.

Audio behaviour is code, so it gets written for you. Placing sound sources is part of building the world, and Flockbay can generate the sounds themselves: effects, loops and music. That is a good reason to deal with it early rather than in the last week.

More on this: Make a horror game with AI: the fear is in the level, not the code

Light does the guiding

In a first person world the player goes where it is bright. That is the most reliable tool you have for direction, and it works without a marker, an arrow or a line of dialogue.

Because a light is a placed object like any other, you can test it directly: ask for everything darker and one warm source where you want them to go, or drag the source there yourself in the editor, and walk it. If you find yourself heading there without thinking, it works.

The same tool sets mood. A room lit from one low source is a different room from the same geometry lit evenly, and swapping between the two is seconds of work rather than a redesign.

More on this: A horror game maker for people who understand pacing

Questions

Is this only for shooters?
No. Walking sims, horror, exploration and immersive sim shapes are all first person, and none of them need a weapon.
Who writes the player controller?
Flockbay, as GDScript in your project. You tune it by playing and saying what feels wrong.
Can I make a large outdoor world?
Yes. Terrain, water and weather come from Godot plugins in the Plugins panel, and running locally on your own machine is what makes that size practical.
Does it run in a browser?
No. It is a desktop app for Windows, macOS and Linux, and the game runs on your machine.

Free to download for Windows, macOS and Linux. Build it, then walk it.

Download Flockbay free