Ashborne Veil Devlog

Weekly Devlog - Foundations and Intent

1) What changed this week

This week was about locking foundations and sharpening intent.

After several rounds of alignment and polish, you focused on turning soft behaviors into hard rules. Input, combat, UI, and AI are no longer just cooperating - they are now governed by explicit ownership and priority.

The project crossed another subtle milestone: AshborneVeil feels authored.

Not just playable - deliberate.

You spent most of the week eliminating ambiguity: when an action starts, who owns it; when enemies engage, how long they care; when menus rebuild, where focus must land.

It is the kind of work players never see - but always feel.

2) Systems implemented or refined

Gameplay: Combat systems moved further into a rule-based model. You finalized clearer lifecycles for skills: Activation, Active window, Resolution / recovery. These phases now behave consistently across melee, projectiles, and area effects.

Input handling evolved into a true gesture arbitration layer: Tap vs double-tap is resolved centrally. Dodge, attacks, and skills compete under priority rules. Camera-plane intent fully drives movement and evasive direction. Instead of raw inputs triggering actions, gameplay now decides what wins.

You also refined animation commitment: short cancel windows preserve weight, late inputs are buffered intentionally, and combat timing aligns more closely with visual feedback. The result: control feels tighter without losing impact.

UI: You reinforced strict hierarchy: lists own expand/collapse logic, entries only expose state, and focus is always reassigned deterministically after rebuilds. Controller navigation is now stable across layers, eliminating ghost focus and unpredictable jumps. Visually, dark fantasy cleanup continued with reduced background noise, heavier framing, and cleaner separation between shadows and content.

AI: Enemy behavior advanced from memory into commitment logic. Threat handling now includes engagement linger after LOS loss, refresh on proximity and damage, and contextual decay instead of flat timers. Enemies no longer flicker between alert and idle. They choose to fight.

Tools / Pipeline: Dialogue and quest action nodes were expanded so narrative can directly trigger gameplay outcomes like healing, quest delivery, and conditional branching. Schemas remained disciplined with no ad-hoc fields and no shortcuts.

3) Content / world / lore progress

The world gained emotional coherence.

The prologue received more pacing and clarity around Garran's loss and motivation, making early narrative beats feel grounded.

NPC interactions now separate cleanly between ambient flavor lines, functional roles (vendors, healers, bounties), and quest-driven conversations.

Narrative progression is increasingly organized as a continuous journey rather than isolated test blocks.

Lore is no longer static. It is being staged.

4) Bugs, decisions, and trade-offs

Responsiveness vs weight: short animation commitments were kept instead of instant cancels.

Navigation freedom vs predictability: deterministic focus won.

Atmosphere vs legibility: darkness is now contextual, not global.

Simple wiring vs expressive control: gesture arbitration added internal complexity but simplified player experience.

Every trade leaned toward long-term consistency.

5) Next week's goals

Finalize combat arbitration across all player actions.

Normalize remaining skill timing edge cases.

Begin exposing early AI combat substates.

Continue prologue pacing and environmental storytelling.

First controlled dungeon atmosphere pass.

Closing

AshborneVeil is exiting its experimental phase.

You are no longer discovering systems.

You are defining laws.

And the game is starting to feel intentional.

Weekly Devlog - Deep Polish and Rule Setting

1) What changed this week

This week marked a shift from alignment to deep polish and rule-setting.

Instead of broad integration, you zoomed in on moment-to-moment feel: how the character starts an action, how long that action truly lives, and how clearly the game communicates intent back to the player.

Several systems crossed from working into designed.

The core theme was authority: deciding which system owns decisions-input, combat, UI, or AI-so behavior becomes predictable instead of accidental.

AshborneVeil is now entering a phase where mechanics are no longer just present; they are becoming intentional.

2) Systems implemented or refined

Gameplay: Combat received another refinement pass focused on skill lifecycle clarity. You formalized Activation phase, Active window, and Resolution / cleanup. This now applies consistently across melee, projectiles, and area skills, removing vague overlaps and edge-case behavior.

Player control was tightened further: dodge direction fully respects camera-plane intent; action buffering is clearer so late inputs do not unexpectedly override current animations; tap vs double-tap moved closer to a true gesture system with explicit arbitration.

A key internal rule emerged: Inputs propose actions. Gameplay systems decide. This model is steadily replacing reactive input wiring.

UI: Work focused on hierarchy and ownership. Lists own expansion logic, entries only report state, and focus is always reassigned explicitly after rebuilds. This removed ghost-navigation issues and made controller traversal deterministic.

Visually, dark fantasy framing became heavier, greenish undertones were reduced, and panels now feel more carved than painted. The interface is adopting the same philosophy as gameplay: fewer surprises, stronger structure.

AI: Threat logic advanced from memory into commitment. Enemies now maintain engagement after line-of-sight loss, refresh threat on proximity and damage, and decay attention contextually instead of by flat timers.

Tools / Pipeline: Dialogue and quest tooling expanded action nodes for healing, quest delivery, and conditional branches. Narrative data can now cause gameplay, not only display text, while schema discipline was reinforced for scalability.

3) Content / world / lore progress

The world gained emotional density.

Prologue sequences were refined to emphasize Garran's personal loss and motivation, making early narrative beats clearer and more grounded.

NPC interactions gained more purposeful dialogue flow, functional role clarity (vendors, healers, bounty givers), and stronger separation between ambient lines and actionable conversations.

Narrative structure kept moving toward chapter-like pacing, with smoother transitions between key campaign beats.

Lore is no longer only written-it is being staged.

4) Bugs, decisions, and trade-offs

Animation vs responsiveness: short cancel windows were chosen over instant overrides to preserve weight while keeping control tight.

UI freedom vs predictability: deterministic focus won over flexible navigation.

Darkness vs legibility: post-process effects became contextual rather than global, used to reinforce danger and enclosed spaces.

Each trade-off leaned toward clarity and intention over raw flexibility.

5) Next week's goals

Finalize gesture-based input arbitration.

Complete combat timing normalization across all skills.

Introduce early enemy combat sub-states (search / re-engage groundwork).

Further polish prologue pacing.

Begin first pass on dungeon-specific atmosphere controllers.

Latest entries