Skip to main content
Avoxar official logo

Roadmap

Development roadmap

A public view of what is complete, what is being built now, what comes next, and what is planned later for Avoxar.

Progress

4 of 15 roadmap items completed

27%

Done

Completed foundation work that gives Avoxar a clear public base.

4 items
  1. 1

    Logo and initial identity

    The first Avoxar logo and visual direction are in place.

  2. 2

    Website foundation

    The official site structure, core routes, metadata, and public assets are ready.

  3. 3

    Voxel studio foundation

    The internal toolset already includes modes for scene building, object building, character building, animation, game UI, paint assets, and game data.

  4. 4

    Runtime data pipeline

    The game project has API-backed records for maps, characters, scene play, game assets, UI screens, sound assets, and player sessions.

Now

Active work focused on turning the project into a playable prototype.

4 items
  1. 1

    Voxel gameplay runtime

    Connect voxel maps, player spawn, scene play config, runtime loading, and WebSocket session state into one playable path.

  2. 2

    Combat and skills

    Tune health, hitboxes, attack radius, attack power, attack speed, skill loadouts, animation roles, and sound hooks.

  3. 3

    Map enemy setup

    Test monster pools, spawn intervals, max-alive limits, spawn radius, difficulty tier, enemy level, and reward configuration.

  4. 4

    Devlog updates

    Publish progress notes that explain what has moved from internal tooling into playable systems.

Next

Near-term goals after the first prototype loop is stable.

4 items
  1. 1

    Internal playable build

    Prepare a build that enters a scene, loads the player, renders the voxel world, plays UI/audio, and exercises combat rules.

  2. 2

    Screenshot and trailer capture

    Capture representative media from real voxel maps, characters, UI, and combat testing when visuals are stable.

  3. 3

    Feedback system

    Create a structured way for players to report issues and suggestions once a testable build exists.

  4. 4

    Community launch

    Open official community channels with clear guidelines.

Later

Longer-term goals that become relevant after the demo path is clearer.

3 items
  1. 1

    Steam page

    Prepare store presence, capsule assets, screenshots, and wishlist flow.

  2. 2

    Public alpha

    Expand testing beyond the first demo once core systems are stronger.

  3. 3

    Supporter build

    Evaluate early supporter access after build distribution is stable.