This error has occurred twice in the last week in a 1.20.1 Realm. This is our first experience with this error in any Realm since joining my first one in 2020.
With the recent 1.20 update we have invested a lot of time in builds, exploration and other game progress. It is extremely discouraging to lose progress. Multiple players on the realm decided to stop playing sooner than they originally planned because of tonight's lost time.
We are discussing cancelling the subscription and moving to a third party service. Occasional crashes or downtime is expected with any cloud service, within the commitments of the terms of service, but losing game progress is unacceptable.
Does anyone know if it's possible to trigger Realm backups manually or more frequently?
Edit: This has happened now a total of four times in one week. This impacts 3 to 6 players at a time, reverting at least 30 minutes, and up to 60 minutes of effort. That is a maximum player-time loss of 6 hours per event. This is unacceptable. Are there any known tips or workarounds to reduce the probability of this issue?
11thNite
This error has occurred twice in the last week in a 1.20.1 Realm. This is our first experience with this error in any Realm since joining my first one in 2020.
With the recent 1.20 update we have invested a lot of time in builds, exploration and other game progress. It is extremely discouraging to lose progress. Multiple players on the realm decided to stop playing sooner than they originally planned because of tonight's lost time.
We are discussing cancelling the subscription and moving to a third party service. Occasional crashes or downtime is expected with any cloud service, within the commitments of the terms of service, but losing game progress is unacceptable.
Does anyone know if it's possible to trigger Realm backups manually or more frequently?
Edit: This has happened now a total of four times in one week. This impacts 3 to 6 players at a time, reverting at least 30 minutes, and up to 60 minutes of effort. That is a maximum player-time loss of 6 hours per event. This is unacceptable. Are there any known tips or workarounds to reduce the probability of this issue?