this post was submitted on 05 Sep 2023
691 points (97.8% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54443 readers
157 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I love the implication here, that they don't have the proper source (or skills left in the company) such that they can remove the DRM which doesn't play nice themselves so they rely on a cracked copy of the game instead. Been quite a bit of news lately about how game companies have failed to keep the original source code for their games. Diablo 2, the Transformers games etc and those from active companies, there's bound to be 1000s of games where the source is lost due to publishers closing down studios.
It's a complete crapshow IMO.
I still have the source code for the simple stuff I developed over 12 years ago, but these organisations don't think it's important to hang on to source code and assets for something they plan to make money from?
Really telling about the attitudes towards software outside of the FOSS space and datahoarder communities, and more importantly how little the management/publishers actually care about the product.
Although to counter that, I'm aware of at least one situation where the opposite has happened. One of my simulation games for example is really buggy and isn't able to receive more updates because the studio behind it voluntarily disbanded, leaving the publisher without access to the source code (I believe the publisher Aerosoft has tried to get a copy of the source to provide further game fixes, but the individuals behind the disbanded studio could not come to an agreement on this)
I've had teams not bother to keep proper history when moving from subversion to git and I've also had a DevOps team entirely wipe the history of a new project just because cloning took a long time (and refused to attempt shallow cloning).
So the idea that a company just lets their code "rot" to the point of not even having it anymore because it's just some legacy thing from over a decade ago is totally unsurprising to me.
Just to pile on. I've seen devs throw out the entire git history when moving between repos for ongoing projects.