Dev Blog #11: Finding a Visual Identity
Designing StormTome's logo became a lesson in contrast, font licensing, and the detail lost through repeated AI image edits before returning to a familiar book.
The development journal
Designing StormTome's logo became a lesson in contrast, font licensing, and the detail lost through repeated AI image edits before returning to a familiar book.
How classic BBS adventures, unpredictable encounters, and the promise of discovery inspire StormTome's Explore button and keep players curious.
Multiple agents can move StormTome forward in parallel, but dividing the work also means coordinating edits, handoffs, and shared test environments.
StormTome uses AI for writing, artwork, and code. The AI Assisted label explains those contributions, the human work, and what I remain responsible for.
Draven began as a world for stories to grow in. Its history and competing beliefs about magic gave StormTome a setting where choosing a side would rarely be simple.
Auditing StormTome's growing test suite revealed misleading checks, hidden assumptions, and outdated code, raising questions about coverage and confidence.
StormTome's docs had gathered old rules, discarded plans, and repeated instructions. Cleaning them up meant deciding what to keep and what agents should trust.
Finding the name StormTome meant revisiting childhood influences, imagining a magical catastrophe, and choosing an identity that could grow with the game.
Generative AI has accelerated StormTome's development, but getting useful work out of a limited allowance has become a development problem of its own.
StormTome is on its third major version. Each one has helped me test ideas, discard bad assumptions, and better understand the game I want to build.
StormTome is the RPG I have always wanted to build. This dev blog looks at the games, ideas, and technology shaping the project.