A ranch game where the horses matter
Most farming games treat a horse as a faster way to cross the map. In Potato Run every horse is a persistent individual with its own genetics, training history, temperament and condition. How it performs over a fence depends on all of those plus how well you ride it. No horse is good at everything.
Riding that feels good
Four gaits, momentum and turning radius, and handling that changes horse to horse. This has to be fun before anything else gets built.
Skill-based jumping
Approach, rhythm, takeoff distance and timing decide whether a fence goes clean, a rail comes down, or the horse says no.
Horses as individuals
Genetic potential and trained ability are separate. Breeding builds bloodlines over generations.
Design your own courses
Build arenas, place fences, set heights, number the course, save it and ride it against the clock.
A living ranch and town
Farming, seasons, weather, day and night, village neighbors, festivals and shows.
Family friendly
Readable controls for kids 9 and up. Outdoor adventure instead of combat. Light, age-appropriate stories.
Originality rule: inspired by the cozy feel of games like Stardew Valley, but every character, piece of art and asset is original. Nothing is copied from any existing game.
The world around the ranch
The player inherits a run-down horse ranch outside Potato Run, a small rural village. The world has seasons, weather, a day and night cycle, and progress that persists.
Homestead
Farmhouse, stables, paddocks, garden and workshop.
Equestrian grounds
Outdoor arenas, riding trails and training facilities.
Village
Shops, the vet, the farrier, neighbors’ homes and festivals.
Forest
Riding trails, archery, camping, fishing and places to find.
Fairgrounds
Horse shows, racing and competitions.
Visual direction
Warm, natural colors and cozy, detailed top-down pixel art. Distinct seasons, readable horse animations, pixel-perfect scaling where practical.
Horse simulation
Each horse has four layers of data. Genetics set the ceiling, training moves a horse toward it, condition changes day to day, and identity carries the history.
| Layer | Attributes | Changes how |
|---|---|---|
| Identity | Name, age, sex, breed, coat, markings, pedigree, breeding history, ownership, competition record | Set at birth or purchase; record grows over time |
| Genetic | Speed, acceleration, stamina, strength, jumping scope, jumping technique potential, agility, conformation, temperament, trainability | Fixed for life; passed to foals with variation |
| Developed | Jumping skill, flatwork, responsiveness, fitness, confidence, discipline specialization, rider bond | Training and riding, capped by genetics |
| Condition | Energy, health, stress, happiness, fatigue | Day to day: work, rest, feed, care |
Riding
Top-down, eight-direction control. Walk, trot, canter and gallop, with acceleration, deceleration, momentum and a turning radius that tightens or widens with gait. Each horse handles a little differently.
| Key | Action |
|---|---|
| W A S D or arrows | Steer |
| Shift | Change gait |
| Space | Jump |
| E | Mount or dismount |
Hunter / jumper
Jumping is interactive. Every fence is judged on what the rider did and what the horse is capable of.
What each fence evaluates
- Approach angle
- Speed and rhythm
- Takeoff distance and player timing
- Horse scope, technique and confidence
- Fence height and width
- Landing and recovery
What can happen
- Clean jump
- Knocked rail
- Refusal
- Runout
- Poor landing
Judged on rhythm, smoothness, consistency and overall quality of the round.
Judged on faults, clear rounds, time and jump-offs.
Competition rules are configuration, not code, so new classes can be added without rewriting the scoring.
Course builder
Players build their own outdoor arenas and design hunter and jumper courses. Courses are stored as structured data, not hand-built scenes.
- Enter and exit build mode
- Place, remove and rotate fences
- Set fence heights
- Vertical, crossrail and oxer
- Numbered course order
- Save, load and ride a course
- Time and faults recorded
- Combinations and related distances
- Decorative fillers
- Terrain and footing
- Course difficulty rating
- Hunter course design
- Cross-country fences
- Multiple arena sizes
Breeding
The long game. Pick a sire and dam, keep pedigrees, and raise foals that inherit traits with some variation. Coat color follows simplified inheritance rules. Foals get their own look and temperament, then have to be raised and trained. Over several generations a player can build a bloodline that suits one discipline.
Design rule: inheritance is probabilistic with adjustable parameters. It should feel believable, not be a genetics textbook.
Ranch, outdoors and town
Farming and ranch
- Seasonal crops: plant, water, harvest
- Farm animals
- Build and upgrade structures
- Stables, paddocks and feed
- Sell goods; earn from training and shows
Outdoor adventure
- Archery practice and competitions
- Trail riding and exploration
- Camping and fishing
- Hidden places and treasure maps
- Foraging and seasonal finds
No combat at the center of the game.
Neighbors
- Villagers with daily schedules
- Dialogue and friendship
- Gifts, quests and festivals
- Light, age-appropriate romance
- Optional marriage between adult characters
Four phases, riding first
- Phase 1 · next
First playable riding prototype
One small outdoor arena, one rider, one horse, one adjustable fence. Mount and dismount, four gaits, eight-direction movement with momentum, simple jump timing and clearance, and clear feedback for clean jumps and knocked rails.
- Phase 2
Equestrian gameplay
Several horses with different attributes, more fence types and heights, course-building mode, numbered courses, faults and timing, basic jumper competitions, save and load.
- Phase 3
Horse depth
Training and progression, temperament, fitness and condition, breeding and genetics, pedigrees, foals, buying and selling horses.
- Phase 4
Living world
Expandable homestead, farming, the village and its people, relationships, archery, camping, forest exploration, seasons and festivals.
The first arena
Phase 1 is done when
- The game launches natively on a Mac.
- The player can mount the horse and ride.
- Riding feels clearly different from walking.
- The player can approach and jump the fence.
- Jumps produce outcomes a player understands: clean, or a knocked rail.
- Nothing blocks play, and the player can immediately try again.
Jump rules start simple. Phase 1 uses deterministic rules so results are predictable while the feel is tuned. The model leaves room for genetics, training and rider skill to feed in later.
Out of scope for Phase 1: inventory, farming, breeding, NPCs and world maps.
Stack
| Area | Choice |
|---|---|
| Platform | macOS native, Apple Silicon |
| Engine | Godot 4.x |
| Language | GDScript |
| Graphics | 2D top-down pixel art; 640 × 360 internal resolution scaled to the window |
| Mode | Single-player, offline to start |
| Art | Consistent placeholder pixel art, swapped for final art later |
| Development | AI coding agents (Claude Code, Cursor) with me as creative director and architect |
| Version control | Git |
Instructions for the AI coding agents
- Working, playable features before infrastructure.
- Never build a custom engine or an unneeded framework.
- Use Godot’s own scenes, nodes, resources and signals.
- Keep systems modular and data-driven.
- Work in small, testable steps.
- Leave the project runnable after every feature.
- Run Godot’s headless validation when it’s available.
- Use placeholder art instead of waiting on final art.
- No new dependencies without a reason.
- Don’t build future features early.
- Write down architectural decisions that matter.
- Keep controls and play accessible to kids 9 and up.
Planned project structure
Folders are created only when something needs them.
potato-run/ ├── PROJECT.md ├── project.godot ├── scenes/ world · horses · arenas · obstacles · ui ├── scripts/ player · horses · riding · jumping · courses · systems ├── resources/ horses · obstacles · courses ├── assets/ sprites · tilesets · animations · audio ├── tests/ └── docs/
Open questions
Riding feel
HighEverything rests on the horse being fun to ride. Gait speeds, acceleration and turning will need many rounds of play-testing, not one pass.
Jump readability
HighA kid has to understand why a rail came down. Feedback on distance and timing needs to be obvious without reading numbers.
Top-down jumping
MedA straight-down camera hides height. The arc, shadow and landing need to sell the jump in 2D.
Art pipeline
MedPlaceholder art keeps things moving, but the eventual style, tile size and horse animation set need deciding before Phase 2 content grows.
Scope
MedEight systems is a lot. The phase gates exist to keep each one from starting before the last is fun.
Godot setup
LowConfirm the installed Godot 4.x version on the Mac and whether headless validation runs from the command line.