A free, uncredited, fan-made tool helped make Catherine’s PC port

Sega did not have permission to use the tool, which was used to cross-reference cutscenes from the original game

catherine classic pc steam charts

After a handful of teasers, Catherine Classic was finally released on PC earlier this month, and players quickly began delving around in the game’s files. Once there, they found that a free fan-made tool had been used during development from the original game’s Xbox 360 version, and was then left in the files.

The use of the tool seems to have first been discovered by VictSok on Twitter, who posted an image of a readme file found in Catherine Classic’s files, which were attached to something called CriPakTools. That readme states that the tool “is based off code […] released on the Xentax forums which was further modified by Nanashi3,” and that the developer, who goes by esperknight, has since added a few of their own tweaks. Sega later confirmed the use of a tool for cross-referencing purposes during development.

We spoke to the developer of CriPakTools. They say that they can’t be sure that the tool used in the game is their creation, although when we compared the text found in the readme file to the text on the tool’s GitHub repository, we found they were exactly the same. Esperknight says that they’ve had “no contact” from Sega.

They go on to say that they released the tool “with no expectation of reimbursement or acknowledgement,” and many people commenting online have pointed out that there’s no licensing agreement on the tool’s GitHub page. According to GitHub, however, if no licensing agreement is posted, “the default copyright laws apply, meaning [the developer] retains all rights to the source code and no one may reproduce, distribute, or create derivative works from your work.”

Related: Atlus has teased more PC ports

We reached out to Sega, who said “we are aware of the discussions online and are currently looking into it.” We then asked for further comment after our conversation with esperknight. Sega told us that “a tool was used to cross reference the game assets and then these files were mistakenly left in the final build. Sega did not use the tool for development purposes. These files will be patched out in the next update, which also include several other fixes, to avoid any further confusion.”

Esperknight says that “I never put a license on [the tool] as I didn’t want to overstep as not all the code is mine (although I did modify quite a bit and added the insertion).” Despite that statement, GitHub’s terms should still apply, potentially creating a legal grey area around Sega’s use of the tool.

YouTube Thumbnail

We approached GitHub for clarification. The website told us that despite esperknight’s comments, “it is best practice for developers who want their code to be broadly used to both apply a standard open source license that is widely understood and can be relied upon, and to make sure that any code they incorporate into their projects also has such a license.” Esperknight’s repository does not feature such a license.

GitHub also pointed us towards its licensing advice website ChooseaLicense.com, which states that “If you find software that doesn’t have a license, that generally means you have no permission from the creators of the software to use, modify, or share the software. Although a code host such as GitHub may allow you to view and fork the code, this does not imply that you are permitted to use, modify, or share the software for any purpose.”

Catherine Classic seems to have been relatively well-received. In Jeremy’s hands-on with the game, he called it “unmissable,” praising its combination of an impressive puzzle game and a compelling relationship drama.