Why Early Access?

“VOLTWOOD is deep, complete-feeling and extensively tested — but a competitive tower defense lives or dies on how it FEELS in thousands of real hands across thousands of maps, and that is the one thing testing alone cannot answer. Early Access lets us tune the difficulty curve, par calibration, onboarding, and readability against real players and real maps before we commit to 1.0. The game already ships with a built-in feedback line — Early Access is how we use it. If you like sinking your teeth into a systems-rich defense game and want a hand in shaping its balance and pacing, this is the time to jump in.”

Approximately how long will this game be in Early Access?

“Six months to a year. The point of Early Access for us is to get the balance right according to the people actually playing the game, and to close any gaps they identify. We consider Voltwood near content-complete today: our 1.0 gate is balance and polish validated by real players across a wide range of maps, not a feature count.”

How is the full version planned to differ from the Early Access version?

“The full version is the finished, fully polished version of the game you are playing today — not a substantially different one. The core is all here: procedurally generated shareable maps, the par-based Torrent, the weekly roguelike Gauntlet and a casual mode, a deep roster of procedurally composed enemies and the fused weapon modules built to answer them, the multi-resource war economy, the Command Center, live leaderboards, and full localization in twelve languages. The road to 1.0 is polish and refinement within these systems, not new systems:

• Difficulty and par calibration tuned from real Early Access play data across many maps
  
• Onboarding and readability refined from first-time-player feedback
  
• We are happy to add new content if the community wants it: like new enemy types, weapon modules, heroes and hero abilities shaped by player feedback. The systems are data-driven and built to grow if needed.
  
• Presentation pass: visual evolution, late-game clarity, VFX polish
  
• Quality-of-life and accessibility improvements the community asks for

We do not plan to gate existing content behind 1.0, and any price change at launch will be announced ahead of time.”

What is the current state of the Early Access version?

“Fully playable start to finish: the full enemy roster and every weapon module implemented, all modes live (Torrent, the weekly Gauntlet, casual), daily and weekly maps, the full economy and Command Center, per-map, personal and per-mode leaderboards, a first-run tutorial, a Field Manual, Steam achievements and Cloud saves, full controller support, and complete localization in twelve languages. The systems are stable and covered by an automated architecture test suite. What we're actively refining is the FEEL — difficulty tuning across the full range of maps, the clarity of the opening experience, and the visual polish a premium tower defense earns.

One expectation to set up front: balance patches change how a wave plays out, so they retire runs recorded on earlier builds. A saved replay from an older build can no longer be watched, a shared Solution from one can no longer be verified, and a score still waiting to upload when you update is dropped rather than posted. This does not touch your progress, your achievements or your Cloud saves. Expect it to keep happening while we are still tuning — it is the cost of the balance work Early Access is for.”

Will the game be priced differently during and after Early Access?

“The price may rise modestly at 1.0 as polish and content accrue. Any change will be announced in advance, so Early Access supporters always get the better deal.”

How are you planning on involving the Community in your development process?

“We encourage the community to tell us about their experience by reporting bugs, suggesting changes and helping to shape the vision for how Voltwood can become the best it can be. Player feedback will be critical to delivering the 1.0 release of Voltwood.

Where we will talk to you, and what each channel is for

• Dev updates — on this page and inside the game. Every build ships with written patch notes: posted to the Steam news feed, readable in-game under Patch Notes, and archived on our website. When a change came from a player report, the notes say so.
  
• Talking to us — the Steam Community Hub. The discussion boards are the main room: strategy, balance argument and questions. This is the channel we check first.
  
• Bugs and feature requests — the in-game feedback button. One click from anywhere in the game, and it attaches the map ID, wave and build version automatically, so we can reproduce exactly what you saw instead of guessing at it. The boards work fine for these too — the button is just the fastest route, not a rule.

How often
Every build we release ships with written notes — in the game, on the Steam news feed, and on our website. That is not just an intention: our build process will not produce a release that has no patch notes attached to it.

So you hear from us every time we ship a patch or a game update, and again whenever we reach a significant development milestone. When a change came from a player report, the notes say so.

What you can shape
The feedback we most need is about how the game balances:

• Balance and par. Every battlefield is procedurally generated from a shareable map ID and scored against a par target, so "this map is unfair" is a report we can act on precisely: send us the map ID and we can regenerate the exact battlefield you played and retune against it. All balance in Voltwood lives in data catalogs rather than in code, so a well-argued report can move numbers in the next patch instead of the next milestone.
  
• Modules against enemy types. Whether a weapon module actually answers the thing it is meant to answer, and which enemy compositions leave you with no good tool.

Beyond that, everything is open: enemy types and composition, module types, cards, champions, heroes and villains, the Gauntlet, leaderboards and scoring, map IDs, replays, onboarding and readability — and ideas for where the game should go next, including expansions. We would rather hear an idea than not.

We will not implement every suggestion, and we would rather say so than pretend otherwise. What we will do is consider each one properly, and tell you what we decided.

How we will run it

• Every report gets a disposition. We keep a triage log of every bug and idea that reaches us, and each one is either fixed or answered with the reason it was not. Nothing is silently dropped.

”