In a recent announcement, GOG has revealed a significant change to their Galaxy Cloud Saves system. Starting August 31st, 2024, GOG will impose a hard limit of 200MB per game for cloud saves, and any saves exceeding this limit will be purged. This move has sparked a debate among gamers, raising concerns about data loss and the implications of such restrictions.
The Change and Its Rationale
GOG explained the decision, citing the ever-increasing size and number of games, which in turn escalates the demand for cloud storage. The company stated, “These limits ensure that all players have access to sufficient and manageable space for their game progress, and that we keep the associated costs under control. By optimizing our storage allocation, we aim to continue providing a reliable and user-friendly platform for everyone.”
While the rationale is understandable from a cost-management perspective, the execution raises significant concerns. The policy dictates that any save files exceeding the 200MB limit per game will be deleted, starting with the oldest files until the remaining data fits within the allocation. This measure puts the onus on players to manually check and manage their save files to avoid potential data loss.
Comparing the Competition
When juxtaposed with Steam’s cloud save policy, GOG’s limitations appear draconian. Steam does not enforce a specific hard limit per game. Instead, it offers a dynamic allocation of storage space, allowing some games to use only a few megabytes while others can occupy several gigabytes. For instance, Baldur’s Gate 3 can consume over 1GB of cloud storage on Steam, whereas a smaller game like Vampire Survivors may use only around 4MB. This flexibility ensures that players do not have to worry about arbitrary storage limits impacting their gaming experience.
The Impact on GOG Players
GOG’s decision to impose a hard limit raises several practical concerns. Modern games, especially those with extensive save data, can easily surpass the 200MB threshold. RPGs with multiple save points, mod-heavy games, and titles with large, complex worlds are particularly vulnerable. Players of such games are now tasked with the tedious process of regularly checking their save files to prevent automatic deletion.
This policy could deter gamers from utilizing GOG’s cloud save feature altogether, as the threat of losing progress could outweigh the convenience of cloud storage. Gamers might revert to local saves exclusively, which undermines the primary benefit of cloud storage—data security and accessibility.
A Question of Priorities
GOG’s new policy highlights a critical question: should cost management take precedence over user experience? While the company’s attempt to control expenses and optimize storage is valid, it should not come at the cost of user satisfaction. GOG has built its reputation on being a user-friendly, DRM-free platform that prioritizes gamer interests. However, this new policy seems to contradict that ethos.
There are alternative solutions that GOG could explore. For instance, implementing a tiered storage system where users can purchase additional cloud storage, similar to models used by other digital services, would offer a more user-centric approach. This would allow players with higher storage needs to opt into a plan that suits their requirements without compromising the experience of the broader user base.
GOG’s decision to impose a 200MB limit per game on cloud saves and the subsequent purge policy marks a contentious shift in their approach to cloud storage. While the company aims to manage costs and ensure equitable storage distribution, this move places an undue burden on players, potentially compromising their gaming experience. As the digital gaming landscape evolves, striking a balance between cost efficiency and user satisfaction is crucial. GOG must consider more flexible and user-friendly alternatives to maintain its standing as a beloved platform in the gaming community.
About the Author
