Skip to content

Backups are inconsistent and unreliable #255

@amihsekai

Description

@amihsekai

Your GTNH Discord Username

blindiota

Your Pack Version

2.8.2 and 2.8.3

Your Server

SP

Java Version

Java 25

Type of Server

Single Player

Your Expectation

Backups are supposed to be a safety net. If something goes wrong, I expect to be able to restore my world to a recent and consistent state with minimal progress loss.
I've set them to run every 3 minutes, so they happen very frequently.
Restoring a backup should put my inventory and world state exactly as they were at that time.

The Reality

Despite being set to run every 3 minutes, sometimes they just stop working, and even when I run /backup start no 'Backup done' notification appears sometimes.
My horse disappeared and I couldn't find it. Whatever happened, I thought I could rely on a backup, just to find out my last one was about 5 hours before, with significant progress behind (exploration and base expansion). I always keep automatic backups enabled.
I proceeded playing without reverting, searching for another horse far away. On the way home, an aura node caught me and my horse died (I also couldn't find the saddle it should've dropped). My patience was thin, so I reverted to the previous backup, which was from a couple of minutes earlier (the moment before I found the horse). Then, I found out the saddle was gone from my inventory.

It's dangerous if these issues keeps happening at any point of the game.

OBS: I actually have set the backups to run every 3 minutes because the unreliability was becoming really stubborn.

Your Proposal

Review the backup system.

Final Checklist

  • I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
  • I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
  • I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions