This content is protected against AI scraping.
I’ve recently reviewed the transcripts of the first two sessions of our newest Godflesh campaign, and I’m reminded why playtesting matters. Not the stress-testing-mechanics kind or the hunting-for-edge-cases kind, but the kind where you watch people try to understand your game for the first time. That’s where you discover all the things you thought were obvious but aren’t.
The Living Well Cycle group spent their first two sessions creating characters and building their adventuring band. They’re playing in Jinshati and the Lustrous Caldera, and they’ve assembled a Shaper, an Anointed, a Haunted, a Primal, and a Harrier. They also asked a lot of questions. Those questions showed some gaps in how the Chrysalis Quickstart explains fundamental concepts.
The divine essence problem
The most persistent confusion was what I think of as the “divine essence” concept – the idea that treasures are imbued with power from dead gods. Several players asked variations of: “What exactly is an aspect?” and “How do my treasures relate to gods?”
One player noted that the treasures needed more explanation in the book itself, and that my in-session emphasis on “essence of a dead god embedded in each treasure” finally clarified what they were after. When I heard similar feedback from others, the documentation gap became obvious. I’d been so deep in the game’s core concept – gods are mortal, mortals consume godflesh, power comes from divine remains – that I forgot players coming fresh to the material wouldn’t automatically connect treasures to this cycle.
The playtest materials explain that each treasure has an “aspect” and that you should choose domains like “chaos,” “volcanoes,” or “plant growth.” But they don’t explicitly state that this aspect represents the portfolio of a dead god whose remains were crafted into your treasure. That’s the missing link. Without it, players don’t understand why aspects matter or how to think about their treasures within the world’s mythology.
The next draft addresses this directly. The treasure section now opens clearly: your treasures aren’t just magical items. They’re relics containing fragments of divine power from gods who fell in earlier cycles. The aspect isn’t a mechanical tag – it’s the echo of what a god once controlled. When your sword channels volcanic fury, it’s because somewhere in its creation, materials were harvested from a god of fire and stone who met their end.
The power of concrete examples
The second pattern was how much players benefited from concrete examples. When they asked how to personalise their treasures beyond the generic playbook descriptions, I shared examples from another group: a weapon forged from a dragon’s tooth that ignites with flame, a giant needle that shrinks and grows, a tambourine made from siren scales that makes plants grow when played.
The difference was immediate. Players stopped treating treasures as abstract mechanical categories and started creating specific items with personality and history. One player designed a staff with an ether-stone sphere that lets them manipulate the weapon’s mass. Another created a humanoid golem named Kaz, cobbled together from clay and bronze, inherited from their dead master. These aren’t just “companion” and “mastercraft weapon” – they’re pieces of the world.
Abstract mechanics need concrete anchors. The playtest materials provide the framework, but they need to show what filling in that framework actually looks like. The Ashcan Edition – the next development milestone – will include a full section of treasure examples, showing how different aspects manifest in different item types, and how to connect each treasure to a specific piece of divine history.
Boundaries need explicit definition
Another pattern emerged around the world’s constraints. The writing taboo generated several questions about what exactly counts as forbidden. Can you use pictographs? What about numbers or symbols? One player realised mid-session that their “recipe book” treasure violated the taboo entirely – which led to a productive conversation about iconography versus actual writing systems.
Players also needed clarification on character bonds. The playbooks suggest four bonds, but are those fixed? Can you create more? The answer – stick to four during creation, though more can develop during play – wasn’t immediately clear from the text.
These questions reveal something about game design: constraints are features, but only if players understand them. The writing taboo isn’t just worldbuilding flavour. It shapes how characters document knowledge, creates opportunities for memory-keepers and oral traditions, and makes certain character concepts more interesting. But if players don’t know where the line is, they can’t engage with it meaningfully.
The optimisation question
One exchange stood out. A player asked, “What does Primal usually want?” – meaning attribute allocation. They wanted the optimal build, the standard approach, the established wisdom. My answer was honest: “The game doesn’t have a ‘usually’ yet.”
This isn’t evasion. Godflesh is still in active development, and we haven’t played enough to establish optimisation patterns. And honestly, I’m not sure I want rigid patterns to develop. The game is built on PbtA principles, which favour player choice and fictional positioning over mathematical optimisation. Your attribute array should reflect who your character is and how they approach problems, not what the build guides say.
But I recognise what the player actually needed. They wanted guidance, not a lecture about narrative systems. The better answer looks like context rather than prescription: “Consider which moves you’ll use most and what situations you want to excel in. If you took Wild Speech, you’ll rely on Insight for social situations. If you took Bestial Fury, Might drives your combat approach.” That respects player agency while giving them something to work with.
The rules error
One concrete problem: an attribute allocation rule was present on the character sheets but not clearly stated in the quickstart text. You assign +2, +1, +0, +0, -1 to your five attributes, then add +1 to one attribute of your choice. That final “+1” was easy to miss, and several players built characters without it.
Straightforward to fix, but also a reminder that important rules need redundancy. Players skim. They flip back and forth. They fill out sheets while half-listening to other players. Single-point-of-failure documentation doesn’t hold up in practice.
What worked
Worth noting what didn’t generate questions. Players grasped the core playbook structure immediately. The Corpus specialisations made sense. The basic moves translated clearly from text to table. The collaborative nature of character creation – everyone contributing to world-building – worked exactly as intended. One player said character creation felt like a conversation, which is precisely what it should feel like.
The group created rich characters with compelling bonds, interesting treasures, and clear motivations. They built a shared setting element – a haven in an unstable volcanic cave – without prompting. They engaged with the Bronze Age aesthetic naturally, creating names and details that fit the world. The fundamental design works. It just needs clearer documentation of the concepts players actually encounter during creation.
The iterative process
This is what playtesting is for – not finding broken mechanics or exploits, but discovering what you failed to communicate. As a designer, you live inside your game world for months or years. You know every assumption, every implied connection, every piece of context. Players don’t. They only have what’s on the page.
Every question a player asks shows where the documentation failed, where an example would help, where explicit boundaries matter. That’s the feedback loop that actually improves a game.
First adventure next
The Living Well Cycle group is about to start their first adventure. They have well-formed characters, an established haven, and enough existing relationships to generate conflict without me having to force it. They’re ready to explore Jinshati, navigate faction politics, and find out what’s lurking in the Lustrous Caldera’s depths.
And they’ve already made Godflesh clearer. Every question they asked, every moment of confusion that led to an explanation, improves the documentation for whoever comes next. I’m grateful for that.
If you’re playtesting Godflesh, keep asking questions. Every “wait, how does this work?” is useful data. Every confusion is fixable, as long as someone surfaces it.