Three of us answer this inbox. Most questions are answered within 48 hours, weekdays only — Saoirse and Tobias share the inbox. If your question is in the FAQ below, you'll get a faster answer there. If it isn't, write directly.
If something isn't here, write to us — we add what people ask about. Most categories below are pinned and updated as the game changes through closed beta and launch.
Q3 2026. The exact date will be announced eight weeks ahead of release. A demo lands September 2026 as part of Steam Next Fest. If you want the demo key the day it ships, sign up on the home-page reminder list.
Game · ReleaseSteam Deck is verified at PC launch. A Switch 2 port is in scope but not yet announced; we'll have a port team confirmed by mid-2026 and an announcement to follow. PlayStation and Xbox are post-launch conversations we have not yet started.
Game · PlatformsYes. Universal binary for Apple Silicon (M1+) and Intel Macs at launch. Tested on macOS 12 through 15. M-series performance is excellent — we routinely hit ultra settings on M1 Pro at 1440p / 60.
Technical · PlatformsSix to nine hours for the main story; eighteen plus hours for full completion across the seven endings. The game is non-linear in path but linear in time — you choose the order and the route through the city, but you progress through seven nights regardless.
Game · DesignTwo-player online co-op, drop-in & drop-out, with shared world progression. Designed so two friends can play start to finish in their own world, but optimized for asymmetric pacing — one of you can be in act two while the other catches up. No PvP, no arena modes.
Game · MultiplayerYes. Cloud-synced saves across Steam ↔ Epic ↔ macOS. Save format is open and stable; once you finish the game we publish the save spec on the studio Github so the community can build save-editors. ~/.veilspire/saves/.
17 settings across motion, audio, visual, and input categories. Color-blind modes (protanopia, deuteranopia, tritanopia), high-contrast UI, full subtitle customization, audio-cue captions for the reactive score, motion-reduction toggles, full key remapping. Two of our cofounders had explicit accessibility needs in mind from day one.
AccessibilityPartial. The menus and the codex are screen-reader compatible. The game itself is heavily audio-driven by design (Tobias's reactive engine), but is not fully audio-playable end-to-end. The community has built a tool for blind players that fills some of the gap; we link to it from the in-game accessibility panel.
AccessibilityRefunds are handled by the storefront — Steam's two-hour / fourteen-day window applies on Steam, GOG's thirty-day on GOG, etc. If a refund is denied by the platform but you feel you have a genuine technical reason, write to us at support@cinderlight.gg and we will help.
Yes. VEILSPIRE is self-published across PC and macOS. We've been approached by publishers but the studio's operating decision is to retain control of the launch window, the marketing voice, and the IP. A publisher may be the right partner for a console port; that conversation is open.
Business · PublishingYes — a 47-minute studio mix at launch, plus an extended 78-minute "reactive variations" album six weeks after. Both will be on Bandcamp, Spotify, Apple Music, and a limited 180g vinyl run pressed by Lisbon Vinyl Co. (numbered, 750 copies). Pre-orders open at the demo.
Game · MusicYes — please. The game's full content is monetization-cleared for streamers and YouTube creators. We will publish a "no-spoiler chapter list" with the demo so you can mark your videos. If you have a channel of any size and would like a pre-release key, write to creators@cinderlight.gg.
We don't run a ticketing system or a chatbot. The address you write to determines who replies. Saoirse handles general inquiries on weekdays; Tobias covers technical bugs and engine questions; Paweł picks up art-direction and license questions for environments and key art.
If you've found a bug, please include your platform, build version (Steam Properties → Betas → Edition), reproduction steps, and a screenshot if applicable. The more your message reads like a bug report, the faster you'll get a fix.