Veilscripture AI news & patch notes

Antivirus False Positives

A small number of users have reported that certain antivirus programs may flag files included with Veilscripture AI.

The reports received so far appear to be false positives caused by the way some Windows components are compiled and packaged. This can occasionally happen with newly released independent software before its files have accumulated enough reputation within antivirus databases.

The affected files are part of the official Veilscripture installation distributed through Steam.

As the developer, I can assure you that Veilscripture AI does not contain malware, cryptocurrency miners, telemetry, or hidden background services.

Security and user trust are particularly important to me because I designed Veilscripture around private, local AI use.

What You Should Do

Please do not disable your antivirus protection globally.

If your antivirus flags a Veilscripture file, please:

• Confirm that Veilscripture was installed directly through Steam.

• Record the name of the antivirus program.

• Record the detection or threat name shown.

• Record the exact filename that was flagged.

• Take a screenshot of the warning, if possible.

• Report the information in the Veilscripture Steam Discussions support forum.

If you encounter this issue but would still like to use Veilscripture in the meantime, you can restore the flagged file from your antivirus quarantine.

However, this is ultimately a matter of personal trust, and I completely understand if you would rather wait until the detection has been reviewed.

You can also verify the installation through:

Steam Library → Veilscripture AI → Properties → Installed Files → Verify integrity of game files

What I Am Doing

I am currently working to reduce these detections by:

• Submitting affected files to antivirus vendors for review.

• Improving the build and packaging process where possible.

• Completing code-signing arrangements for future builds.

• Monitoring reports involving different antivirus products and detection names.

Reports containing the exact filename and detection name are especially helpful, since antivirus vendors usually need to review each affected file individually.

At the same time, I don’t want this review process to bring development to a standstill. I will continue working on bug fixes, compatibility improvements, and planned features while the affected files are being reviewed.

Some of these corrections may take time, particularly while Veilscripture AI is still a new application and its files are building reputation with antivirus systems.

I apologize for the inconvenience, and I appreciate your patience while I work through the process.

Thank You

Thank you to everyone who has reported this issue and provided detailed information. I will continue reviewing reports and will update this notice if there are any significant developments.

Feature Updates

Bug Fixes

Bug Fixes

Feature Changes

What Comes Next for Veilscripture

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.

Short-Term Priorities

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.

Mid-Term Development

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.

Long-Term Plans

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.

A Few Personal Words from the Developer:

About the Launch

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.

To my Early Users

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.

Suggestions and Communication

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.

Available at launch

• Character and scene creation

• Long-term memory with dedicated Memory Bank

• Veil Atlas world-building tools

• Local text-to-speech

• Story and conversation export

• Secure remote access on your phone

• Steam Workshop support

• Extensive prompt and model controls

You can try the free demo or purchase the full Creator Edition from the Steam store page.

Thank you to everyone who followed the project, tested the early builds, offered feedback, or simply waited patiently for release.