PRODUCTION GUIDE

Create your first ADV with LUMINA Engine

Start with dialogue and two choices that both reach an ending. Check file placement, text encoding and branching before adding artwork.

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

1. Find the GameData you will edit

Work in a project copy and edit the GameData beside the lumina.exe you launch. Check the source folder: generated distribution folders are replaced by later builds.

Create GameData/data0/scenario/first_dialogue.txt and save the example below as UTF-8. Each dialogue line starts with one actual tab character.

2. Write dialogue and a choice

This example references no extra background, character or audio assets. It assumes the supplied system configuration, including the message window and title.

choice goes to the label selected by the player; jump rejoins the shared ending. Commands begin at the start of a line, and dialogue begins with a tab. The example dialogue is shown in its original Japanese.

*start
msgshow
name "ナレーション"
	LUMINAで、最初のシーンを作ります。
choice "話しかける" *talk "周りを見る" *look

*talk
	こんにちは。ここから物語が始まります。
jump *finish

*look
	広場を見渡してから、歩き始めました。
jump *finish

*finish
	最初のシーンはここまでです。
end

3. Launch and test both branches

On Windows, run the command below from the folder containing lumina.exe to open this scenario without going through the logos and title.

Check that both choices reach the final line. For connecting the scene to the normal New Game button, follow the beginner manual chapters on the first scenario and title configuration.

lumina.exe --start-scenario=scenario/first_dialogue

4. Check these points if it does not work

Check for a doubled extension such as first_dialogue.txt.txt, confirm UTF-8 encoding, and make sure the EXE and edited GameData belong to the same folder. If the configuration loads an existing .lsf, update the encrypted script too.

In development mode, inspect lumina_debug.log for syntax line numbers and failed loads. A tab-indented line beginning with a command name can still be parsed as a command; see the message command when writing dialogue that may match a command.

What to check

  • Dialogue advances when clicked
  • Both choices reach the shared ending
  • Script conversion and rebuild steps are checked before distribution

Details and references