Open-source project
ThirteenAG/WidescreenFixesPack avatar
ThirteenAG/WidescreenFixesPack

widescreenfixespack hides its deploy keys in a file git ignores

Plugins to make or improve widescreen resolutions support in games, add more features and fix bugs.

3,329 stars280 forksC++GPL-3.0

At a glance

What is it?
A collection of injected plugins that add or repair widescreen support in individual PC games, deployed by copying files into a game directory. The build reads the target paths from a local file that is never committed, and a game missing from that file is skipped without an error. The crash reporting section is longer than the install section and ends at a public link.
Who is it for?
Use this if you play one of the supported titles in a widescreen mode the release never shipped, because that is precisely and only what it is, and it is the least ambiguous thing in the file. Two things to know before you build it.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • ThirteenAG/WidescreenFixesPack3,329 ★ · +134
Star history
Repository2026-09-242026-11-15
ThirteenAG/WidescreenFixesPack3.2k3.3k

134 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A missing key means a silent no-op

The build does not deploy every plugin in the repository. It deploys the ones whose install location is named in a file at the repository root, and that file is deliberately not committed so that nobody's machine paths end up in version control. The key is the game folder name in upper case, mapped to where that game lives on this machine, with a worked example showing a drive letter and a game title. The consequence is stated in the same sentence and it is the important one: a game the file does not name is simply not deployed. There is no warning, no error, no non-zero exit. A contributor who adds support for a game, builds successfully and sees no output has almost certainly forgotten the file, and because the file is untracked there is nothing in the repository to tell them the convention beyond a paragraph in the readme.

The crash report is a public link to a large memory dump

The crash reporting section is the longest part of the file and it comes with three separate instructions, each carrying a cost. The first asks for the dump file a plugin can generate itself, and the readme is precise that the dump is required and the log is optional. The second is a registry walkthrough, creating a key under the machine's error reporting settings, and it warns in bold that this needs administrator rights and turns crash dumps on for every program on the computer. The third is for games that hang rather than crash, and it says to use the task manager to create a memory dump, warns that the file will be hundreds of megabytes or more, and asks for it to be uploaded to a personal cloud drive account with the link set to public access. Nothing in that sequence mentions what a memory dump of a game process can contain, so read it before sending anything.

Three build systems and a Windows executable in the source tree

Look at the badge row and the build requirements together. Three continuous integration systems are configured for the same repository: a hosted service for Windows builds, a hosted service for the main pipeline, and a workflow file on the code host itself. None of them has replaced another, so every push is plausibly built three times. The build itself needs a code generation tool that has a pre-built Windows executable committed at the repository root alongside a batch launcher, plus a specific compiler from the same vendor. Generating the project files is one command naming the toolset version, and the build configuration is a Lua script, with two Windows batch hooks running before the build and before packaging. So the toolchain is: a committed executable, a Lua script, two batch files, a native submodule directory, and three CI systems, for a project whose output is a plugin file you copy into someone's game folder.

Releases are per game and the pack has no version

The three releases visible in the repository's release list are individual plugins, named by a short code, dated four years and ten years and seven years ago respectively. There is no release for the collection as a whole, which means there is no version to pin, no upgrade path, and nothing to compare against. What a user actually installs is a per-game zip from the releases page, and the readme's own badges are pre-filtered release links, one for the general case excluding four specific platforms and then one each for two emulators, one handheld client, one reimplementation and one emulator fork. That is a careful piece of release organisation: the badges exist so a person on a console fork downloads the right artefact without reading a list. But it also means the collection is versioned by nothing at all, and the default branch was pushed yesterday.

Three identities in the payment links, one in the repository

The project has been renamed and the repository kept its old name, which is worth understanding before you go looking for things. The repository is named for one identity, the product page and every release link live under a different name, and the path segment of that product page is a legacy abbreviation of the first. The payment links go further: sponsorship is offered through four separate platforms across three distinct account names, one of which is a given name rather than either brand. The sponsor progress graphics are served from a third domain whose name describes the project as a legacy effort. None of this is hidden and none of it is unusual for a project that has run for years under more than one name. It does mean that searching for one of the names and not finding the others is the normal experience, and that the readme is the only place all of them appear together.

The build replaces an installed copy rather than creating one

The deployment step has two rules and the second is the one that surprises people. The plugin is copied into the game's scripts directory, or into a plugins directory for the games that use one, and then the game is started from there when debugging. And only a plugin that is already installed is replaced. So the build is a deploy-and-refresh operation over an existing manual installation, not an installer: on a machine where you have not already copied the files into the game folder, the build does nothing and reports nothing. That is consistent with how the tool is meant to be used, since the readme describes installation as copying the files into the game root and uninstalling as deleting them, with no package manager and no installer. It also means the first install on a new machine is a manual step the build cannot perform, and a developer debugging a plugin has already done it once by hand before the tooling is any use.

Windows XP support is two compiler flags

The important notes at the bottom of the file are two lines long and the first is about a platform from two decades ago. The plugin is not compatible with that version of Windows unless it is recompiled with a specific older toolset and a specific thread-safety compiler flag. That tells you the code still compiles for it deliberately, which is a rarer commitment than it sounds for a project that injects into other people's executables, and it tells you the binary you download for a modern system is not the same one you would need there. The second note hands WINE users to a third-party blog rather than documenting the path itself, which is the sensible division of labour and also means the project's own answer to running on a non-Windows system is not in the repository. The licence file and the readme are both lower case in the tree, which is consistent with a project that has been reorganised by hand rather than generated.

Editorial conclusion

Use this if you play one of the supported titles in a widescreen mode the release never shipped, because that is precisely and only what it is, and it is the least ambiguous thing in the file. Two things to know before you build it. The deployment map is a file that is never committed, keyed by the game folder name, so a fresh clone has no deployable game until you create that file yourself, and a typo in a key produces no output rather than an error. And the crash reporting instructions, which are the longest part of the documentation, ask for a memory dump of the game process uploaded to cloud storage with public access, which can be hundreds of megabytes and may contain whatever the game had in memory. Read that before you send one, and redact it first.

Frequently asked questions

What is ThirteenAG's WidescreenFixesPack?

A collection of plugins that make or improve widescreen resolution support in PC games, add features, and fix bugs, distributed as per-game downloads from the repository's releases. The plugins are loaded into the game process through a separate loader project by the same author, and installation is copying the files into the game's root directory.

How do I build widescreenfixespack?

You need a code generation tool whose Windows executable is committed at the repository root, a specific compiler version, and a project file generated by one command naming the toolset. The deployment step then reads each game's install path from an environment file at the repository root that is deliberately not committed, and a game missing from that file is simply not deployed.

How does the widescreenfixespack build decide where to copy a plugin?

From an environment file in the repository root that git ignores, keyed by the game folder name in upper case, so machine paths stay out of version control. The build copies into the game's scripts folder, or a plugins folder where one exists, and replaces a plugin only where one is already installed, so the first install on a new machine is a manual step.

What does widescreenfixespack ask for when reporting a crash?

The crash dump file is required and the log is optional. If the plugin cannot generate one, the readme gives a registry walkthrough that needs administrator rights and enables crash dumps for every program on the machine. For games that hang rather than crash it asks for a task manager memory dump, warns that it will be hundreds of megabytes or more, and asks for it on cloud storage with the link set to public access.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. ThirteenAG/WidescreenFixesPack on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/thirteenag-widescreenfixespack.svg)](https://hysenlabs.com/projects/thirteenag-widescreenfixespack)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/thirteenag-widescreenfixespack.svg)](https://hysenlabs.com/projects/thirteenag-widescreenfixespack)

Was this useful?