Common Builder Mistakes
Even good builders make the same handful of mistakes. This chapter collects them so you can recognize each one early, understand why it hurts, and choose the simpler Hearth & Crown approach instead.
1. Building everything before play
Trying to define the whole world — every village, law, family, price, and history — before the first scene.
It costs you weeks of unused work, creates maintenance for places play never visits, multiplies contradiction risk, and leaves less room for the world to grow organically around actual play.
Build a Minimum Playable World instead. Start with enough. Expand when relevance arrives. An unanswered question is not a missing rule; it is room to grow.
2. Turning every concept into a system
Seeing a road, religion, dynasty, claim, memory, rumor, weather pattern, crop, title, routine, or army in the fiction and creating a type, field, tracker, or subsystem for it.
Most concepts need no architecture. Ask first whether existing records, Project truth, description, or reference knowledge already handle the actual problem. A road is geography. A rumor is information with a carrier. An army is people, organization, and realm pressure in context.
A concept is not a mechanic. A concept is not a type. New systems must earn their existence.
3. Tracking everything
Recording every meal, coin movement, conversation, rumor, relationship shift, memory, routine, weather change, and work action.
Exhaustive bookkeeping does not create realism — it buries it. Realism comes from coherent consequences, not complete logs. Simulate broadly. Persist selectively. Write only what matters. Record what changes what people can do, owe, own, or expect — and let the rest pass as lived life.
4. Creating every NPC
Assuming every person needs a Character file.
A person can exist without a Character file. Villages hold hundreds; only a few need individual state. Persist someone when continuity requires it: recurring employer, spouse, rival, official, partner, craftsperson, witness, household member. Until then, let them live as background — named, speaking, real, and unfiled.
5. Duplicating the same fact
Writing ownership in two places, employment in two places, skill rank in two places, office, household membership, or location in two places — until the copies disagree.
Duplication drifts. One copy updates, the other does not, and the world contradicts itself. One fact should have one authoritative home. Ownership lives with the property. Work lives with the employment. Belonging lives with membership. Write it once, point at it everywhere else.
6. Re-deriving facts from related facts
Assuming a label proves another truth: occupation proves skill, nobility proves authority, wealth proves status, residence proves ownership, title proves competence, reputation proves truth, marriage proves affection, membership proves leadership.
A related fact never transfers authority. Read what is actually established; do not reconstruct it from neighbors. The employed smith may still be learning. The titled courtier may command nothing. Check the fact itself.
7. Turning reference into Project canon
Treating the library's grounded baselines as mandatory law for your world.
Reference explains what is plausible in general. Your truth decides what is true here. The baseline may describe common landholding or harvest patterns; your valley decides its own customs, crops, and calendar. Consult, then override freely.
Project truth beats general reference, every time.
8. Universalizing "medieval"
Assuming one universal law, hierarchy, economy, inheritance, religion, military, tenure, or settlement form — and one set of myths: everyone dying young, universal barter, universal filth, every village holding every specialist, all nobles wielding identical power, armor freezing its wearer solid.
Hearth & Crown gives baselines precisely so you can vary them. Your world decides its institutions. Difference is identity, not error.
9. Assigning universal prices, wages, or speeds
Fixing permanent tables for prices, wages, rents, travel speeds, yields, construction times, or army sizes.
Context decides actual values: season, place, scarcity, relationship, urgency. Your world anchors its own scale — what an ordinary day's labor earns — and every judgment flows from there. Tables organize knowledge. They never become a second resolution engine.
10. Treating occupation as character class
Reading a job title as a package of skill, status, wealth, and destiny.
Occupation is not a class. Occupation is not skill rank. Employment is not occupation. A weaver may be novice or master; an employed guard may still be learning the sword; a skilled smith may have no employer at all. Establish work, arrangement, and capability separately.
11. Treating titles as automatic authority
Assuming a title, noble birth, or fine relations automatically grant jurisdiction, command, land, or obedience.
Title is not office, and neither is authority. Nobility is not automatic jurisdiction. Every power comes from your law, custom, and established state — exactly as much as granted, no more.
12. Making the player the center of everything
Letting every NPC, opportunity, conflict, rumor, and crisis exist because the player arrived.
People have their own goals, work, and obligations. The world continues elsewhere. Ordinary life stays ordinary whether watched or not. Attention is not causation. Let the player discover the world, not generate it by looking.
13. Manufacturing drama
Adding danger, betrayal, encounters, or escalation because a scene is quiet.
Ordinary life is content. Nothing unusual happening is a valid result. A safe road may stay safe. A workday may stay routine. A shopkeeper may simply be busy. A refusal may remain a refusal. Drama earns its place through causes — never through silence.
14. Turning social ability into control
Letting persuasion, status, or relationship force love, loyalty, forgiveness, or obedience.
Social skill is not mind control. Relationship is not obedience. Authority is not automatic compliance. Persuasion opens ears; it never commands hearts. Even friends, spouses, and patrons may refuse — and sometimes should.
15. Making information omniscient
Letting everyone know everything immediately.
Information requires a plausible path. Public is not universally known. Belief is not truth. Rumor is not fact. News travels with carriers, garbles in retelling, arrives stale, or never arrives at all. Different places believing different things is the world working correctly.
16. Turning plausible assumptions into canon
Promoting every improvised detail — a name, a price, a weather remark — into permanent law.
Inference is not canon. Plausible is not established. Improvise freely to support a scene; establish permanently only what consequence requires, through the proper authority. Honor what was plainly stated and acted upon; release the rest.
17. Copying another game's subsystems
Adding factions, dynasties, claims, army systems, meters, scores, or trackers because some other game has them.
Start from the fictional problem, not the foreign solution. Ask what is actually happening here, then ask whether existing records and truth already solve it. Most of the time they do. Borrow insight freely; import machinery almost never.
Before adding complexity, ask
- What problem am I solving?
- Does the system already solve it?
- Does this need permanent state?
- Is this Project truth or merely plausible?
- Who benefits from this complexity?
- Will play become better — or merely more complicated?
Build what play needs. Let the rest remain possible.