From the Workbench

Devlog

Concrete notes from Duskvein's early development: what is being shaped, what is being cut, and what still needs to earn its place.

The First Vessel

Before Duskvein can become a large roguelite, it has to survive one honest minute of play.

The current goal is deliberately small: enter the arena, move with confidence, let the first weapon fire automatically, read the enemy pressure, collect a reward, and restart without friction.

  • Movement first: acceleration should feel responsive, but not weightless.
  • Auto-attack clarity: weapons should tell you their range and cadence before numbers are needed.
  • Restart speed: death is part of the structure, so the path back into a run must be short.

Bloodlines Without Busywork

The bloodline system is the heart of Duskvein, but it has to be more than permanent power with darker naming.

A vessel dies, the curse continues, and the next vessel carries something forward. The design danger is simple: if everything carried forward is just a stronger number, death becomes accounting.

  • Inherited traits: small run-shaping modifiers that push builds without solving them before the run starts.
  • Scars: consequences from failure that create texture.
  • Clean choices: fewer, sharper decisions between runs.

Dusk Horror You Can Still Read

Duskvein should look cursed, but the arena can never become a dark soup of beautiful mistakes.

The visual target is dusk horror: bone, ash, oxblood, ruined gold, and silhouettes that feel older than the player. That mood matters, but a bullet-heaven game lives or dies by readability.

  • Readable silhouettes: enemies need distinct outlines before detail work matters.
  • Controlled glow: red must be saved for danger and high-value moments.
  • UI restraint: gothic flavor belongs in framing while HUD elements stay scannable.