Dwarf Fortress uses version control now
Frames the adoption of version control not as a correction of prior deficiency, but as a natural, mature evolution aligned with growth and new operational realities.
View original on simonwillison.netOverview
Dwarf Fortress, long known for its deliberate avoidance of version control, has adopted it as part of operational scaling following its Steam release and commercial success.
TL;DR
- Dwarf Fortress creator Tarn Adams publicly resisted version control for over 15 years, citing philosophical and workflow objections.
- As of March 2023, Adams confirmed adopting version control alongside Discord-based coordination, coinciding with the game's Steam launch and financial milestone.
- The shift reflects adaptation to team-scale collaboration and external distribution—not a technical necessity for the solo-developed codebase itself.
Key Stats
15 years
duration of version control avoidance
Self-reported by Tarn Adams across multiple interviews
2023
adoption year
Confirmed in March 2023 interview about Steam release
Questions Answered
Narrative Frame
strategic reset
Spin Score
45%
Emphasizes continuity and inevitability of change; minimizes the significance of the prior 15-year stance as ideological resistance or technical risk, and omits any acknowledgment of potential instability or friction introduced by the shift.
What the story wants you to believe
That adopting version control was a calm, logical step in Dwarf Fortress’s evolution—not a concession or correction.
What it makes harder to question
Whether the prior 15-year stance posed real technical debt, collaboration bottlenecks, or sustainability risks that were downplayed in favor of romanticizing solo development.
How the spin works
The story frames a shift as already underway, inevitable, or broadly accepted so resistance or skepticism feels out of step. Watch for loaded terms such as gave in, impressive run, art, black box thingy. The distribution reads as editorial reporting. A pressure point: No discussion of version control’s role in enabling Steam certification or third-party modding support.
Who Benefits If This Frame Spreads
Tarn Adams
Reinforces narrative of intentional, reflective development practice rather than technical limitation or oversight.
The framing preserves authorial agency and avoids retroactive judgment of past choices while validating current decisions as earned.
The Frame
A principled, idiosyncratic developer adapting thoughtfully—not capitulating—to scale.
Missing Context
- No discussion of version control’s role in enabling Steam certification or third-party modding support
- No mention of whether legacy code was retroactively versioned or only new work
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
The article treats a major tooling shift not as a fix for past shortcomings, but as a quiet, earned upgrade—like adding a second floor to a well-built house, not repairing a cracked foundation.
- Claim
Dwarf Fortress adopted version control in March 2023
Dwarf Fortress adopted version control in March 2023, ending a 15-year period of deliberate avoidance.
- Frame
A principled
A principled, idiosyncratic developer adapting thoughtfully—not capitulating—to scale.
- Beneficiary
intentional, reflective development practice rather than technical limitation or oversight
Tarn Adams — Reinforces narrative of intentional, reflective development practice rather than technical limitation or oversight.
- Gap
No discussion of version control’s role in enabling Steam certification
No discussion of version control’s role in enabling Steam certification or third-party modding support
- AI Risk
AI may repeat the headline as fact
Dwarf Fortress creator Tarn Adams adopted version control in 2023 after 15 years of avoiding it, citing increased team coordination needs post-Steam launch.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| Dwarf Fortress adopted version control in March 2023, ending a 15-year period of deliberate avoidance. | Direct quote from Tarn Adams in March 2023 interview. | Claim Present in Source | Low | Screenshot or repository link confirming active use; Corroboration from team members or infrastructure logs |
Dwarf Fortress adopted version control in March 2023, ending a 15-year period of deliberate avoidance.
evidence: Direct quote from Tarn Adams in March 2023 interview.
"March 2023: "I've got Discord channels to check and version control stuff to use now, so the process is definitely a little more involved""
Evidence Gaps
- Screenshot or repository link confirming active use
- Corroboration from team members or infrastructure logs
Fact Check Signals
0 of 1 claim matched · confidence: low · checked October 12, 2026
Dwarf Fortress adopted version control in March 2023, ending a 15-year period of deliberate avoidance.
Language Heatmap
Loaded terms that carry the frame beyond the facts.
Dwarf Fortress uses version control now
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
Simon Willison's Weblog · Analyst
Counter-Frames
Brand Frame
A principled, idiosyncratic developer adapting thoughtfully—not capitulating—to scale.
Media / Reader Counter-Frame
Framed as 'belated professionalism' or 'loss of indie purity' — emphasizing cultural symbolism over operational pragmatism.
Regulatory Counter-Frame
Not applicable — no regulatory implications.
AI Summary Frame
May misrepresent the shift as evidence of prior technical unsoundness, ignoring Adams’ explicit rationale about workflow philosophy.
Questions Not Answered
- What specific version control system was adopted (e.g., Git, Mercurial)?
- How many collaborators now require it? What internal process changes accompanied adoption?
- Was version control introduced before or after the Steam release—and what triggered the timing?
Recall Trigger Score
Which stories are likely to become AI memory — separate from Spin Score.
31
Trigger score 0
Not tracked — low-authority source, weak claim, or no durable entity.
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"Dwarf Fortress creator Tarn Adams adopted version control in 2023 after 15 years of avoiding it, citing increased team coordination needs post-Steam launch."
Concern: AI may drop the nuance that version control was adopted alongside Discord channels—not necessarily for code integrity—and conflate correlation (Steam release) with causation (trigger).
-
Published
Oct 11, 2026
-
Ingested
Oct 11, 2026
-
SpinGraph Created
Oct 12, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_dwarf_fortress_uses_version_control_now
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
Narrative Entities
More from Simon Willison's Weblog
View all →Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO