DEV Community: HALO

GOKI2 Gameplay: ModBookmark & KAG3 Variable System for Data Persistence

HALO — Fri, 01 May 2026 23:45:39 +0000

Download

Avalanches & GOKI2 can download the latest environment from the Assets link of Avalanches-GOKI2-Release2.x.y.y.zip based on the release tag on the following site (written as Avalanches (GOKI2) release version 2.x.y.y).

https://github.com/halo1234/Avalanches/releases

ModBookmark and ModSnapshot

ModBookmark is a module related to save data.
ModSnapshot is a module related to snapshots.

First, load the modules.

; Snapshot feature
@load_module name=ModSnapshot
; Bookmark feature
@load_module name=ModBookmark

With this, snapshot and save data features are incorporated.

Setting the Save Data Format

First, set the format for save data.

@bookmark format=bmp24 width=150 height=auto keep_aspect_ratio mode=z quick=quick store_skipping

Let's go through it step by step. First, format=bmp24 specifies bmp24 for the format attribute. Other options include bmp32/bmp8/bmp (same as bmp32). This means that a thumbnail will be included in the save data.

Next, we specify the size of the thumbnail with width=150 height=auto.
The width is set to 150, and the height is calculated automatically.

We specify keep_aspect_ratio to fix the aspect ratio of the thumbnail.
When this attribute is specified, the size is calculated while maintaining the aspect ratio.

mode=z specifies the format in which the data is saved.
Specifying z compresses the data.
Specifying c encrypts the data.
Both cannot be specified at the same time.

quick=quick specifies the name of the so-called quick save data.
If a quick save is performed, the data is saved under the name specified here.

store_skipping specifies whether to store save data during skipping.
This functions as a hint for speeding up.
If you set this attribute to true, save data will not be stored during skipping.
This can thus provide faster skipping.
However, when stopping at an s tag, for example, it is necessary to store the final state of the save data.
Including force_store in the name of a savable label allows save data to be stored even if this attribute is true.
For instance, when using choices, the following method is recommended:

*force_store|
@select caption=Choice 1 target=*choice1
@select caption=Choice 2 target=*choice2
@select show
@s

By doing this, even if store_skipping is true, the save data will be forcibly stored by force_store during skipping.

Thumbnails

The thumbnail module manages the capturing and releasing of snapshots. Normally, it is a module you don't need to pay particular attention to.

You can also manually take snapshots.

; Capture a snapshot of the current screen
@lock_snapshot
; Release the snapshot
@unlock_snapshot

If the number of calls to lock_snapshot and unlock_snapshot does not match, malfunctions may occur. You will probably rarely use this tag directly.

Variable Areas

The variable areas managed by ModBookmark include three areas: user variables, system variables, and temporary variables. User variables are stored in save data. System variables are stored in system save data. Temporary variables are disposable variables that can be used temporarily and are not saved to files. This design is the same as KAG3.

The contents stored in user variables are saved in each save data. To store a value in a user variable, do the following:

@eval exp="f.testVal = 99999"

The contents saved in system variables are stored in the system save data. The system variable area stores settings that affect the entire game. For example, information such as whether the game has been cleared is not very meaningful to save in individual save data. It is used in cases where you want to access the same information regardless of which save data is loaded. The actual script for saving a value in the system variable area is as follows:

@eval exp="sf.gameClear = true"

As the name suggests, temporary variables are a variable area used temporarily. Since they are not saved, they are used when you just want to temporarily store a value. They are not saved, so the information is lost when the game is restarted. The usage is as follows:

@eval exp="tf.tempVal = 'string'"

Return to Previous / Return to Title

The "Return to Previous" and "Return to Title" functions are also managed by ModBookmark. The Return to Previous function uses the record and go_back tags. The record tag saves the state of the last savable label before it was written. The go_back tag returns to the previous state.

The function to return to the title uses the start_anchor tag and the go_to_start tag.

The start_anchor tag saves the state of the previous saveable label before it.

The go_to_start tag returns to the location where start_anchor was written (the previous saveable label).

For example, you would write it like this:

*game_start|
@start_anchor

Normally, returning to the previous point or back to the title would be done by the user from the menu.

Dialog

In ModBookmark, you can display a confirmation dialog to the user when performing actions like returning to the start or saving.

If you want to use original images in the dialog, it is recommended to use the ask_save, ask_start, and ask_record tags.

These tags allow you to specify images for each UI.

For the values to assign to each attribute, please refer to the manual (/doc/goki2/index.html).

If you do not use these tags, the default UI will be used.

Expanding Gameplay with GOKI2 [Introduction to ModSelect] Implementing Branching Scenarios and Choices with ModSelect

HALO — Fri, 24 Apr 2026 22:17:51 +0000

Download

https://github.com/halo1234/Avalanches/releases

Choices

In the previous "Introduction to ModADV" series, we completed the basic screen settings that make up a game. From this point on, we will start a new series that dives deeper into the "gaming experience"!

The first installment explains the choice function (ModSelect), which allows you to implement "scenario branching," the core appeal of ADV (adventure games).

There is a module called ModSelect that manages choices. First, load the module.

; Choices
@load_module name=ModSelect

Now you can use choices.

Choice Settings

You can preset various sound effects and button sizes for choices. As an example, we will use the following settings:

@select_option base_left=10 base_top=10 base_left_step=80 button_width=70 button_height=40

Let's go through them one by one. base_left=10 base_top=10 specifies where the choices will start. Here, the first button is placed at position (10, 10).

base_left_step=80 specifies that the next choice will be displayed 80 pixels away from base_left. Although not specified here, there is also a base_top_step attribute. Set it if necessary.

Finally, button_width=70 button_height=40 specifies the size of the buttons.

This completes the choice settings. If necessary, you can also specify sound effects, so please refer to the manual.

By the way, to specify sound effects, you will need to separately load ModSound.

Creating Choices

You can write choices at any point in the scenario script. Choices are placed on the background layer rather than the message layer (more precisely, on a choice-specific layer with the primary as the parent).

You can create choices at any point in the scenario as follows:

@select caption="Choice 1" target=*choice1
@select caption="Choice 2" target=*choice2
@select show
@s

You will write the select tag for the number of choices you have. Specify the caption of the choice in caption. Specify the label name to execute when selected in target. You can also specify the scenario storage in storage.

Once you have created the choices, they will be displayed and paused. Use select show to display the choices and s to pause.

Finally, define the labels that will be executed when a choice is selected.

*choice1
You chose Choice 1.
@s

*choice2
You chose Choice 2.
@s

Currently, when a choice is executed, it will show the execution content and then pause, but in practice, you will likely write some other tags.

Now you can use choices.

Was that too simple this time? Choices are an important feature for implementing gameplay. Please make sure you can use them proficiently.

ADV Development with GOKI2 [ModTitle Introduction]: Implementing the Title Screen and Defining Button Layouts

HALO — Sat, 18 Apr 2026 08:27:52 +0000

Download

https://github.com/halo1234/Avalanches/releases

Title Screen

In GOKI2, ModTitle implements the title screen.
First, load the module.

tjs:/src/goki2/system/construct.gs ; Title Screen @load_module name=ModTitle`plaintext
Now the title screen is available.

Title Screen Settings

First, specify the sound effects.

@title_option click_sound=se001.ogg enter_sound=se002.oggplaintext
Here, we specify the click sound and the sound effect for mouse enter.

Title Screen Layout

The title screen can have five buttons: "Start," "Load," "CG/Recollection," "System," and "Exit."
For example, you can do it like this:

@title_screen start_caption=Start start_left=370 start_top=400 start_width=60 start_height=20 start_target=*start
@title_screen load_caption=Load load_left=370 load_top=430 load_width=60 load_height=20
@title_screen cgmemory_caption=CG/Reminiscence cgmemory_left=370 cgmemory_top=460 cgmemory_width=60 cgmemory_height=20
@title_screen system_caption=System system_left=370 system_top=490 system_width=60 system_height=20
@title_screen exit_caption=Exit exit_left=370 exit_top=520 exit_width=60 exit_height=20 exit_target=*exit

The start and end options require specifying the scenario storage and label name to execute when selected.
Otherwise, the screen display will be executed directly internally.

Let's look at each option using the start option as an example.

start_caption=Start specifies the button's caption.
This is mostly unnecessary if you're using an image for the button.

start_left=370 start_top=400 start_width=60 start_height=20 specifies the button's position and size.

start_target=*start specifies the label name to execute when Start is selected.
If the scenario storage is omitted, the scenario storage at the time title_screen show is called is assumed to be the one specified.
This attribute is only valid for Start and End.

Displaying the Title Screen

After configuration is complete, display the title screen at any time.

@title_screen show @s`plaintext
After displaying the title screen, stop using the s tag or similar.

Events

When the Start and End buttons are pressed, they execute the specified scenario storage and label.
For example, like this:
*exit @close !ask *start @go_to_start !ask
In this case, the start label simply returns to the start, but in reality, it's better to use the *que** tag in the default tags to execute the next scenario.

In Conclusion

We've written a series of articles up to this point, and I think we've finished setting up most of the screens.
From here on, there's a long road ahead where we'll be diligently writing scenario scripts.
However, if you've followed the articles this far, you should be able to overcome this long road.
In the next articles, we'll explain how to implement the game parts, such as choices and video playback.

ADV Development with GOKI2 [ModCGMemory Intro]: Implementing CG/Recollection Mode and Data Management via Excel

HALO — Sat, 11 Apr 2026 04:39:04 +0000

Download

https://github.com/halo1234/Avalanches/releases

CG/Reminiscence

In GOKI2, ModCGMemory implements the CG/Reminiscence screen.

First, load the module.

; CG/Reminiscence screen
@load_module name=ModCGMemory

With this, the CG/Reminiscence screen can be used.

CG/Reminiscence Data

First, you need the data for the CGs or reminiscences to be shown on the CG/Reminiscence screen.

In Avalanches, you can input the data using Excel.

First, please open the following file.

/src/data/cgmemory/list.xlsx

For now, the default content is as follows.

Do not edit the headers. (Strictly speaking, it is okay to edit them, but there is a procedure, so it will be omitted here.)

thum_CG_A is the file name of the thumbnail.

Do not enter the extension.

CG_A000/CG_A001 are the file names of the CGs to be displayed on the screen.

Do not enter the file extension here either.

Specify one file per line for each CG.

ModImageTest specifies the scenario file name to be played back as a replay.

Do not enter the file extension here either.

The sheet name will be the output file name.

You can add as many sheets as you like, so for example, if you want to switch CG screens for each character, it is good to separate the sheets.

Data Output

There is a tool that converts the input Excel data into a format that Kirikiri can read.

If you enter data into the default /src/data/cgmemory/list.xlsx, you can use the following batch as it is.

/tools/make_cgmem/run.bat

If you change the file name or create an Excel file from scratch, you need to update the batch contents to the new file path.

Running /tools/make_cgmem/run.bat will generate *.dic files from Excel.

Execution screen

By default, the following two files are generated:

main.dic

sub.dic

Copy the generated files to the project folder.

You can copy them to any folder that is included in the automatic search path.

CG/Recall Screen Layout

We will write the GOKI2 script.
First, we will load the CG/recall data we created earlier.

@load_cgmemory key=halo storage=ハロ.dic
@load_cgmemory key=2nd storage=2番目のCG

The key attribute and storage attribute are required attributes.
Be sure to specify them.
The key attribute should be any string that serves as the data key.
The storage attribute specifies the generated CG/recall data.
The file extension is optional.

Next, we define the UI.

@cgmemory_option item_width=120 item_height=120
@cgmemory_option blank_thumbnail=thum_blank memory_button=memory_button
@cgmemory_option item_count=8 memory_count=3

First, item_width=120 item_height=120 specifies the size of each item.
This is the size that will contain the CG thumbnail and recall button.
Next, blank_thumbnail=thum_blank memory_button=memory_button specifies the images for the thumbnail (unopened) and the recall button.
Please refer to the manual for image formats.
Finally, item_count=8 memory_count=3 specifies the number of items per page and the number of recall buttons.

There were two CG/recall data created initially. We will place buttons to select each of those data.

@cgmemory halo_left=370 halo_top=270 halo_caption=Halo's CG halo_width=60 halo_height=20
@cgmemory 2nd_left=370 2nd_top=300 2nd_caption=2nd's CG 2nd_width=60 2nd_height=20

Here, the value of the key attribute specified in load_cgmemory appears. Each attribute is specified in the format key_xxx. For instance, for the left position attribute of Halo's CG button, it is halo_left.

The recall buttons will be displayed below the CG thumbnails.

@cgmemory mem0_left=10 mem0_top=100 mem1_left=30 mem1_top=100 mem2_left=50 mem2_top=100

This specifies the positions of the CG thumbnails.

@cgmemory item0_left=20 item0_top=10
@cgmemory item1_left=160 item1_top=10
@cgmemory item2_left=300 item2_top=10
@cgmemory item3_left=440 item3_top=10
@cgmemory item4_left=20 item4_top=200
@cgmemory item5_left=160 item5_top=200
@cgmemory item6_left=300 item6_top=200
@cgmemory item7_left=440 item7_top=200

It is indicated as itemN_xxxx, but this N can be specified from 0 up to the number specified in cgmemory_option item_count=8 minus 1. Here, it will be arranged in 4 columns and 2 rows.

With this, the CG/recollection screen has been defined.

Registering CGs

If entered in Excel, the CG file name will be automatically registered. To open it, use the load_cg tag to display the CG.

@load_cg layer=cg_layer_0 storage=CG_A001.png visible

If you use the above tag to display the CG, it will open in the CG/recollection screen.

Recollection Script

You need to specify the script range that will be played in recollection (from which part of the script to which part is recollection). First, write the open_memory tag at the starting position. Keep in mind that this tag must be written immediately after some label. The ending position can be specified arbitrarily using the end_memory tag.

*label|
@open_memory

[Hello] This is during recollection.

[Hello] It's ending.

@end_memory

With this, you have specified the recollection range. Once the script enclosed by this tag is executed even once, the button will be activated on the CG/recollection screen.

Starting ADV Development with GOKI2 [Introduction to ModSaveLoad/ModSystemButtons] Layout of Save/Load Screens and Placement of System Buttons

HALO — Sat, 04 Apr 2026 23:31:40 +0000

Download

If you are interested, you can download the latest environment from the link in the Avalanches-Release2.x.y.y.zip in Assets from the release tag of the following site (Avalanches release version 2.x.y.y).

https://github.com/halo1234/Avalanches/releases

Save/Load

In GOKI2, the ModSaveLoad module implements the save/load screen.
First, load the module.

; Save/Load Screen
@load_module name=ModSaveLoad

Now, the save/load screen can be used.

Save/Load Screen Layout

We will arrange the UI for the save/load screen, but first, define the area where the UI will be placed.

@save_load_option client_left=10 client_top=10 client_width=780 client_height=580

This sets the UI placement area from (10, 10) to (780, 580).

Next, set the size of a record.
One record corresponds to one save data.

@save_load record_width=780 record_height=140

Now, the record is defined.
Next, we will continue to place the UI within the record.

@save_load index_left=10 index_top=60
@save_load date_left=180 date_top=10
@save_load summary_left=180 summary_top=30

From top to bottom, this specifies the positions of the index, date, and summary. The summary displays the last shown text (more precisely, the content output to the message layer). If nothing is set here, nothing will be displayed for the records.

Finally, you define the thumbnail. (You don’t have to specify it if unnecessary.) You can specify the position and size, as well as the background color when blank.

@save_load thumbnail_left=30 thumbnail_top=0 thumbnail_width=150 thumbnail_height=120 thumbnail_color=0xFF0000

With this, the save/load screen is complete.

System Buttons The system buttons familiar from ADV games are implemented with ModSystemButtons. First, load the module.

goki2:/src/goki2/system/construct.gs ; System Buttons @load_module name=ModSystemButtons

Now the system buttons can be used. ### Placing System Buttons Next, place the system buttons on the screen.

; System Buttons
@system_button log_left=10 log_top=390 log_width=60 log_height=20 log_caption=History
@system_button skip_left=80 skip_top=390 skip_width=60 skip_height=20 skip_caption=Skip
@system_button auto_left=150 auto_top=390 auto_width=60 auto_height=20 auto_caption=Auto
@system_button hidden_left=220 hidden_top=390 hidden_width=60 hidden_height=20 hidden_caption=Erase
@system_button system_left=290 system_top=390 system_width=60 system_height=20 system_caption=System
@system_button save_left=360 save_top=390 save_width=60 save_height=20 save_caption=Save
@system_button load_left=430 load_top=390 load_width=60 load_height=20 load_caption=Load
@system_button qsave_left=500 qsave_top=390 qsave_width=60 qsave_height=20 qsave_caption=Quick Save
@system_button qload_left=570 qload_top=390 qload_width=60 qload_height=20 qload_caption=Quick Load

For now, let's take a look at the definition of the "History" button.

First, specify the button's position with log_left=10 log_top=390.
Next, specify the button's size with log_width=60 log_height=20.
Specifying the size is not necessary if you use an image for the button.
Finally, specify the caption with log_caption=履歴.
With this, the History button has been defined.

Other buttons are defined in the same way, specifying their position, size, and caption.
For the available buttons, please refer to the manual (/doc/goki2/index.html).

Displaying the System Buttons

Finally, display the system buttons defined with the following tag:

@system_button_option visible

To hide them, execute the following tag:

@system_button_option !visible

Starting ADV Development with GOKI2 [ModSystem Introduction] Building System Screens and Defining Configuration Items

HALO — Sun, 29 Mar 2026 00:32:18 +0000

Download

https://github.com/halo1234/Avalanches/releases

System Screen (ModSystem)

Normally, games have a system screen to change settings and such.
ModSystem is what implements that.

Building the System Screen

When you load ModSystem, several tags become available.
Building the system screen is done with the system tag.
For now, we will continue the explanation using GOKI2's default buttons and sliders without images.
It is also possible to use images. (In the manual, the <id>_storage attribute is the item where you specify the image file)

Setting the Page Size and Other Properties of the System Screen

First, set the position and size of the page.
After that, specify things like the sound effect for clicks.

@system_option page_left=0 page_top=30 page_width=800 page_height=570 click_sound=se001.ogg enter_sound=se002.ogg

ページ定義

システム画面は、ページ単位で構築する事になります。
まずは、ページ0を定義します。

@system page=0 page_tab_caption=システム page_tab_left=0 page_tab_top=0

Page 0 has been defined with this.
The display name is 'System'.

Setting Item Definition

Next, let's make it possible to adjust the sound volume.
Add a slider to page 0 as shown below.

@system page=0 master_left=400 master_top=10 master_caption="Master Volume" master_slider_left=530 master_slider_top=10 master_slider_width=160 master_slider_height=20 master_slider_color=0xFF0000
@system page=0 bgm_left=400 bgm_top=40 bgm_caption="BGM Volume" bgm_slider_left=530 bgm_slider_top=40 bgm_slider_width=160 bgm_slider_height=20 bgm_slider_color=0xFF0000
@system page=0 se_left=400 se_top=70 se_caption="Sound Effects" se_slider_left=530 se_slider_top=70 se_slider_width=160 se_slider_height=20 se_slider_color=0xFF0000
@system page=0 vo_left=400 vo_top=100 vo_caption="Voice" vo_slider_left=530 vo_slider_top=100 vo_slider_width=160 vo_slider_height=20 vo_slider_color=0xFF0000

Specify the position and size of the slider caption and the slider itself.
master_left=400 master_top=10 master_caption="Master Volume"** specifies the position of the caption and the caption text.
master_slider_left=530 master_slider_top=10 master_slider_width=160 master_slider_height=20 master_slider_color=0xFF0000 specifies the position, size, color, and other properties of the slider.

With this, you can now change the sound volume.

From Page 1 Onward

You can use page=1, etc., just like on page 0. Make sure not to forget to add the page tab.

; Add page tab
@system page=1 page_tab_caption=Message page_tab_left=80 page_tab_top=0

; Add items to page 1
@system page=1 message_speed_left=400 message_speed_top=10 message_speed_caption="Message Speed" message_speed_slider_left=530 message_speed_slider_top=10 message_speed_slider_width=160 message_speed_slider_height=20 message_speed_slider_color=0x00FF00
@system page=1 auto_speed_left=400 auto_speed_top=40 auto_speed_caption="Auto Mode Speed" auto_speed_slider_left=530 auto_speed_slider_top=40 auto_speed_slider_width=160 auto_speed_slider_height=20 auto_speed_slider_color=0x00FF00
@system page=1 message_sample_left=400 message_sample_top=70 message_sample_width=300 message_sample_height=40 message_sample_caption_color=0xFFFFFF message_sample_shadow_color=0x808080 message_sample_edge_color=0x808000

Loading Configuration Values

After defining the system screen, please load the configuration values with the load_system_config tag.

Finally

Since the configurable items are extensive, please refer to the manual (/doc/goki2/index.html) under "ModSystem Tags".

Starting GOKI2 ADV: Defining Backgrounds, Time Zones, and Screen Update Control Tags [Mod ADV Introduction]

HALO — Thu, 19 Mar 2026 21:57:51 +0000

Download

https://github.com/halo1234/Avalanches/releases

Background

The definition of a background is simple.
You just need to specify the name and the storage name (file name) as follows:

@make_stage name=white storage=white.png
@make_stage name=black storage=black.png

Additionally, you can also specify a time zone for the background.
For time zones, specify the name and suffix as follows:

@make_time_zone name=morning suffix=''
@make_time_zone name=evening suffix=ev
@make_time_zone name=night suffix=ng

With this, you can now use five tags: "white", "black", "morning", "evening", and "night".
When a time zone tag is specified, the background storage will load with the corresponding suffix added to the storage name.

@evening
@white

[halo] Loaded the white background for the evening.

In this case, the "white" tag will load whiteev.png.

Timing of screen updates

ModADV updates (transitions) backgrounds and character sprites at the timing when text is processed.
So, if you do the following, the screen will transition before displaying "あ".

@white

@halo pose1 expression1 middle show
[halo]abcdefg。

If you want the background and character sprites to transition separately,
you can also use the [run_reserved_transition] tag to forcibly trigger a transition.

Control tags

ModADV has several tags for control purposes (with run_reserved_transition being one of them).
If you understand how they work, using them is fine.
If you don't understand how they work, it might be difficult to use them properly.

Mastering ADV Development with GOKI2: Manage Character Assets, Audio Paths, and Dialogues Like a Pro

HALO — Fri, 13 Mar 2026 22:16:10 +0000

Download

https://github.com/halo1234/Avalanches/releases

Prerequisites

For more information on syntax extension, please refer to the following link:
https://dev.to/halo1234/getting-started-with-adv-development-in-goki2-system-architecture-understanding-module-structure-1olc

ModADV

GOKI2 includes a module called ModADV, which is specifically designed for ADV (Adventure) and Visual Novel games. Since ModADV depends on ModMessage, ModImage, and ModSound, these modules are automatically loaded whenever ModADV is initialized.

Character Definition

First, define a character using the make_character tag. For this example, let's extend the syntax of make_character to simplify the descriptions.

@!make_character image=with_image->true,without_image->false
@!make_character voice=with_voice->true,without_voice->false

; Create mob tag (redirect)
@redirect alias=mob name=make_character
; If no variables are specified with a pattern, the specified values will always be expanded.
@!mob /mob=true

Next, define the character. Do it as follows.

@make_character name=halo with_image with_voice
@make_character name=halo sub_directory_name=images part_of_directory_path=A
@make_character name=halo voice_sub_directory_name=testcase
@make_character name=halo shadow_color=0x808080 edge_color=0xFF0000
@make_character name=halo history_shadow_color=0x808080 history_edge_color=0xFF0000
@make_character name=halo history_icon=history_icon_halo history_icon_left=18

Let's go through it line by line.

@make_character name=halo with_image with_voice

This defines that the character "halo" is a character that has a standing picture and a voice.

@make_character name=halo sub_directory_name=images part_of_directory_path=A

This is the information necessary to calculate the path when a character illustration is placed in a subdirectory of the automatic search path. In this case, the character illustration will have the following folder structure:

images/A/CharacterIllustrationFileName.png

!Note!
If you place the character illustration in a subdirectory, you will need to rename the file when releasing. The /tools/make tool automatically does this for you. The /tools/make tool is used to generate master data.

@make_character name=halo voice_sub_directory_name=testcase

This is the information required to calculate the path when the voice is placed in a subdirectory. In this case, the voice folder structure is as follows:

testcase//halo000.ogg

specifies the file name of the currently running scenario script (without the extension). If the scenario being executed is test.gs, will be set to test, and the final path will be as follows:

testcase/test/halo000.ogg

@make_character name=halo shadow_color=0x808080 edge_color=0xFF0000
@make_character name=halo history_shadow_color=0x808080 history_edge_color=0xFF0000

This specifies the text color for the character "halo"'s dialogue and history.

@make_character name=halo history_icon=history_icon_halo history_icon_left=18

This specifies the icon to be displayed next to the history text.

Character Tag

This defines the character "halo". (The tag "halo" can now be used.)
We extend the syntax for the tags "character" and "halo".
By the way, internally, "halo" is redirected to "character".
If syntax extensions are made to the "character" tag here, they will also apply to "halo".
Conversely, if syntax extensions are made to the "halo" tag, they will apply to "halo" but not to "character".

@!character center_x=left->200,middle->400,right->600,middleleft->300,middleright->500,leftend->100,rightend->700
@!character gray_scale=sepia->true r_gamma=sepia->1.5 g_gamma=sepia->1.3
@!character visible=show->true,erase->false
@!character no_voice=nv->true

@!halo /storage=A_<POSE>_<FACE>
@!halo face=expression1->face1,expression2->face2
@!halo target=pose1->*target
@!halo pose=pose1->pose1,pose2->pose2

I don't need any more explanations.
The scenario script should now look like this:

; Handling Scenario Text with ModADV
; If you don't do this, you won't see any text
@using_mod_adv
; If you also want to omit the [r] and [p] tags, run the following tags:
@cr_handling !ignore

; Define a character "mob" that is only valid within this scenario
@mob name=mob without_image without_voice

@halo pose1 expression1 middle show
[halo] halo's line.

; Make the standing picture sepia and move it to the left
@halo pose1 expression2 left Sepia
[halo] The voice will play if configured.

[mob] This is the line of the mob. There are no standing pictures or voices.

@halo pose1 expression2 medium
[halo nv] does not play the voice.

@halo erase
[halo] erases the standing picture.

This is how to define a character using ModADV.

If you want to try GOKI2, you can download the latest environment from the following.

https://github.com/halo1234/Avalanches/releases

List of Related Articles

List of related articles on GOKI2

Getting Started with ADV Development in GOKI2: System Architecture – Understanding Module Structure and Custom Syntax Extensions

HALO — Fri, 06 Mar 2026 23:34:46 +0000

GOKI2

I am developing a framework called GOKI2 to enable the creation of games other than ADVs/visual novels using KiriKiri Z.

If you are interested, please download "Avalanches-Release2.x.x.x.zip" from the site below.
Extracting this file will provide you with the Avalanches source code and binaries (the development environment), as well as the tools required for development. We recommend reading readme.txt first.

Avalanches: The development environment.
GOKI2: The game framework.

Download

If you are interested, you can download the latest environment from the "Assets" section of the release tag (labeled as Avalanches release version 2.x.y.y) on the site below:

https://github.com/Halo1234/Avalanches/releases

Modules

In GOKI2, each tag is managed as a "module," and each module implements the necessary tags for its specific function.
Currently, a large number of modules have been developed. Users can build their own unique game configuration by importing only the modules (features) they require.
Modules are loaded in /src/goki2/system/construct.gs.
For a standard ADV game, the configuration would typically look like this:

; Snapshot feature
@load_module name=ModSnapshot
; Bookmark feature
@load_module name=ModBookmark
; Image-related features
@load_module name=ModImage
; Message layer-related features
@load_module name=ModMessage
; Sound-related features
@load_module name=ModSound
; Video-related features
@load_module name=ModVideo
; Right-click-related features
@load_module name=ModRightClick
; ADV features
@load_module name=ModADV
; System buttons
@load_module name=ModSystemButtons
; Save/Load screen
@load_module name=ModSaveLoad
; System screen
@load_module name=ModSystem
; Choices
@load_module name=ModSelect
; Title screen
@load_module name=ModTitle
; CG/Gallery screen
@load_module name=ModCGMemory
; Version window
@load_module name=ModVersionWindow

For details on each tag, please refer to the manual /doc/goki2/index.html.

GOKI2 implements its own tags, but with GOKI2's syntax extension features, tags compatible with KAG3 can also be provided. By default, GOKI2 provides a script called KAGCompatible.gs, which allows writing GOKI2 tags in KAG3 format.

The content is as follows, specifying scripts to create KAG3-compatible tags for the modules that are loaded.

@que unshift storage=KAGCompatibleDefault.gs
@que unshift storage=KAGCompatibleBookmark.gs
@que unshift storage=KAGCompatibleImage.gs
@que unshift storage=KAGCompatibleMessage.gs
@que unshift storage=KAGCompatibleRightClick.gs
@que unshift storage=KAGCompatibleSnapshot.gs
@que unshift storage=KAGCompatibleSound.gs
@que unshift storage=KAGCompatibleVideo.gs

Let's take a quick look at the contents of the file.

@!cursor /default_cursor=<DEFAULT> /pointed_cursor=<POINTED> /click_cursor=<CLICK> /draggable_cursor=<DRAGGABLE>

@redirect alias=loadplugin name=load_plugin
@!load_plugin /name=<MODULE>

@redirect alias=resetwait name=reset_wait

@!wait /skip=<CANSKIP> /no_skip=<NO_CANSKIP> /!skip=<!CANSKIP>

@redirect alias=waitclick name=wait_click

Utilizing `syntax` and `redirect` Tags in GOKI2

GOKI2 has a basic policy of "not omitting tag names or attribute names," but to simplify descriptions that tend to become long, it adopts a style that combines the syntax tag and redirect tag.

`syntax` Tag: Tag Syntax Extension

The syntax tag is used to define new syntax patterns for existing tags to simplify descriptions. However, extended syntax is not saved in the save data, so be sure to set it during initialization.

1. Expanding Syntax by Adding `!` to Tag Names

When using the syntax tag, you can define new description patterns by adding ! to the tag name you want to define.
Example of Syntax Extension:

Extension Definition (`@!`)	Actual Description	Interpreted After Conversion (`@`)
`@!make_character image=imgebl->true,imgdis->false`	`@make_character imgebl`	`@make_character image=true`
	`@make_character imgdis`	`@make_character image=false`

2. Specify a pattern by adding a `/` symbol to an attribute (pattern replacement)

By using the / symbol in a syntax tag attribute, you can specify a pattern replacement for the attribute value. The <KEY> part will be replaced with the value of the specified attribute.

Example of pattern replacement:

Extended definition (`@!`)	Actual notation	Interpreted after conversion (`@`)
`@!halo/storage=A_<POSE>_<FACE>`	`@halo pose=Pose1 face=Face1`	`@halo storage=A_Pose1_Face1`

3. Combined Usage

These can be used in combination.

Example of combination:

Extended Definition (`@!`)	Actual Description	Converted Interpretation (`@`)
`@!halo /storage=A_<POSE>_<FACE> pose=Pose1->p1 face=Face1`	`@halo Pose1 Face1`	`@halo storage=A_p1_Face1`

`redirect` Tag: Shortening Long Tag Names

As a basic principle of GOKI, we try not to abbreviate tag names or attribute names, but we adopt a style of shortening names using the redirect tag and the syntax tag.

The redirect tag is used in combination with the syntax tag to convert GOKI2's long tag names and attribute names into arbitrary short names for the user. This allows both concise writing and code clarity.

Data specified with the redirect tag is saved in the save data, so it doesn't matter where it is written.

Support for KAG3 Compatibility

Since GOKI2 tags have longer names compared to KAG3, a configuration file is provided in advance so that you can write in the conventional KAG3 format.
Make sure to load only what is necessary. For example, if you are not loading the ModBookmark module, you do not need to load KAGCompatibleBookmark.gs. (It will result in an error)

This is mainly handled in the /src/goki2/system/KAGCompatible***.gs files.

In Conclusion

For now, we have briefly introduced GOKI2.
Going forward, we will periodically post about GOKI2 and Avalanches.

DEV Community: HALO

GOKI2 Gameplay: ModBookmark & KAG3 Variable System for Data Persistence

Download

ModBookmark and ModSnapshot

Setting the Save Data Format

Thumbnails

Variable Areas

Return to Previous / Return to Title

Dialog

Expanding Gameplay with GOKI2 [Introduction to ModSelect] Implementing Branching Scenarios and Choices with ModSelect

Download

Choices

Choice Settings

Creating Choices

ADV Development with GOKI2 [ModTitle Introduction]: Implementing the Title Screen and Defining Button Layouts

Download

Title Screen

Title Screen Settings

Title Screen Layout

Displaying the Title Screen

Events

In Conclusion

ADV Development with GOKI2 [ModCGMemory Intro]: Implementing CG/Recollection Mode and Data Management via Excel

Download

CG/Reminiscence

CG/Reminiscence Data

Data Output

CG/Recall Screen Layout

Registering CGs

Recollection Script

Starting ADV Development with GOKI2 [Introduction to ModSaveLoad/ModSystemButtons] Layout of Save/Load Screens and Placement of System Buttons

Download

Save/Load

Save/Load Screen Layout

System Buttons The system buttons familiar from ADV games are implemented with ModSystemButtons. First, load the module.

Displaying the System Buttons

Starting ADV Development with GOKI2 [ModSystem Introduction] Building System Screens and Defining Configuration Items

Download

System Screen (ModSystem)

Building the System Screen

Setting the Page Size and Other Properties of the System Screen

ページ定義

Setting Item Definition

From Page 1 Onward

Loading Configuration Values

Finally

Starting GOKI2 ADV: Defining Backgrounds, Time Zones, and Screen Update Control Tags [Mod ADV Introduction]

Download

Background

Timing of screen updates

Control tags

Mastering ADV Development with GOKI2: Manage Character Assets, Audio Paths, and Dialogues Like a Pro

Download

Prerequisites

ModADV

Character Definition

Character Tag

List of Related Articles

Getting Started with ADV Development in GOKI2: System Architecture – Understanding Module Structure and Custom Syntax Extensions

GOKI2

Download

Modules

Utilizing syntax and redirect Tags in GOKI2

syntax Tag: Tag Syntax Extension

1. Expanding Syntax by Adding ! to Tag Names

2. Specify a pattern by adding a / symbol to an attribute (pattern replacement)

3. Combined Usage

redirect Tag: Shortening Long Tag Names

Support for KAG3 Compatibility

In Conclusion

Utilizing `syntax` and `redirect` Tags in GOKI2

`syntax` Tag: Tag Syntax Extension

1. Expanding Syntax by Adding `!` to Tag Names

2. Specify a pattern by adding a `/` symbol to an attribute (pattern replacement)

`redirect` Tag: Shortening Long Tag Names