
First, thank you to everyone who has purchased, played, reviewed, reported problems, or shared suggestions during Veilscripture’s first few days after release.
Some of you have already spent an astonishing amount of time with the software and provided detailed feedback based on real, extended use. That has been both encouraging and extremely useful. It has also made one thing clear: I should communicate development plans and ongoing work more regularly.
This post therefore marks the beginning of a more visible development log for Veilscripture.
My immediate focus will be on launch-related bug fixes, compatibility problems, and improving the overall onboarding experience.
Veilscripture AI is less a single-purpose application than an interconnected ecosystem of tools and systems, and some parts of that ecosystem are not yet explained as clearly as they should be. I will therefore be expanding the user manual and creating better tutorial materials so that new users can understand the intended workflow without having to discover everything through trial and error.
The short-term priorities are:
Fixing launch bugs and compatibility issues
Improving error messages and troubleshooting information
Better user manual
Creating clearer tutorials and introductory materials
Every future public build will also receive proper patch notes, including smaller bug-fix updates.
Once the most urgent launch issues and documentation work are under control, I intend to return to feature development and broader interface improvements.
Several useful ideas have already emerged from early users. One is better control over the characters included in a Scene Card. The current design distinguishes between Major and Minor characters, but larger recurring casts would benefit from quicker controls for changing those roles and temporarily hiding or excluding characters when they are not active in the current scene.
Features currently being considered for the mid-term include:
Quick Major/Minor character swapping inside Scene Cards
Controls for temporarily hiding or excluding inactive characters
General interface and workflow improvements
More fine-grained control over the Memory Bank
User data input and control
The exact implementation may change as I test these ideas. I would rather solve the underlying workflow problem properly than add several confusing controls too quickly.
The largest confirmed long-term additions are further localizations.
Chinese localization is planned as a major future update, followed by Russian localization. Both involve more than simply translating interface text, particularly because Veilscripture includes prompts, documentation, model-related guidance, and language-sensitive systems that need to behave coherently.
These updates will therefore take time, but they remain an important part of the long-term plan.
To speak frankly, Veilscripture has had a very quiet commercial launch.
The early users who found it appear to be engaging with it deeply, which is enormously encouraging. The problem is that very few people currently know the software exists. Because of that, I will need to devote part of my time in the coming weeks to creating videos, demonstrations, tutorials, and other marketing material.
This does not mean development has stopped. It means that development and visibility now need to proceed together. For Veilscripture to grow and support continued development over the long term, however, it cannot remain invisible.
For those of you who already enjoy Veilscripture, telling other potentially interested people about it would genuinely help. That might mean mentioning it in a relevant Discord community, sharing it on Reddit, showing it to a friend interested in AI roleplay, or simply leaving an honest Steam review.
Obviously you don't need to spam unrelated communities. But as the creator of this software, I genuinely believe that I've made something unique and I wish to share it with the world.
I will create a dedicated discussion thread for feature suggestions and keep a pinned development-status post updated as plans change.
Not every suggestion will be implemented, and items mentioned in a roadmap are not promises of a particular release date. However, I will try to provide clear responses when an idea is being considered, planned, rejected, or completed.
Veilscripture remains under active development. Thank you for being here at the beginning—and especially to those of you who have already spent many hours exploring what it can do.