I wrote the Eternal Fusion lore book to teach players about the universe. I did not expect it to teach me about game design. But it did. Here is what I learned.
Lesson 1 — Lore is design documentation
Writing the lore forced me to answer design questions I had been avoiding.
**”Why does the Alliance not just conquer the Horde?”** — The lore says: because the Horde is not a fixed target. They move. They fracture when they lose. They re-form. Conquering them does not solve the problem; it just moves it.
This became the design decision: no permanent territory. The 30-day reset.
**”Why does the Sylvan not just steamroll everyone with their forest?”** — The lore says: because the forest is not the Sylvan’s to command. They participate in the forest. They ask, and the forest answers. If they asked too often, the forest would stop answering.
This became the design decision: the Canopy mechanic has a focus meter. Using it costs. The forest is not a weapon; it is a partner.
**”Why does the Clockwork not just build infinite constructs?”** — The lore says: because constructs need maintenance. Maintenance requires infrastructure. Infrastructure requires the Grand Algorithm’s approval. The Algorithm has limited throughput.
This became the design decision: construct costs and maintenance costs. The Clockwork player has a budget.
The lore was the design doc I didn’t know I needed.
Lesson 2 — Constraints come from the world
When I designed gameplay first and lore second, the lore always felt forced. The lore had to bend to fit the gameplay.
When I designed lore first and gameplay second, the gameplay always felt inevitable. The gameplay was the only thing the lore could support.
Example: I originally had the Alliance as a faction that could build walls anywhere. The lore wrote them as defensive specialists. So the gameplay: Alliance can only build on defensible terrain (rivers, mountains, fortified locations). The constraint came from the lore.
This made the gameplay better. Constraints force interesting decisions. Players have to choose where to build. They have to fight for defensible terrain. They can’t just wall off the entire map.
Lesson 3 — Voice carries the lore
The lore book uses a specific voice: declarative, slightly archaic, no contractions, third person. “Aeldric walks into the Badlands. He does not return. The warbands find his sword three days later.”
That voice transfers to the game. NPCs speak in the same voice. Item descriptions use it. Quest text uses it. The lore book is the tone guide for everything in the game.
When the voice is consistent, the world feels like a world. When the voice is inconsistent, the world feels like a video game.
Lesson 4 — The reader does the heavy lifting
The lore book does not explain everything. It gives the reader enough to imagine the rest. The reader does the heavy lifting.
Aeldric’s backstory mentions his master, but does not explain who his master was. The reader imagines. The reader cares because they imagined.
If I had written the master’s backstory explicitly, the reader would have read it and moved on. By leaving it implicit, the reader carries it with them.
This translates to gameplay: EFER does not explain every mechanic. It gives the player enough to figure out the rest. The player who figures out the meta is more invested than the player who was told the meta.
What this means for the business
I am a better game designer because I wrote the lore book first. The lore book is the design documentation. The lore book is the tone guide. The lore book is the constraint set.
When I sit down to write code, I already know what the lore demands. The code writes itself.
When I sit down to write an article, I already know what the lore supports. The article writes itself.
When I sit down to design a new feature, I already know what the lore permits. The feature writes itself.
The lore book is not a side project. It is the foundation. Everything else grows from it.
How to start your own
If you are building a game, write the lore first. Write 1,000 words about your main character. Write 500 words about the main conflict. Write 500 words about the world.
Then build the game around those 2,000 words. The gameplay will feel inevitable. The mechanics will feel necessary. The world will feel coherent.
The lore book will become your design doc, your tone guide, your constraint set, and your marketing copy. Four artifacts from one source.
Where to read mine
The Eternal Fusion lore book is on Gumroad — paperback + Kindle + PDF. Free chapters at /lore-sample/. The full index at /lore/. The factions at /factions-alliance/ (and 6 more).
Play EFER on Roblox. Free.
The lore book that taught me game design is the same lore book players read. Same source, same voice, same world.
