Fortress Forever's pre-Steam Greenlight encryption key #83
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I think I'll just swap the hyphen, even if it means eventually removing the "_PRE_GREENLIGHT" bit after azzyr has dealt with updating FF to the TF2 SDK... in case we re-use the encryption.
craftablescience
approved these changes
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Back in 2012, Fortress Forever had file encryption implemented (fortressforever/fortressforever@cbe8f3b).
Then three years later, the encryption was taken out (fortressforever/fortressforever@4f69be0).
That encryption key was
saxEWr5v. What a nostalgic trip, and I suppose the devs no longer believed it worthwhile keeping it!