this post was submitted on 12 Sep 2023
177 points (95.9% liked)
Gaming
19730 readers
192 users here now
Sub for any gaming related content!
Rules:
- 1: No spam or advertising. This basically means no linking to your own content on blogs, YouTube, Twitch, etc.
- 2: No bigotry or gatekeeping. This should be obvious, but neither of those things will be tolerated. This goes for linked content too; if the site has some heavy "anti-woke" energy, you probably shouldn't be posting it here.
- 3: No untagged game spoilers. If the game was recently released or not released at all yet, use the Spoiler tag (the little ⚠️ button) in the body text, and avoid typing spoilers in the title. It should also be avoided to openly talk about major story spoilers, even in old games.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That doesn't make ANY sense.
They locked their keys inside their program and had to break in.
Here's a video from Modern Vintage Gamer explaining why they did that https://youtu.be/XEKPUARYckc?si=oxszKFtYHBL9TmHH
thanka for the link. that was worth the watch
Thank you for posting this, it is a fascinating story.
After watching the video the main thought I have in my mind is that the whole issue could have been subverted by building two sets of executables. One with DRM and one without. The DRM free version could then be stored for potential future use. That way you wouldn't have to necessarily maintain the build environment.
Obviously this wouldn't have occurred to me if I was building the game, but I hope the companies learned as soon as they ran across the issue the first time.