3 ms·
> let it be yet another lesson to publishers like EA and Activision/Blizzard, and platform owners Microsoft and Sony, who may be considering always-on DRM in ne
by stcredzero 14y ago
> let it be yet another lesson to publishers like EA and Activision/Blizzard, and platform owners Microsoft and Sony, who may be considering always-on DRM in next-gen consoles or PC games: don't even think about it. It's a pipe dream
But this is Always-Online DRM done wrong. You DO NOT prioritize prevention of pirate-enabled playing of your game. You DO NOT implement anything which causes legitimate users to not be able to play. You DO prioritize UX over anything else at launch. You bias heavily to avoid false positives. Legit users (i.e. customers) are your first priority -- as they should be.
Most of all, you do not live in the fantasy world of DRM being some kind of impenetrable fortress. Basically, the resources of the entire Internet are arrayed against you, and the forces on your side constitute several hundred people in your company at most. You as the game publisher aren't the evil empire. You're the guerrillas. You don't have a vast army and an impenetrable fortress. You have a few fighters on your side and a jungle to hide in.
Here is what you do: You prioritize detection. You let the pirates play. You let the pirates believe that they've broken your DRM by throwing some honeypot DRM at them for them to break. All the while, you're detecting them. Then, when they think they've won, you use assets that you can control (servers) to restrict the pirate-enabled users you've detected. The point here is to be the one to keep the pirates guessing, not the other way around. Let them announce cracks, then make sure they get egg on their face a week after their "release -- again and again. Basically, you fight dirty to make sure that your product is far superior to the pirate's.
The way to have DLC in the modern age is to make sure that a key element of your "DLC" always stays on the server.