LUMINA Engine
日本語

PRODUCTION GUIDE

Prepare a LUMINA browser game for release

A game that works on Windows still needs browser-specific checks. Verify the complete generated output at the actual release URL and play through the game before publishing.

A production guide by ALC Software Laboratory. The referenced official manuals are listed at the end.

1. Prepare the complete browser output

If your development environment includes the build scripts and SDK, update the Windows staged output and run build-web.bat. A release ZIP may not include that build environment; follow its supplied documentation to obtain the required environment or a prepared browser build.

The standard output folder is build/web/bin. Serve the HTML, JavaScript and WASM together with the GameData packs, packlist.json and external movie files. Every file listed in packlist.json must exist.

build/web/bin/
├── lumina.html
├── lumina.js
├── lumina.wasm
├── lumina.ico
└── GameData/
    ├── packlist.json
    ├── data0.laf ...
    └── data8/ ...

2. Test over HTTP and publish over HTTPS

Open the game from an HTTP server rather than double-clicking a file:// HTML file. If serve-web.py is included in your development environment, the command below serves the build at http://localhost:8000/lumina.html.

Use HTTPS for the public site and a browser and device that support WebGPU. Verify that WASM is served as application/wasm, that large files and movies load reliably, and that required Range requests work correctly.

python serve-web.py

3. Check media formats and asset terms

A Windows OGV file alone does not establish browser movie support. Prepare browser-compatible media such as MP4 or WebM for referenced movies, and test both logos and in-game movies. Check that audio works after a user interaction.

Sample art, models and audio have separate terms from the engine. Check distribution permissions and credits, and keep authoring keys, source backups and personal save data out of the published package.

4. Play through at the actual release URL

After local Apache testing, check loading, title, choices, movies and the ending on the actual host. If deploying into a subfolder, verify that assets load from that URL.

Test on a PC and real Android hardware, on first and repeat visits, and with an older cache present. Narrow browser-width tests do not verify Android GPU, audio or memory behavior.

What to check

  • All listed GameData packs and movies load
  • Complete playthroughs are checked at the HTTPS release URL on PC and Android hardware
  • Repeat visits after an update and retry after errors are checked

Details and references