How to get the .ks files

The safest way to translate a KiriKiri-KAG game is to work from the real scenario scripts. In most projects, dialogue and scene flow live in .ks files.

Source-first workflow

Use the original scenario files whenever possible. Working from unpacked source scripts makes it much easier to preserve tags, labels, and engine-specific formatting.

What you should have

The original game script files or a clean, legally obtained extraction of the scenario folder.
Permission to translate and redistribute changes if the project is not yours.
A backup of the full script folder before editing.

Where KAG scripts usually live

The exact layout varies by game, but scenario files often live in folders such as scenario/, data/scenario/, script/, or another unpacked archive directory.

MyKAGGame/
  scenario/
    start.ks
    common.ks
    route_a.ks
    route_b.ks
  data/
  bgimage/
  sound/
  system/

Path / file	What it usually contains	Translate?
scenario/*.ks	Main story flow, dialogue, scene labels	Usually yes
common.ks / system.ks	Shared menus, reusable message blocks, helper macros	Sometimes
macro-only scripts	Pure command logic with little or no visible text	Usually no
archives / binaries	Packed resources or engine data	No

What KAG formatting must stay intact

Tag lines such as @jump, @eval, @if must remain valid.
Inline tags like [l], [r], [p], [np], and [emb exp="..."] should not be removed.
Names and labels inside macros or jumps should never be translated unless you also update every reference.
Escapes / spacing may matter for some projects. Avoid aggressive cleanup tools.

Good vs risky edits

; Good: visible text translated, tag preserved
[cm]
「I will wait here.[l][r]」

; Risky: formatting tags removed
「I will wait here.」

Encoding notes

Older KiriKiri-KAG games may still rely on legacy encodings such as Shift-JIS, while others use UTF-8 or UTF-16. If you are not sure, start by keeping the original encoding and test one file first.

Do not convert everything blindly

A working script with the wrong encoding can still become unreadable in-engine. Translate one small scenario file, export it, and test before touching the whole project.

If you only have a packed game

Some KAG titles store scripts inside archives instead of loose files. If you cannot find readable .ks files, you may need a translation-friendly source package from the developer or publisher.

Legal / safety note

This guide does not cover bypassing protections or extracting content you do not own. Always respect the game license and the developer's terms.

Quick checklist

You are working from real .ks scenario files.
The files open as readable text in an editor.
KAG tags and commands are preserved.
You test the output in-engine after export.