B-Maker Explained

Story planningLocations

Why make a location a project entity instead of just writing its name?

Because a recurring place can accumulate facts, scenes and relationships just like a recurring character.

The principle

Track a location separately when consistency across many scenes becomes harder than simply remembering it.

A place can carry story information

A house has rooms, history and constraints. A city has districts and travel time. A fictional station may have rules, factions and recurring scenes. Repeating that information in notes attached to individual chapters creates drift.

Locations help answer “where does this happen?”

When scenes can point back to the same place, the location becomes another way to navigate and inspect the story.

B-Maker story planning workspace with project entities connected to manuscript scenes

Not every place deserves a card

If a café appears once, write “café” and move on. Structured location data is useful only when the place becomes important enough that consistency and reuse matter.

The same progressive-complexity rule applies

Do not build a world database before writing. Promote a place into a structured entity when the manuscript earns the complexity.

Why Characters, Relationships and Arc Points? · Why Plotlines?