When I first sat down to design the Veilwalker, I made a promise to myself.

It wasn’t going to be a Rogue with a new coat of paint.

That may sound obvious, but it’s one of the easiest traps to fall into when designing for a 5e-compatible game. The temptation is always there to begin with an existing class, rename a few abilities, add setting-specific flavor, and call it finished. It works, but it doesn’t create something that feels like it belongs to its own world.

From the beginning of Whispers of Erosia: Second Bloom Edition, I’ve tried to follow a different philosophy. Every class starts with a single question:

How does this archetype interact with Desire?

Only after answering that question do I begin designing mechanics, class features, progression, and balance. It’s a philosophy that’s become central to the project, because if Desire is truly one of Erosia’s defining forces, then every class should express that force in its own unique way. The mechanics should emerge from the fantasy, not the other way around.

The Veilwalker became one of the clearest examples of that philosophy in action.

The World Remembers

The breakthrough came from a deceptively simple idea.

Desire leaves Echoes.

Every powerful emotion leaves something behind.

• Love.
• Fear.
• Devotion.
• Obsession.
• Triumph.
• Grief.
• Betrayal.

None of these simply disappear when the moment ends. They linger within the Veil, leaving behind subtle impressions that most people never notice. A hurried departure leaves a chair slightly out of place. An argument leaves a room that somehow feels wrong. A lifetime of habit wears a groove into stone. A ritual leaves behind traces long after the candles have burned away.

Most adventurers walk past these details without a second thought.

A Veilwalker learns to read them.

That realization completely changed the direction of the class. Rather than building another stealth specialist, the Veilwalker became something much closer to an investigator, profiler, and observer of hidden truths. Their greatest weapon isn’t a dagger. It’s understanding.

Echoes Tell Stories

One of the biggest design challenges was deciding what an Echo actually is.

At first it was tempting to define Echoes as magical remnants or supernatural clues, but that quickly became too restrictive. The world leaves behind more than magic. History leaves Echoes. Emotion leaves Echoes. Violence leaves Echoes. Even craftsmanship and routine create patterns for someone patient enough to notice them.

That broader definition opened an enormous amount of design space.

A Veilwalker examining an abandoned temple might notice worn stone where countless worshippers once knelt. In a noble’s court, they may recognize subtle shifts in posture that reveal hidden alliances. During combat, they might observe an opponent unconsciously favoring an old injury or repeatedly protecting the same companion.

None of these are magical abilities in the traditional sense. They’re moments of extraordinary perception. Once that idea clicked, the rest of the class began building itself.

Expose

Every class needs a defining mechanic. For the Veilwalker, that mechanic became Expose.

Rather than creating weaknesses that never existed, Expose reveals opportunities that were already present all along. A creature may carry an emotional vulnerability hidden beneath practiced confidence. A crumbling bridge may possess a support beam moments away from collapse. An ancient lock may conceal a forgotten release mechanism. A desperate villain may betray their true motivation through a single glance.

The Veilwalker doesn’t invent these moments. They uncover them.

That distinction became incredibly important throughout development because it changes how players approach every encounter. Instead of asking whether they can roll Investigation, they’re encouraged to ask a much more interesting question.

“What opportunity already exists here?”

That simple shift transforms observation into active gameplay.

Every Pillar of Play

One of my long-term goals for Whispers of Erosia has been ensuring that every class contributes meaningfully outside of combat. The Veilwalker naturally embraces that philosophy because its core mechanic functions anywhere hidden truths exist.

In combat, Expose identifies the precise Opening that turns an impossible fight into a manageable one.

During exploration, Echoes reveal forgotten histories, concealed passages, unstable structures, and clues that reshape how players understand an environment.

In social encounters, those same Echoes become emotional tells, concealed motives, fragile alliances, and carefully hidden fears that can completely alter a negotiation.

The same mechanic supports all three pillars of play without needing separate subsystems for each. That was one of the most satisfying moments in the entire design process because it reinforced the idea that observation itself can be an adventure.

Revelation

Every Erosian class also carries its own relationship with the Desire Cycle.

For the Veilwalker, that defining moment is known as Revelation.

Unlike many high-level abilities that simply increase damage or improve action economy, Revelation represents perfect understanding. Every scattered clue suddenly aligns into a complete picture. Every hidden motive becomes obvious. Every Opening that once required careful investigation simply reveals itself.

Mechanically, it’s the culmination of everything the class has been building toward since first level.

Narratively, it’s the moment every mystery finally makes sense.

I love that it doesn’t ask the Veilwalker to become someone different. It simply allows them to become the absolute pinnacle of what they’ve always been.

Building an Erosian Class

One of the guiding principles behind Second Bloom has been that classes should feel inseparable from the setting that created them.

If you removed the Echoes…
If you removed Expose…
If you removed Revelation…
If you removed the Veil itself…

There wouldn’t be much of a Veilwalker left. That’s exactly the outcome I was hoping for.

Too often, setting-specific classes can be transplanted into another fantasy world without changing a single rule. I wanted the opposite. I wanted players to look at the Veilwalker and immediately recognize that it could only have been born from Erosia’s mythology, cosmology, and Mechanics of Desire.

In many ways, it has become the strongest proof yet that this design philosophy works.

Four Classes Down

With the completion of the Veilwalker, four of the fourteen planned base classes are now complete.

The Anointed explores restoration, compassion, and sacred aftercare. The Reveler transforms emotion into shared inspiration through Resonance. The Pactsworn builds power through dangerous bargains and supernatural patrons. Now the Veilwalker joins them as a master of hidden truths, emotional history, and perfectly timed opportunity.

Each class has pushed the design doctrine a little further. Each has challenged me to think about Desire in a different way. More importantly, each one has reinforced the idea that Erosia isn’t simply adding erotic themes to familiar fantasy. Desire is a mechanical pillar of the setting, shaping how characters fight, explore, negotiate, and grow.

There are still ten base classes waiting to be built, and each one presents its own design puzzle. If the Veilwalker taught me anything, it’s that the most memorable mechanics rarely come from asking what a class can do. They come from asking what makes that class see the world differently.

For the Veilwalker, the answer was surprisingly simple.

The world remembers.

Someone simply has to learn how to listen.