The game · simulation / strategy · Unreal Engine · in development
A hundred clans.
One hill.
Eleven thousand years ago, people with neither writing nor wheels raised tonnes of stone on a hilltop. This game asks you one question: how would you have talked them into it?
Trailer · coming
concept placeholder
The premise
You cannot give orders. You can only persuade.
In the Neolithic, around a hundred clans of 20–50 people, settled 5 to 100 km apart, must be persuaded to build and organise the monumental enclosures of Göbeklitepe, Sayburç, Karahantepe and others.
- ≈100
- clans
- 20–50
- people per clan
- 5–100
- km apart
These figures are the game's design assumptions, not an archaeological population estimate. The wiki separates evidence from fiction on every page.
Five absences
Everything you do not have is a rule of the game.
- 01No writingPlans, agreements and debts live in memory: in speech, in knots, in signs cut into stone.
- 02No paperMeasures are taken with cord and paces; drawings are made in the dirt and washed away by rain.
- 03No metalYou have flint, obsidian, bone, antler and wood. All of it breaks; all of it is made again.
- 04No animal powerNo oxen, no donkeys. Every stone, every skin of water, every basket of grain arrives on a human back.
- 05No wheelA pillar weighing tonnes walks on sledges, logs, ropes and slopes — and on enough people.
The problems you will have to solve
The core of the game
These are design goals, not finished features. The wiki describes both the mechanic and the archaeological basis of each.
- 01
Persuade the clans
Around a hundred clans, each with its own totem, resources and suspicions. You cannot command any of them — only persuade.
- 02
Communication
News travels at walking pace and changes a little in every mouth. How do you tell a clan a hundred kilometres away when to come?
- 03
Logistics
Food, water, stone, flint, rope, timber and people: everything a building season needs arrives on foot.
- 04
Labour and specialisation
Knapper, carver, hunter, gatherer, brewer… Who cuts stone, and who feeds them? Raising a specialist takes seasons.
- 05
Motivation
No wages, no coercion. What keeps people on the hill is feasting, standing, kinship and a shared story — and those can run out.
- 06
Safety
A toppling pillar takes a clan's best carver with it — and the clan's trust along with him.
- 07
Knowledge: the rules of stone, fire and sky
Levers and ramps, knapping and drilling, fire and lime, custom and sanction, the stars that mark the season, the right bed of stone. All of it handed down by word of mouth.
Concept placeholders — not in-game footage
Screens
Notes from the workshop
Development diary
Building without wheelsDesign notes on moving and raising multi-tonne stone with rope, timber, muscle and patience, and nothing else.Read +Close −
The constraint is the game
The premise rules out metal, the wheel, draft animals and writing. For the building work this leaves stone tools, wood, plant fibre, hide, water, fire and human muscle. We do not treat these limits as a handicap to be removed by later upgrades. They are the subject.
What the evidence allows
Archaeology gives us fixed points. The pillars are limestone, cut from the plateau around the site; unfinished pieces still lie in the quarry areas, and the tools found are of flint and other stone. How the pillars were actually moved and raised has left no direct trace, so every method shown in the game is a reconstruction. Sledges, rollers, levers, ramps and ropes are the usual candidates in the research literature, and experiments elsewhere show such methods can work, but none is proven for Göbeklitepe. The question page on moving the pillars sets out the debate.
Physics the player can reason about
Our intent is for the physics to be simple enough to think with. A heavier stone needs more people on the ropes. A slope multiplies the effort. Wet ground, a worn rope or a badly placed lever changes the outcome. The player should be able to predict roughly what will happen and then be surprised by what was overlooked. The physics and geology pages hold the working assumptions.
Everything has to be made first
Before a stone moves, someone has to make the rope, shape the timber and knap the picks, and those materials have to be found and carried. We want this chain to be visible, because it is where building meets logistics and raw materials: a rope long and strong enough for the job is itself many days of work.
Risk without melodrama
Heavy stone, crowded slopes and improvised gear are dangerous. We intend injury to be a real cost that the player plans around, and that affects whether clans return, without turning it into spectacle. The work safety page explains the approach.
Still undecided
How much of the hauling should be simulated and how much abstracted is an open question. We would rather show less and keep it honest.
A hundred clansDesign notes on the game's social map: about a hundred small clans, days apart on foot, and no way to command any of them.Read +Close −
The numbers we start from
The premise gives us about a hundred clans of 20–50 people each, living 5–100 kilometres apart. These figures are a design premise, not a census: archaeology cannot count the communities that used Göbeklitepe. They do set up the problem we care about.
Simple arithmetic shows why. A clan of thirty includes children, the elderly and people who must keep finding food. Only a handful of adults can leave for weeks. No single clan can quarry, move and raise a large pillar alone. The work only becomes possible when many clans each lend a few people, and that is a social problem before it is an engineering one.
Distance as the main obstacle
A message between neighbours 5 kilometres apart is a morning's walk. A message to a clan 100 kilometres away is several days each way, carried in someone's memory, because there is no writing. We want distance to be felt in the design: news should arrive late, promises should be hard to check, and a meeting should be an event that has to be arranged well ahead. The communication page and the envoy role describe how we are thinking about this.
No chiefs to appeal to
Nothing excavated so far shows a ruler at these sites, and the game does not assume one. The player is intended to work through persuasion, reciprocity and reputation. Why would a clan come? Possible answers we are exploring include shared feasts, exchange of materials, marriage ties, stories and obligations remembered from earlier seasons. Scholars debate how much weight each of these carried, as the question on persuading the clans explains; the game should let more than one answer work.
Rules without writing
When a hundred groups cooperate, disputes follow: an injury, a broken promise, a quarrel over food. With no written law, rules live in memory and in the standing of people such as elders. The law page sets out the little that evidence suggests and the larger part we have to imagine.
Open design questions
How many clans can a player keep track of before it becomes bookkeeping? How should a clan remember being treated badly? These are unresolved, and we would value the author's view.
Why a game?Why the questions raised by Taş Tepeler lend themselves to a game, and what we want the player to have to solve.Read +Close −
A problem you cannot read your way out of
A book can tell you that a limestone pillar several metres tall was cut from the bedrock and set upright by people who had no metal tools, no wheel, no draft animals and no writing. It is harder for a book to make you feel how many separate problems hide inside that one sentence. Who decided where the building would stand? How did the news reach people living several days' walk away? Who fed the carvers while they were not hunting? What happened when someone was hurt, or simply refused to come back next season?
The project behind this site starts from that list of problems: persuading clans, communication, logistics, labour, motivation, safety, physics, tools, chemistry, law, astronomy and geology. A game, now in development in Unreal Engine, is our attempt to hand those problems to the player instead of describing them.
What we want the player to do
The intent is that the player never commands an army of workers. The premise is a landscape of about a hundred clans, each of 20–50 people, living 5–100 kilometres apart. Nobody in that world can be ordered to do anything. So the central activity we are designing around is persuasion and coordination: giving people who owe you nothing a reason to walk a long way and do heavy, risky work together.
Each problem in the list is meant to become something the player has to think through, and the wiki records the reasoning behind each one, with the archaeology kept separate from the design.
Evidence first, invention labelled
Archaeology does not know how the builders organised themselves; it knows what they left behind. Where the game has to invent, for example how an agreement between clans is reached, we want that invention to be plausible and clearly marked as ours. The pages on motivation and logistics each state what is excavated evidence, what is interpretation and what is game fiction.
What this diary is for
These notes describe intentions, not finished features. They will change as the author reviews them and as the work on the game continues.
Newsletter
Follow the development
One e-mail when there is a new diary entry, the first in-game footage or the trailer. Nothing else.
- Engine
- Unreal Engine
- Status
- In development
- Genre
- Simulation / strategy
- Platforms
- Not announced yet
- Release date
- Not announced yet
- Setting
- Pre-Pottery Neolithic, Taş Tepeler