Why Minecraft gets boring once everything is automated
Farms don't just save you work: they take over the actions your sessions were built around. Ivan Illich explains why a world that plays itself stops asking anything of you.
Why Minecraft gets boring once everything is automated
Minecraft gets boring once you automate everything because farms don't only save you work: they replace the actions each session was built around. The world keeps producing resources, but it stops asking anything of you, and a game that asks nothing gives you no reason to log in.
There's a moment almost everyone who plays survival seriously will recognise. The chests are full, the iron, gold and XP farms are running, the sorting system drops every item into its place. You log in, check the counters, walk once around the base and quit ten minutes later without having done anything in particular.
The farm that worked too well
Search for why it happens and the answer is always the same: more farms. Lists of the best endgame farms, tutorials for automating whatever is still done by hand, round-ups of what to do after the Ender Dragon. They all answer what to build next, and none of them answers the question the person searching is really asking: why, with everything solved, logging in no longer appeals.
The short answer is that the boredom doesn't arrive in spite of the farms but because of them. Every farm is built to remove a task, and it succeeds. What nobody accounts for while building it is that the task was also the reason to be there.
Ivan Illich and the tools that do it for you
Ivan Illich, a thinker who wrote about schools, hospitals and roads, published a book in 1973 called Tools for Conviviality. His central distinction fits Minecraft with almost no translation. Some tools extend what a person can do with their own hands and their own judgement, and some tools end up doing it in their place.
A bicycle belongs to the first kind: you go further, but you are still the one pedalling, picking the route and deciding when to stop. Illich called such tools convivial, because they live alongside the autonomy of whoever uses them instead of replacing it.
The second watershed
Illich added something more uncomfortable. In his account, many tools pass two watersheds. At the first they improve life in obvious ways. At the second they keep growing and start taking away the very thing they existed for: the system meant to save everyone time ends up organising everyone's time.
An iron farm crosses the first watershed straight away: you no longer have to hunt golems or spend hours in caves for a few ingots. The second arrives when the sum of your farms covers everything you used to do with your hands. You no longer mine, no longer farm, no longer explore for materials. The world produces, and you supervise.
Building the machine was the game
Concluding that automation is a mistake would be easy, and wrong. Designing a farm is one of the most creative things the game offers: timing the spawns, testing the redstone, failing, adjusting, watching it finally work. A large part of the technical Minecraft community plays exactly that, and what we described in the history of redstone grew out of it.
The nuance lies in which part is the game. Building the machine is your action, full of decisions. The machine running for months is not. Once a farm is finished, its design becomes a memory and its operation becomes somebody else's routine. That is why so many players find building the next farm more appealing than using the last one.
The principle: a tool is measured by what it leaves you to do
Illich's test reaches far beyond a world made of blocks. A tool shouldn't be judged by how much work it saves, but by which action it leaves in the hands of the person using it. If what it saves is something you never cared about, you've gained time. If what it saves was the verb that defined you in there, you've gained inventory and lost the reason.
In the piece on grinding we separated repetition that challenges you from repetition that merely holds you. Automation is the logical answer to the second kind. The risk is applying it to the first kind as well without noticing.
What to keep
The way out isn't tearing down farms but deciding beforehand which action you want to keep doing yourself. Some players keep mining by hand because it's their time to switch off. Some automate every resource and keep building, because their game was always shaping the landscape. Others change verbs entirely and move from producing things to organising something with other people.
For anyone designing a server, KobiCraft included, the same question applies to every system that saves steps: does this take a chore away from the player, or does it take away the game? That's a design opinion rather than a finding, and it can be argued with. What is hard to argue with is the symptom: a world where everything is solved is a world people enter out of habit.
The full chest
Minecraft never promised a goal to reach and then rest. It promised things to do. A perfect farm keeps its side of the bargain and leaves the chest full, but a full chest is not a reason to come back.
What brings people back is having something unfinished in their hands.
Frequently asked questions
Do AFK farms ruin the game? Not on their own. An AFK farm is a solved resource, and solving resources makes sense when what you care about lies somewhere else, such as building a city or setting up an event with friends. The trouble starts when the farm solves exactly the activity that brought you into the world and nothing behind it takes its place. Then the inventory keeps growing while your sessions keep getting shorter.
Who was Ivan Illich? An Austrian-born thinker and priest, born in Vienna in 1926, who spent much of his life in Mexico and wrote about schools, medicine and transport. In Tools for Conviviality, published in 1973, he separated tools that widen what a person can do for themselves from tools that end up doing it for them. He never wrote about video games; his framework is applied here as an analogy.
Is it better to play without automating anything? No. Harvesting every stalk of sugar cane by hand for months is not a virtue, and people who love technical Minecraft find their game precisely in designing machines. The useful question is a different one: which action do you want to keep as yours? Automate what you would not miss, and keep by hand whatever used to bring you back.
Para continuar leyendo
- Análisis6 minPor qué pasas más tiempo eligiendo servidor que jugandoDel mismo tema que acabas de leer.
- Análisis7 minPor qué la granja pública siempre acaba vacíaDel mismo tema que acabas de leer.
- Análisis6 minMirar a los mejores no te enseña a construirDel mismo tema que acabas de leer.
Has llegado al final. Puedes seguir con una de estas, o descansar.
Gracias por leer. Vuelve cuando quieras.