[Feature] Add way to toggle Feb 2026 and legacy .exe release, along with applying the correct T7Patch

[RotKingJoey]

It would be ideal to be able to switch back and forth between .exe versions manually depending on what mod you want to load after launching the game, if that mod has not been updated for the new version Treyarch pushed.

Additionally, now that Scroptss has released a new version of T7Patch for the Feb 2026 build, it would be great if the tool could automatically detect the version of the game that is currently selected, then select the appropriate version of the patch.

Below is the new T7patch and source code:
https://github.com/Scroptss/T7Patch
https://github.com/Scroptss/T7Patch-src

[boggedbrush]

This is technically two feature requests in one, so I’m going to split it into two PRs.

For the .exe side, executable detection is already a feature, but I agree it could be improved. A manual .exe switcher would also be a good addition.

For the T7Patch side, I will open a PR for the new patch and implement support for Windows users. That said, I’m not a fan of moving one platform ahead of the other unless it is actually necessary. Because of that, it will not reach the stable branch until Linux users are on the same version as well.

I will update this comment with the new PRs if you would like to track the progress.

I hope that makes sense.

Edit: I just realized the latest release includes Linux support. I’ll probably do some testing around that and update the PRs accordingly.

[boggedbrush]

Two PRs are now available for this work and can be tracked here: #32 and #33.

This is planned for the 1.2.3 release.

Thank you @RotDogWater for the ideas and for outlining the workflow needed here.

[boggedbrush]

EXE Swapper Update

Hello @RotDogWater ! I wanted to share an update on the new design for the EXE Swapper:

T7Patch Update

T7Patch has also been updated to the latest version in v1.3.0-beta.

Current Status

The EXE Swapper is not quite ready for prime time yet. I want to make sure it is secure and does not allow hijacking or other unsafe behavior.

Once it is ready, it will be included in the official stable release of v1.3.0.

If you care about the nerdy details:

Security

The compatible EXE, latest EXE, and enhanced EXE all have their hashes tracked.

The compatible EXE and latest EXE also have their Steam build numbers tracked. The enhanced EXE does not use Steam build-number tracking.

These checks help verify that the EXE being used is the intended one. If an unexpected or unintended EXE is detected, the app will show a warning.

Examples of unintended EXEs include:

• unsupported builds
• modified files
• pirated copies
• files altered by malware or viruses
• any EXE that does not match the expected hash and, where applicable, build number

Compatible build retrieval

Previously, I used a permalink to retrieve the compatible build. That was easier for me, but it created issues whenever the link went down, which made it not so permanent after all.

Instead, I decided to use Steam Console so the app can retrieve the previous EXE needed for the compatible build from Steam in a more reliable way.

Important security note

These security checks only verify the EXE itself.

They do not verify that anything outside the EXE is safe. They only confirm that the EXE file matches the expected hash and has not been tampered with.

Versioning Note

I originally planned to add these features in v1.2.3, but after making significant changes to the underlying codebase, I decided that the new features and larger architectural changes warranted a major version bump to v1.3.0.

[RotKingJoey]

The new UI is great, glad to see progress on this. Just a heads up, when downloading the patch with the beta, it seems to still be pulling from the shiversoftdev repo by default:

Not sure if that's intended or not, just wanted to check with you.

[boggedbrush]

Thanks for the heads up, I'll have to look into that. It should only pull the LPC files from that repo.

[boggedbrush]

@RotDogWater The t7patch issue, and the exe swapper, are fixed and implemented in beta3. This will (hopefully) be the last beta release before it reaches stable.

If you encounter any issues, please don't hesitate to reach out!

[RotKingJoey]

Tested the new build, it appears to download the updated patch successfully and the .exe swapper appears to work as intended.

One thing I noticed however is if you choose the legacy exe, then reinstall t7patch, it doesn't appear to download the legacy t7patch to match the older .exe? If I'm doing something wrong, let me know.

[boggedbrush]

If I'm not mistaken, the new t7patch is backwards compatible with the previous build of the game as well as the current version. I haven't tested this heavily, but to my knowledge it works just fine. If you encounter anything otherwise, please let me know!

[RotKingJoey]

This post on the new patch seems to go against this notion, I believe it was intended to be supported initially but didn't pan out.

Scroptss/T7Patch#6

[RotKingJoey]

To add to the above, I haven't been able to successfully get the new patch working with the legacy .exe at any point in my testing, be it through the Windows .exe or .dll version of the patch. Based on the issue tracked, it doesn't seem we can expect this to be resolved any time soon, and the best bet would be to use the older patch as an alternative option, despite it having less protections comparatively at this point.