Patch.tjs — Xp3filter.tjs [extra Quality]

Based on the filenames Patch.tjs and Xp3filter.tjs, you are likely looking at Kirikiri/Z-Game Engine (often used for visual novels). These files are typically used for modding, extraction, or file replacement without modifying the original game archives (.xp3 files).

Here are the specific features these two files provide when used together:

5. Debug & Development Overrides

For modders/developers:

• Hot-reloading: Changes made to files in the patch folder take effect immediately without repacking the archive.
• Bypassing Archive Encryption: If Xp3filter.tjs is configured to bypass checks for certain files, it allows loading unencrypted/modified assets.

Example Patterns (pseudocode)

• Simple path redirect filter

  • If "mods/" + requested exists on disk, return that file data; else return null to let engine continue.

• Decryption filter

  • Read raw bytes from XP3 entry, apply XOR or AES routine, return decrypted buffer to engine.

• On-the-fly text patch

  • For script files (.ks/.tjs), read buffer, replace tokens (e.g., change text encoding or fix strings), and return modified buffer.

Minimal example: listing XP3 entries (Xp3filter.tjs-like pseudocode)

// open xp3, read header, iterate file table
var xp3 = openXP3("game/data.xp3");
var entries = xp3.listEntries();
for (var i = 0; i < entries.length; ++i) 
  print(entries[i].path + "  size:" + entries[i].size);

6. Security Implications

The existence of Patch.tjs presents a significant security consideration for developers using the Kirikiri engine. Because the engine automatically executes code in Patch.tjs without integrity checks, it becomes a trivial vector for: Patch.tjs Xp3filter.tjs

• DLL Hijacking: Injecting malicious native libraries via the Plugins.link command.
• Logic Tampering: Bypassing authentication checks or altering game mechanics.

To mitigate this, developers often:

1. Disable the autoload functionality for Patch.tjs in a recompiled version of the engine executable.
2. Embed the patch logic into the main executable or load it from encrypted, memory-loaded resources rather than the file system.

Minimal example: replace a file inside XP3 using Patch.tjs-like pseudocode

// create patch: replace image at path with new file
var patch = new Patch("game/data.xp3");
patch.replace("/image/bg/title.png", readFile("mods/new_title.png"));
patch.apply(); // writes new archive or produces .patch package

What is Xp3filter.tjs?

While Patch.tjs handles runtime logic, Xp3filter.tjs handles load-time security. This file is executed when the Kirikiri engine initializes its file system (the Storages layer). Based on the filenames Patch

The "filter" in its name is literal: it filters which files from an XP3 archive are allowed to be read, and how they should be decrypted or decompressed.

3.2 Mechanism of Operation

When the engine attempts to read a file from an XP3 archive: Hot-reloading: Changes made to files in the patch

1. The raw sectors are read from the disk.
2. If an archive filter (defined or loaded via mechanisms often linked to Xp3filter.tjs) is registered, the raw data is passed to this filter.
3. The filter performs operations (XOR decryption, bit shifting, decompression).
4. The processed data is returned to the engine for parsing as scripts or images.

What these scripts do

• Patch.tjs: a TJS (TriangleScript/TeaJS-style) patching utility script used to modify files or archives (commonly used with game resource packages). It applies binary or text patches, replaces files inside archives, and can update headers/offsets.
• Xp3filter.tjs: a filter/handler script specifically for XP3 archives (visual novel engine archives, e.g., Kirikiri/KAG2). It extracts, lists, repacks, or transforms files inside XP3 containers and often works with Patch.tjs to apply modifications directly into the archive.