Studio v0.2.0
Studio v0.2.0 · Product manual

Build and deliver a Windows game

Set your Windows visual novel's name, icon and EXE entry point, choose a signing option, check and build the standalone Player, and deliver the complete release directory.

A Windows release contains a standalone Player and the work. Players run its entry program inside the complete release directory. Studio applications and installers serve authoring; the work release serves players.

1. Set the work identity

  1. Import the work icon into the asset library. Open Publishing and choose Windows.
  2. Expand Work name, icon & Windows identity. Enter the name, release version, executable filename and publisher, then select the icon. For example, use example.exe as the entry filename.
  3. Enter a valid .exe filename; Chinese names are supported. Choose its directory separately under Output directory.
  4. Choose Apply work identity, review and save all. Name/icon changes retain the current work’s save identity.

2. Choose signing

Leave unsigned produces an unsigned receipt. For author signing, choose Sign with a local certificate, load local signing certificates and review the subject, expiry and fingerprint suffix under Certificate for this release.

The list reads valid code-signing certificates with private keys from the current Windows user’s certificate store. The selection belongs to local build options; the project retains its work identity and signing policy. Obtain your certificate through your certificate provider and prepare it using Windows certificate management.

Signing failure stops the build and preserves the preceding release. Read signature status, identity and system trust in the receipt. A self-signed certificate may have a valid signature while remaining untrusted. Open Properties → Digital Signatures on the entry EXE to inspect it.

3. Check and build

  1. Choose a dedicated empty directory such as D:\Releases\spring-0.1.0-windows, or an existing release of this work and target.
  2. Choose Check and build, or use Check only to review exact dependency, asset and font issues first. Review and save changes, then check again as needed.
  3. The builder writes the work name, entry filename, icon and PE product information before applying the selected signature.
  4. Read the receipt, open the output and find the configured EXE, such as example.exe. Launch it from this complete directory to try Home, story and save/load.

Recheck after changing the target, identity, certificate or other build options. Rebuild when Not built for current settings appears. If Local trial shows Not executed, launch the output using that action.

4. Deliver the directory

Archive the complete output. Players extract it and run its EXE alongside the runtime, snapshot, assets, fonts and licences. Before updating, players can export their profile under Settings → Data. See Publishing and Player for compatibility and import.

Other targets: Web · Android · iOS.