Keep it clean
If you believe that a wish duplicates another one or is not meant for the category, use Options button above to report a duplicate or spam.
Add your wish
If there is an item you wish to have on GOG.com and it’s not yet on the wishlist, please add your wish
Implement automatic patch/build deployment for developers/publishers
Added by
consumerism87 Currently, there is no quick and efficient way for developers to roll out new game builds or patches via GOG. Unlike Steam, where a simple upload on the developer's end is all it takes to make a new build/patch immediately available to those who have purchased the game, GOG seems to have a process where the game files are first submitted by the developer, then manually reviewed, and provided an additional wrapper (with a separate version number) by GOG. Which takes time.
This is not a problem for old games that are no longer maintained. However, for new games with a frequent patch release cycle, this means that customers who opt to purchase a game on GOG will not receive the same level of support as those who buy the game on Steam.
For example, the initial Mac version of Icewind Dale: Enhanced Edition had missing game files- a problem that could have been resolved quickly with an automatic submission process, but instead took a week. A patch for Baldur's Gate II: Enhance Edition, which fixes a number critical issues, is (at the time of writing) not yet available on GOG for Mac and Linux users, despite having been released and submitted over a week ago.
There has got to be a better way.
gliamonster Gog should only be stepping in to package files in cases where the game is badly broken. Doing it routinely is just aggressive branding.
cyion Please! Something has to be done differently.
LordCrepe So much this. At the very least they should speed up the process for fix-heavy patches (as opposed to mostly extra content builds).
KeyperOS Baldur's Gate 1 & 2 EE are at version 2.0.x which has several serious bugs including multiplayer and a auto-changing difficulty slider that have been addressed in version 2.1.
On the other hand, version 2.1 introduces MORE bugs, arguably even more serious in multiplayer. A review process can catch these things.
It appears there are pros and cons with each approach.
a4plz Glad to see this wish skyrocketing in the last few days. It feels strange having to tweet developers asking if they've submitted their latest patch to GOG yet, since the approval process is so slow and invisible. Falling behind the community of a new release is a real hype-killer.
I recommend Cusith's solution below: an optional "direct update" branch separate to GOG's prepackaged installers. We could have the best of both worlds this way.
vsr Absolutely agree with you on this.
This is the biggest -con- GOG has now (if you buy new games, which are covered by developer's support cycle currently, i.e. get patches).
With increase of releasing more new games (which get patches currently) on GOG, this -con- will be more and more obvious to customers.
Cusith I would like this to run along side the current system. You'd have GOG's standard one and an "inbox" version that is the raw files provided by the developer to GOG. Those willing to download the potentially larger block of files could then get stuff faster.
7 comments about this wish