Skip to content

Building a farming game, which is mostly a calendar problem

By Eduardo Orellana · Updated

Farming games look like they are about crops. They are really about time: a day that ends, a season that turns, and a small set of choices you regret in the right way. Here is how that gets built. 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 systems under a farming game

Strip the genre back and there are four things. A clock that advances and cannot be rewound. A grid of soil with state on it, wet or dry, planted or empty, ready or not. An inventory and an economy that turns the harvest into money and money into more capacity. And people, who are there on a schedule and who react to you.

None of those are hard individually. What makes the genre demanding is that they all touch each other. Watering matters because the day ends. The day ending matters because the season ends. The season matters because the villager you wanted to give a gift to has a birthday in it.

That interlocking is exactly the kind of thing that is tedious to program and easy to describe, which is why handing it to Flockbay works well here.

What you tell Flockbay

You describe the rules, and they go into a brief you approve before anything is built. Crops grow one stage a day if they were watered. Rain waters everything for you. Sleeping past two in the morning costs you the next morning. Tools upgrade at the smith and the upgrade changes how many tiles you cover in a swing.

Flockbay writes that as GDScript inside your project. The day cycle, the crop state machine, the save file, the shop, the gift preferences of each villager. It is real code in a real Godot project, so the systems can be as specific as your design is rather than as specific as a template allowed.

Then you play a week of in-game time and find out that watering thirty tiles is boring, or that money comes too fast. That verdict is yours to make and it is the actual design work. You say what is wrong and Flockbay revises.

The top-down farm is a 2D project, and the brief says so before anything exists

Stardew Valley, which ConcernedApe shipped in 2016, is drawn from above on a grid, and so is most of the genre it revived. In Flockbay, 2D or 3D is settled in the brief, with a recommendation and no default, before anything is built. For that farm, the answer is 2D.

Then the land is painted rather than placed. Ground is a TileMapLayer: Flockbay paints the cells, and the TileSet terrains decide which picture lands in each cell, where the edges and outside corners fall, and what the character walks into. A grid of soil with state on it is the genre's central object, so this is about as direct as world-building gets, and Godot's TileMap panel is there when you want to widen a field yourself. The same layer gives you a dirt path you cross as readily as the field beside it.

The village and the people in it are sprites at an exact position, rotation and scale, placed by Flockbay and movable in Godot's 2D view. With each sprite's origin at its base and Y-sort on, the barn stands on the ground instead of hovering by however much empty margin its file carries, and a villager walking below the porch passes in front of it. Most of what a valley needs is already in the library: 55,073 of its 60,648 objects are sprites.

Pick 3D instead and this is one of the few genres with real use for all of it. Flockbay places the farmhouse, the barn and the river where the brief says, on a terrain from a Godot plugin, and sets up the sky, the weather and the time of day as part of the scene rather than something bolted on, which matters when your seasons are supposed to feel unlike one another. That is the reason to take the extra work if you want to stand in the valley rather than look down at it.

Either way you decide how long the walk into town is. That walk length is a design decision disguised as geography, and it is one of the most important numbers in the genre. You find it by walking it, and when the fix is moving the town forty metres, describing it is the slow way: Godot's own editor is right there, so you drag it there, and Godot's undo takes it back.

More on this: The best games like Stardew Valley to play in 2026

Why it runs locally

Flockbay is a desktop app for Windows, macOS and Linux that ships with Godot. Your game runs on your machine when you press play. That matters for this genre specifically, because a farming game accumulates: crops, animals, villagers on schedules, weather, a save file that grows all year. A browser tab is the wrong place for that and browser tools quietly keep your scenes small so it never shows.

Building needs an internet connection, since Flockbay and asset generation come over the network. Playing what you have built does not.

A sensible first target

One field, one crop, one day. Plant, water, sleep, wake up, see it grown. If that loop is satisfying with a single crop it will be satisfying with twenty, and if it is not, adding twenty crops will not save it.

Then add the thing that makes yours different. Every farming game has soil. Yours needs one reason to exist, and the sooner it is in the build the sooner you know whether it works.

More on this: How to write a Steam short description

The villagers are the hard part

Crops are arithmetic. People are not. What makes the best games in this genre stick is that the village feels inhabited: someone is at the shop in the morning and at the bar in the evening, they notice the season, and they remember you turned up with the wrong gift.

That is a scheduling system with memory attached, and it is exactly the kind of thing that is miserable to write and easy to describe. You say who goes where and when, what they care about, and what changes after you do something they mind. Flockbay writes it.

Then you play a month of in-game time and see whether the place feels alive or merely populated. Only playing tells you that, and it is your call to make.

A starting project for this is the simulation game templates.

Questions

Can I make a 3D farming game or does it have to be top-down?
Either, and the brief settles which before anything is built. Top-down is a 2D project: a TileMapLayer, sprites, and no gravity, so the character steers on both axes instead of jumping. A 3D valley gets terrain, water and weather from Godot plugins, and a time of day, instead. Same app, the same chat, an ordinary Godot project at the end of either.
Do I need to code the day and season system?
No. You describe how time should work and Flockbay writes the GDScript for it into your project.
Are there farming templates to start from?
No farming template ships. You describe your rules and get code that does what you actually asked for.
Is it a browser tool?
No. It is a desktop app for Windows, macOS and Linux, and the game runs locally on the bundled Godot.
What does it cost?
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.

Free for Windows, macOS and Linux. Describe the seasons, then walk the valley.

Download Flockbay free