Why I wrote the lore book before I finished the game

Conventional wisdom says: ship the game, write the lore later. I did the opposite. Here is why it worked.

The conventional wisdom

Most Roblox devs ship a working game first. They add lore as a stretch goal. The lore is what they write when they have nothing else to ship.

I wrote the lore book first. 8 chapters, 60,000 words, every faction, every thesis, every NPC. The game came second.

The lore forced the game design. Every faction had a thesis. The thesis implied mechanics. The mechanics implied cards, abilities, and progression trees.
The lore made the game coherent. A faction with no thesis is a faction with no design. The lore book gave every design decision a reason.
The lore made the game marketable. Buyers don’t buy “a Roblox game.” They buy “the lore of Sylvan Communion.” The lore book IS the marketing.
The lore book IS a product. It sells on Gumroad for $9.99. The game is the marketing for the lore book, not the other way around.

If you are building a Roblox game with factions, lore, or a TCG, write the lore book first. The book will tell you what the game should be.