Corruption of large elements - Bug Report

Started by gendalfons on

Topic category: Troubleshooting, bugs, and solutions

Joined Oct 2025
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Corruption of large elements - Bug Report

MCreator 2025.2
Full version: 2025.2.28610
Current recommended major version: 2025.2
Workspace element format version: 79
OS architecture detected: 64-bit OS (x86_64) Bundled JVM architecture: 64-bit JVM
-------------------------------------
I’m the creator of mods such as Sea Dwellers, Farmers Structures, Dragon Survival, Gothic RPG, and many others. For years, I’ve been dealing with this bug, and I’ve finally had enough - I’m writing here to ask for help or for it to be fixed.

Problem: when you work for a long time on a LARGE procedure, at some random point while connecting code blocks, the program may completely destroy the JSON file of that procedure and all other procedures that were open at the same time. For example:

1. I was working on TamedBeeRightClickedOnEntity.mod.json (procedure) and also had TamedBeeUpdate.mod.json open (another procedure).  
2. I tried to add something to existing blocks in the editor (in MCreator, not by editing the JSON manually), and suddenly it became impossible to interact with any elements in that "Scratch" like workspace. If you close it without saving, your procedure will still be lost anyway and replaced with:

{
"_fv": 79,
"_type": "procedure",
"definition": {
  "skipDependencyNullCheck": false
}
}

3. When you try to reopen the procedure, all you get is a blank page with no base “select trigger” header. It corrupted.

All I have left as a developer are TamedBeeRightClickedOnEntityProcedure.class and TamedBeeRightClickedOnEntity.class, but they’re completely useless without TamedBeeRightClickedOnEntity.mod.json. Backups like "bee_queen_ds.mcreator-backup_20251026_081722" are USELESS — they don’t save the elements folder, which is a huge oversight considering how common this issue is. The only way for me as a developer is to endure this problem like a samurai and make MANUAL backups of the entire workspace, ignoring the built-in backup system.

All the files I still have are listed below in the Google document.
-------------------------------------
[google link deleted by anti-spam system, lol]
-------------------------------------

Joined Oct 2025
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Clarification: I do NOT have…
Sun, 10/26/2025 - 08:15

Clarification: I do NOT have any plugins.

Joined Dec 2023
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
I had the same problem, and…
Sun, 10/26/2025 - 10:49

I had the same problem, and it still happens to me sometimes. Unfortunately, there is no way to completely fix this problem for good.

However, there are a few things you can try.

1 - Export large procedures every 5 minutes. This will help you minimize the damage.

2 - Collapse procedure blocks. This CAN reduce the likelihood of code corruption.

I hope that helps D:

Joined Oct 2025
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
_Spectrall, When creating a…
Sun, 10/26/2025 - 13:51

_Spectrall, When creating a post on the forum, the link that leads to “create a bug report here” is broken.
But I repost it again on github.