Unfallen_Satan: I am sorry for the delayed reply. Work and a lot of Pathfinder: Kingmaker.
Not a problem. I appreciated your post and the quality discussion we've had already. If you reply back, please be aware I often have delays in responding myself and sometimes posts get lost in the shuffle, so basically if I don't respond further, please don't take it personally. While I also have delays responding, you can also feel free to PM me if you prefer that.
Unfallen_Satan: I want to make sure our main disagreements are clear:
A game has single player part and multiplayer/skirmish part. As whether it is better to have a version of that game that can install/play the single player part DRM-free but requires DRM for the multiplayer/skirmish parts than a version that just has DRM-free single player part: I believe it is better. You believe it is worse. Is that correct?
As to whether it is to GOG's benefit (by that I mean beneficial to its work on releasing more DRM-free games, though not 100% exclusively), by releasing some games that has DRM-like behavior, e.g DoW2: I believe it is beneficial. You believe it is harmful, to GOG and perhaps also to GOG users, in the way that hair in what should be hair-free soup is harmful. Is that correct?
Please feel free to correct me or explain more of your reasoning if you feel like. I have nothing further to add to my reasoning.
1. Yes, I believe "DRM-free singleplayer, but with DRMed multiplayer" is worse than "DRM-free singleplayer, but with DRMed multiplayer removed entirely". My position tends to not be the most popular even around a store/forum like this, as people will argue that removing multiplayer is taking away game content. While objectively, that is correct it is removing content, to me, the game content has already been taken away so to speak, by being DRMed. So in my view, the "DRM-free singleplayer, but with DRMed multiplayer removed entirely" example is a complete game (in the sense the product being sold can be owned 100%) and "DRM-free singleplayer, but with DRMed multiplayer" is not.
2. Yes, I also believe that releasing some games with DRMed content/DRM-like behavior is counterproductive to advancing DRM-free gaming as a whole.
While I grant that many bigger name titles have released here in recent years (as GOG became increasingly "DRMed" in my view), I don't think that has much to do with the increasing slide towards DRM-like practices.
Exception: whenever GOG first began distinguishing that "DRM-free" is in reference to singleplayer but not necessarily multiplayer modes, that did open the door for something like Dawn of War 2 to eventually release here...however, it only allowed the possibility of such a game coming here and I don't believe it directly impacted negotiations in any way (e.g. I don't believe in talking to bring the game here SEGA said something like "we weren't gonna bring it here, but once CDPR added 'MyRewards' to Witcher 3, that really convinced us, now you got yourself a deal")
I do believe GOG loses negotiation leverage in bringing releases here completely DRM-free, because companies can turn around and say "so what if I lock a small amount of content behind online/client? So does CDPR," to which GOG cannot meaningfully counter. In fact GOG staff have said several times comments to the effect of some online/client locks are okay as long as it doesn't substantially affect the singleplayer offline (my paraphrasing to the best of my recollection). So we've already been sliding down the slope. Wheeeee! :)
Unfallen_Satan: I am not blind to the dangers of the slippery slope. However, I see GOG trying to compromise with an industry that is very and increasingly protective of its "digital rights," instead of going on a slippery slope. At the same time, I think users like you who push back forcefully against every perceived offense contributes in no small measure to keeping GOG honest and off that slope.
I think this may be at the root of our friendly disagreement too: I don't wish for GOG to compromise with the industry. I think compromise, in this particular instance and set of circumstances (DRMed PC gaming market), compromise = losing. I am not so bull-headed as to automatically think that way in other matters, of course, but I do think it applies in this situation. Also, there is an argument to be made that by being a hardline DRM-free store, this stands out in the market (especially given the big name titles that are on GOG), whereas being another store with various DRMed content isn't doing anything special to stand out amongst competitors.
Unfallen_Satan: I am not commenting on this and only want to ask: What happened with Tempest? Was it a innocent mistake in coding the patch? Did the devs try to pull a fast one on GOG and GOG didn't catch it? Or did GOG try to pull a fast one by knowingly letting the devs patch a previously DRM-free game to have DRM? You might not know the behind-the-scenes story. If you could share what you did, what GOG's response was, and what is the status of Tempest now, readers might be able to draw their own conclusions.
Tempest previously worked fine offline but on the newest version, apparently requires Galaxy to run. There is a forum thread in the dedicated game forum for Tempest but at the moment I don't have much information. I contacted GOG Support, was told it was a known issue being investigated, but there was no timetable for it being fixed. The advice I was given was to use Galaxy, which has a rollback feature, to get the previous version's "Galaxy installation" (my term...sorry I don't know how to describe this precisely), which could then be played offline.
I don't know if the issue was intentional or not on anyone's part, so I can't attribute malice to either the devs or GOG. My point/opinion was more just to say that such an error shouldn't happen if a store is serious about caring for DRM-free games. It has happened with other games in the past too (For the King, Cult of the Lamb).