Maybe to reduce the simultaneous load in their servers among other things.

If I download one after the other, that's what reduces simultaneous load IMHO... I was just wondering if I'm the only one who noticed, and if there is a real reason. Maybe GOG announced something and I missed it?

The only reason I can think of is piracy.

Going by the other download issues in the last week or so, it is troubling, but if we are lucky, it will just be due to the last sale ... maybe something they are experimenting with for future sales, to reduce Server use impact for browsing buyers.

That said, many sites have a short download time limit for non-active links, and many don't even support resume. Let's hope this isn't a permanent change ... and perhaps further coercion to use Galaxy. I doubt it is anything to do with piracy, why would it be?

Whether you are downloading multiple files simultaneously or multiple threads per file, both impact GOG servers. So stopping you being able to automate downloading or reducing that considerably, will reduce server impact.

With some big sales in the past, many of us could not download our games at all during the sale ... or only at an incredibly slow and painful download speed. Sometimes using a Download manager would double or triple that horrible speed, by using multiple threads, and at least make it possible to download your game(s). Maybe GOG don't even want that possibility in big sales. With Galaxy and even third party downloaders that use the GOG SDK, they retain a measure of control over download speed etc.

True. Just for clarification, I use a download manager that is configured to download in a single-thread, i.e. not multiple chunks at the same time, but rather linear. The comfort was that I could add all the links, so it would start the next 4 GB file after the current download is finished.

Now, I have to download during daytime, because I add the next download just prior to the current download being finished, in order for the download link to still be valid when it starts the next file. I don't see how this is relevant to GOGs' server stress, except that now I have to be at the computer (which I often enough am anyhow, during daytime) and they get additional stress during daytime (instead of "linear" download during night hours).

Anyway, thanks for your reply.

No worries, and just for the record, I used to do almost the same thing, using Free Download Manager 5 at GOG, though I have it set to 1 download, 3 threads.

If you want to avoid the current limitation, you either have to use the dreaded Galaxy, or like myself and many others, you could use gogrepo.py or gogcli or Lgog etc.

You can queue up the downloads with them, and they use the GOG SDK to just get the link when it is needed, so it is fresh and won't expire.

I've made Windows frontends for gogrepo.py and gogcli.exe, though the latter is my preference these days, and doesn't require Python be installed.

https://github.com/Twombs/GOGcli-GUI

https://github.com/Twombs/GOGRepo-GUI