An amphora that came to life
Blood and Clay began as a small desktop idle-gladiator idea and then acquired the dangerous quality all my favorite projects seem to acquire: a very specific identity.
The basic fantasy is that you are not looking at a game decorated with ancient pottery.
You are looking at the pottery itself somehow moving.
Characters, status, events, progression, and eventually the history of the gladiator should feel painted onto clay in the visual language of Greek and Roman black-figure pottery.
That single idea has ended up driving almost everything else.
The part I keep coming back to
I have spent a ridiculous amount of time thinking about silhouettes, black slip, cracks, wear, ornament, fired and unfired clay, how text belongs beside painted figures, and how much modern UI can be removed before the game stops being legible.
The goal is not historical reenactment and it is not a generic idle game wearing an ancient-Greece skin.
I want the interface, the storytelling, and the world to feel as if an ancient painter somehow acquired animation and an inconvenient amount of knowledge about game UI.
The compact version of the game is deliberately passive. The player should be able to leave a small horizontal ribbon on the desktop and glance at what the gladiator is doing rather than constantly making moment-to-moment selections.
Clay as history
One of the ideas I like most is letting the material itself remember the character.
Cracks can accumulate. Wear can appear. Progression can become part of the vessel rather than another abstract menu. A later life may leave something closer to an archaeological object than the clean surface the player began with.
That is still design territory rather than a promise about the finished game, but it is the kind of idea that tells me whether a feature belongs.
Does it make the amphora feel more alive, more historical, or more personal?
If not, it probably needs a very good reason to exist.
The less romantic problem
Blood and Clay is also one of the projects teaching me the painful difference between having a strong vision and having a shippable scope.
The vision comes easily to me. Once I know what something wants to be, I can keep discovering implications almost indefinitely.
That is useful until every implication becomes a requirement.
So part of the work now is not adding more identity. It has plenty.
It is choosing the smallest version that can actually carry that identity into somebody else’s hands.
I am still figuring that part out.
This page will probably become more useful as it records those decisions rather than pretending the answer was obvious from the beginning.