COD:BO7's single-player uses dedicated servers. Terrible, yes, but that's as foolproof as it gets when it comes to piracy. They also probably did this to combat all the 'services' offering to unlock camos/cosmetics that you'd normally have to grind for; players would give someone their credentials (probably stolen later and sold to cheaters) and the person on the other side would then use a hacked client to trick the backend into thinking they completed all the challenges. With a server-side campaign, that probably got much more time consuming, I reckon.
Every game separately encrypted then compressed into solid archives. Pressed in a way every game lands on different precise height of CD, padded before compression if necessary so it takes enough space on CD. Separate machine burning tiny holes in CD from the back, but not so tiny that CIRC could fixes them. At least one hole per file.
Install locates the damage and gives you code encoding locations. Over the phone You receive ECC code. No more magic keygens, pirates have to distribute whole multi megabyte games.
I think most (all?) Steam games link steam_api.dll (or something like that) which somehow figures out the running Steam process and thus the Steam ID, and then does a HTTP API request to check that you own the title.
Like 15 years ago Steam launched CEG (Custom Executable Generation) - I remember reading a write-up a while ago, but each user had a customer launcher generated on install I think, and I think there was an extra segment put into the .exe file and that was put to use somehow, though I don't know if CEG is still a thing.
COD:BO7's single-player uses dedicated servers. Terrible, yes, but that's as foolproof as it gets when it comes to piracy. They also probably did this to combat all the 'services' offering to unlock camos/cosmetics that you'd normally have to grind for; players would give someone their credentials (probably stolen later and sold to cheaters) and the person on the other side would then use a hacked client to trick the backend into thinking they completed all the challenges. With a server-side campaign, that probably got much more time consuming, I reckon.
Every game separately encrypted then compressed into solid archives. Pressed in a way every game lands on different precise height of CD, padded before compression if necessary so it takes enough space on CD. Separate machine burning tiny holes in CD from the back, but not so tiny that CIRC could fixes them. At least one hole per file.
Install locates the damage and gives you code encoding locations. Over the phone You receive ECC code. No more magic keygens, pirates have to distribute whole multi megabyte games.
I respect the creativity, but this was a 22mb game. Nothing arj or rar wouldn’t handle. Or going on irc
there isn't a market for gamers buying games on CDs these days, so it's not really a problem that needs to be solved
The same problem exists with PC games released on DVDs.
there isn't a market for gamers buying games on DVDs these days. BlueRay the same.
Of course there are voice that do want real disks but sadly that time is over. Digital sales won.
2 replies →
Well how does Steam do DRM?
I think most (all?) Steam games link steam_api.dll (or something like that) which somehow figures out the running Steam process and thus the Steam ID, and then does a HTTP API request to check that you own the title.
Like 15 years ago Steam launched CEG (Custom Executable Generation) - I remember reading a write-up a while ago, but each user had a customer launcher generated on install I think, and I think there was an extra segment put into the .exe file and that was put to use somehow, though I don't know if CEG is still a thing.
1 reply →
Its easier on a system that doesn't need to do broadcast distribution and with servers available.