So, I've been looking at my list here to see which SpellForce games I have. Noticed SpellForce Platinum. It reminded me that it normally wants an activation key, but comes with a generic key, similar to Unreal and Far Cry which I also have here and are using generic keys. That lead me to asking this question.

Any plans for introducing a key distribution system? When? Never? Why and / or why not?

An implementation idea: since you want the keys to be unique for each customer, whenever a customer purchases a game which requires a key, you query your database to get a unique key, and then write that key into a simple XML file which is specific to that customer, and is distributed to him / her as part of the whole deployment procedure (like you do now with setup.exe, setup-1.bin, and so on, except you'd also have a setup.xml or key.xml or whatever). During installation, just read the value from that XML file using the Msxml2.DOMDocument API.

=> customers install and play faster, less waiting on customers' side, less support tickets for you.

Already implemented for games released here after April 5 2012. For games released here before that, contacting support is still required, since I'm not sure if support has kept a record of which user was assigned to which key.

How is it exactly implemented? Do they distribute the key along with the package (separate file or embedded), or just show it on the website similar to how GamersGate does it?

See attached. Since the use of keys does depend on the game (see UnEpic and/or Incredipede for example), displaying the key is (imho) best. This also allows you to use 2 keys (generic and unique), which depending on the game may allow you to play against one other person (if the check is for specific match, not centrally).

See the image.

As JMich said, this doesn't apply to games released prior to April 2012. I do agree that GOG should have had this fixed by now, but the system is in place.

Thank you both for the replies.