This section describes files and folders related to Kirikiri.
It does not cover all files. Most of the files require special attention. Please refer to readme.txt for the folder structure of the Kirikiri Z SDK distribution archive.
For your convenience, files related to KAG are also posted.

plugin and plugin64

This is the folder where Kirikiri looks for plugins. Kirikiri refers to the plug-ins located in the folder where the Kirikiri executable file is located.→ About plugins

data and content-data

If this folder is in the folder where the executable file of Kirikiri is located, the folder is regarded as the project folder and executed.→ How to start

*.xp3

It is an archive file for Kirikiri.→ Releaser

data.xp3 and data.exe

Kirikiri will execute this file if it is in the same folder as Kirikiri's executable file, assuming that it is a project folder.→ How to start

*.tpm

A plug-in for Kirikiri, which is automatically loaded at startup.→ About plugins

krdevui.dll

This is a DLL commonly used by Kirikiri's development tools. You do not need to include this file in your end-user distribution.

krmovie.dll

Necessary when playing WMV / MPG in Kirikiri. If you do not want to play video, you do not need to include this in the end user distribution.→ VideoOverlay class

*.dll

For Kirikiri plug-ins, they must be included in the distribution for end users. Of course, you don't need to include unnecessary plugins.→ About plugins

krkr.eXe

It is Kirikiri core. You can change the file name when distributing to end users.

*.cf and *.cfu

This file contains the options for the Kirikiri core. To enable the options specified to Kirikiri core (including -datapath option, etc.) in "Kirikiri settings" (-userconf), the same applies to the distribution for end users. Must be packed.→ Kirikiri setting

File corruption check tool.exe and its .ini file

File corruption check tool. You can change the file name when distributing it to end users, but you must make sure that both the .exe and .ini files have the same name. When you distribute the Kirikiri Z SDK, it is included in enduser-tools, but when distributing to end users, it is usually necessary to place it in the same folder as the Kirikiri executable file.→ File corruption check tool

startup.tjs

TJS script file. Kirikiri looks for this file directly under the project folder and executes it first.→ How to start

*.tjs

TJS script file.

msgmap.tjs

Message map file. If you haven't created it, you don't need to include this file in the end-user distribution.→

*.sig

The signature file output by the key / signature tool. Refer to a file corruption check tool.→ Key and signature tools

*.rpf

Releaser's profile. Releaser setting information is recorded. This file does not need to be included in the end-user distribution (Releaser automatically excludes this file).→ Releaser

hwexcept.log

When the Kirikiri core crashes, it may be created at the location specified by the -datapath option. There are various situations that can be said to be a crash, but if this file was created it is a very severe crash, so please collect it from the end user and send it to the author of Kirikiri if necessary. This file does not need to be included in the end user distribution.

*.console.log

It is a log file of the console of Kirikiri. Normally, when Kirikiri crashes, it may be created at the location specified by the -datapath option. The log that this file records is almost always the result of script mistakes. During application development or after distribution to end users, collect them from end users for debugging. You do not need to include this file in your end-user distribution.

*.dump.txt

TJS dump file. You do not need to include this file in your end-user distribution.→

*.sli

This is a loop definition file output by the loop tuner.→ Loop tuner

*.tft

Rendered font data output by the rendered font data creation tool.→ Rendered font data creation tool

*.png *.jpeg *.jpg *.tlg *.bmp *.jxr

This is an image file.→ Graphic system

*.wav *.tcw *.ogg *.opus

This is an audio file.→ Sound system

*.wmv *.mpg *.mp4 *.ogv

This is a video file.→ VideoOverlay class

*.ks

This is a KAG scenario file.

*.ksd *.kdt

These are KAG save data.

*.asd

This is a KAG animation definition file.

*.ma

This is the KAG area action definition file.