The Miner Was Replaced, explained one task at a time
Miner Replaced is an unofficial English guide for The Miner Was Replaced — the underground programming DLC for The Farmer Was Replaced, not a standalone game. Find the task in front of you, understand what the game is actually asking, then write the code.
Start here Browse the directory
DLC for The Farmer Was Replaced · requires the base game · PC (Windows, Mac) · planned release November 2, 2026 — the date can still move
Find your task
- Start here: get ready to go underground The Miner Was Replaced needs The Farmer Was Replaced. Check the planned release, platforms and practical skills to prepare for underground tasks.
- Why Python-shaped code can fail here Separate language support, unlocks and game commands when Python-shaped code fails. Use a short adaptation checklist before adding more code.
- Give every scan a stopping rule Give a scan a measurable end, update progress after confirmed work, and handle failed actions. Follow a four-step conceptual trace.
- Track a bounded route, one move at a time Follow a bounded 4×4 snake route. Track confirmed position, visited cells and the last move without assuming underground wrapping or damage rules.
- Remember what happened, not what you hoped happened Keep confirmed position, visited locations and pending work separate. A failed-move example shows when state should change and when it should not.
- Understand sorting before moving mushrooms Learn compare, swap and a reliable stopping condition with an original four-token exercise. Mushroom rules and game commands are not assumed.
- Prove a safe move before taking it Use three conventional Minesweeper examples to prove safe cells, prove mines and recognize ambiguity. No final DLC board rules are assumed.
- Find the first step that goes wrong Separate syntax, names, unlock availability and wrong state. Trace the first bad step and reduce it to a small reproducible example.
- Find the work your script repeats Compare the same completed job before optimizing. A fixed hypothetical example separates movement, repeated observations and avoidable rework.
- Edit a file, confirm the change, then run Use the official .py and File Watcher workflow safely: identify the active file, save an edit, confirm detection and run it deliberately in the game.
- A first look at the underground tasks See the announced underground tasks: resources, colorful mushrooms, Minesweeper and careful ruins excavation, with official scenes and preparation links.
No guide matches that filter — try a shorter word, or reset the filters.
New here? Read in this order
-
Check access, platforms and release facts
What has to be true before you can play the DLC at all.
-
Learn where the in-game language differs from Python
Why working Python can still fail inside the game.
-
Pick one task guide and work it end to end
Routes, loops, state, sorting, mine logic, errors.
Practice the thinking, not just the code
Three small workbenches that each train one skill — with the full static explanation always on the page.