Automatic full-workspace backups

Started by SnailsAttack on

Topic category: Feature requests and ideas for MCreator

Joined Oct 2020
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Automatic full-workspace backups

MCreator has a workspace backup feature, but it only seems to cover a very narrow range of cases concerning corruption of the workspace .mcreator file.

On rare occasions, I have procedure elements become wiped out or lost when saving and exiting the element or exiting the workspace, which can't be reloaded from a .mcreator backup.

Additionally, sometimes I just accidentally delete elements by mistake.

The easiest solution to lost progress due to these problems is if MCreator could create manual or automatic backups of the entire workspace (except the 'run' folder), or preferably just the files that are required.

On rare occasions, I have…
Sat, 02/08/2025 - 11:12

On rare occasions, I have procedure elements become wiped out or lost when saving and exiting the element or exiting the workspace, which can't be reloaded from a .mcreator backup.

This should not happen in 2024.4 without any plugins that have bugs by themselves that cause this.

The easiest solution to lost progress due to these problems is if MCreator could create manual or automatic backups of the entire workspace

This would be a resource-heavy process that would also require blocking user input while it is being made.

I recommend using https://mcreator.net/plugin/97468/remote-workspaces-support-20232 instead and doing own revisioning. This is how software development projects usually track and backup their development process

Joined Oct 2020
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
This should not happen in…
Thu, 02/20/2025 - 05:55

This should not happen in 2024.4 without any plugins that have bugs by themselves that cause this.

I'm on version 2024.4 and I'm not using java plugins or an unofficial generator plugin.

I mainly just use plugins that provide additional procedures and event triggers, which I can't imagine could cause procedures to become corrupted during the saving process. I suppose it's possible, though.

This would be a resource-heavy process that would also require blocking user input while it is being made.

Today I found that restoring a corrupted procedure only requires a backup of its .mod.json element file, which have a file size of like one kilobyte each.

The functionality to create backups of these would be much simpler than full workspace backups, and could still be quite useful