If you are trying to get a game working, the workflow usually looks like this:
In the KiriKiri environment, these scripts act as hooks during the game's boot sequence: Xp3filter.tjs Patch.tjs Xp3filter.tjs
Once scripts are translated, they must be re-inserted. Instead of repacking the archive (which is difficult with custom encryption), translators often place translated scripts in a folder on the disk. They then create a Patch.tjs . This Patch.tjs instructs the engine: "When looking for scene1.ks , look in the patch folder first, before looking in the archive." If you are trying to get a game
While the filter handles the "how," Patch.tjs handles the "what." This file is traditionally used to override the core game logic without touching the original, encrypted archives. This Patch
In conclusion, Patch.tjs and Xp3filter.tjs represent just a small part of the broader world of game scripting and modding. However, their impact on the gaming community and the potential for future development make them significant topics of discussion and exploration.