Heyo, I recently posted some notes about cracking games on Linux. Those notes originally started as a reply to someone, but they evolved into more of a small treasure map for a lot of the important parts of cracking games on Linux. As I finished up the post, I noticed that it was almost exactly at the maximum length it could be on Lemmy (10k characters). I kept wanting to come back and expand just a little bit on something in that post but anything over 10k characters would not save. I eventually got so annoyed that one thing led to another and now I actually have a proper bible, this time at 100k characters.

The GNU Testament of the Linux Cracking Bible is located on GitHub: https://github.com/YoteZip/LinuxCrackingBible

A brief list of topics covered in it:

  • Configuring Lutris
  • Configuring Wine
  • Sourcing clean games
  • Discovering what DRM your game has
  • Step-by-step guides for cracking each type of popular DRM using community tools:
    • CEG (Steam Custom Executable Generation)
    • Epic Online Services
    • GFWL (Games for Windows Live)
    • Origin
    • Securom
    • SteamDRM (Windows)
    • SteamDRM (Linux)
    • Steamworks API
    • Uplay r1
    • Uplay r2
    • Xbox Live
  • Some of my personal scripts for automated cracking
  • Repacking games on Linux

My primary goals for this guide are to:

  • Demystify cracked gaming on Linux
  • Teach you to crack games by yourself, instead of relying on scene/p2p crackers

(Although it’s written primarily for Linux users, Windows users should be able to follow along fairly easily for the cracking guides.)

  • redditReallySucks@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    This is great. Even as a windows user I never saw a guide this good that talks about all drm solutions. Thanks for sharing your exertise. @Mods please add this to the Megathread

    • Yote.zip@pawb.socialOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Thanks! After coming back and re-reading some of the sections of the guide, it’s really surprising how few steps it takes to crack most things, and how simple a user guide on something like that would be. You’d think someone would have done something like this at some point. (or maybe they have and I haven’t seen it)