TyranoScript Support

Guide to translating TyranoScript visual novels with Mafkers.

Supported Versions

How Mafkers Detects TyranoScript

1. tyrano.ks file exists
2. tyranoscript* directory exists
3. data/ folder with .ks scenario files
4. package.json with “tyrano” in name

Where Strings Are Stored

.ks Scenario Files (PRIMARY)

TyranoScript uses .ks files for scenarios. Similar to KAG but with TyranoScript-specific directives:

@bg storage="bg01.jpg"
Hello, player!
This is a TyranoScript scene.

data/*.json Files

TyranoScript stores scenario data, character names, and configuration in JSON files:

• data/scenario/*.json - scenario data
• data/system/*.json - system config

.js Files (Limited)

Some TyranoScript games store strings in JavaScript files via .text property assignments.

Tools Used

• Native Python parser for .ks and .json files (text-based, no tool needed)
• tyrano-kit (MIT, on-demand) - extract .ks to Excel for manual editing

Tag Pattern

TyranoScript uses square bracket tags and @ commands:

• [tag] - TyranoScript directive
• @command - inline command
• f.flag / sf.flag - variable references

Built-in Translation Plugin

TyranoScript has a built-in translation feature accessible via tyranoscript.com/usage/advance/translate. This generates JSON translation files that Mafkers can also process.