EPIC treated the problem due to which saving in Borderlands 3 was erased

One of the most common complaints about PC version Borderlands 3 – Sliding conservations. Many users write that they lost several hours of passing because of this. Apparently, the key reason for the problem is the bug in the cloud storage of Epic Games Store.

When a player launches his copy Borderlands 3 On different PCs, the EGS client tries to synchronize the data through the "cloud". If the program discovers that there are different storages in the local and network storages, it offers a choice: download old data from the local storage to the network or download new data from the network storage to the local.

The loading of local data into the network storage rewrites the “saves”, which were already lying there. It seems that the root of the problem lies here: because of the Bag Epic Games Store, I did not show the user a window with a question of cloud conservations and silently sent old local data to the network.

On the website of technical support Epic I recognized the problem. A few hours ago, the company updated the EGS client and added a hotfix that eliminates the error. According to the technical support page, it is impossible to restore the lost conservations.

In the commentary for Polygon Representative 2K Games Specked as follows: “We understand how upset those who have touched this situation, so we work with our partners from Epic, to monitor the situation and make sure that the problem is completely solved. We carefully listen to our community and players and continue to do everything possible to provide everyone with the best impressions ".

September 17, 2019 Rayman the size of an ant – announcing the Rayman mini trailer

September 17, 2019 “The Devil https://bookmakersnotongamstop.co.uk/independent-online-bookmakers/ came to pick up a duty” – Released Trailer Daymare: 1998

Borderlands 3

The best comments

And they write 1 day? This cemetery of the disadvantaged for almost a year now, plus for some time before the announcement (most likely 30 minutes, for which they threw Rootmapu).

If you invest where you need to invest, and not in the "scattering of suitcases", then there will be much less problems. This is what prevented the store at least to an acceptable level before starting its aggressive exclusivity policy? Otherwise every week we hear about the next heap shit problems that Epicians faced.

This whole situation is a visual confirmation of aphorism "Hurry, make people laugh".

The words 2k that the Epic store to the release of the border will become better. They finally forced the cloud storage to work. They also gave people in a beta test to participate.

Do not forget that just a couple of weeks ago on this very Rodmape they pushed pushed Lists of the desired and a basket from the section "soon" to the "Then" section. But in "soon" there appeared overflow overflow.

Their priorities are crystal clean and neither real healthy competition, nor bringing the store at least to a simple but decent state in this list.

On a vapid, by personal experience, one (!) an experienced programmer needs 2.5-3 months to write a similar system. How much is a person in working in Epic Games, and how long is Epic Games Store in the release?

And yes, to roll out really not tested functionality worse than not to roll out the functionality at all. Although what can I say if they missed the problems more serious into their stroke (for example, related to data safety).

Only the lazy did not stumble about this error with synchronization of the saves in the cloud.
I sifted the saves of the ME2 in Origin, the titan of the quest in Steam, and in the area of ​​2016 decided to tightly chopped off all cloud preservations. Stupidly automatically make a backup of all places where they are lying on a local computer.
The fact that the data cannot be restored clear. Everything that happens on the user’s computer, as usual, the user problem.
But, how could one trip on this in 2019, when there is already a wagon of examples?
Moreover, judging by the news, the error is nursery. There is a check on the date, if the dates did not converge, we display the dialog box … And there is a default action that is produced if a jamb occurred above the code.
It seems that in many offices it is not at all in the topic about the department of technical/prog/any other control

Approximately the same as releasing in 2018 the okryza launcher/stroke, having examples of sane storage and launches in mind.

After this fix, a new bug will come out, which will delete the game from the account.
But nothing, it will be possible to tolerate as many as 12%. Steam was also not immediately built!