unable to transfer my 2025.2 workspace to 2025.3

Started by Brocher's Mod … on

Topic category: Troubleshooting, bugs, and solutions

Joined Nov 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
unable to transfer my 2025.2 workspace to 2025.3
Mon, 01/19/2026 - 08:05 (edited)

Hey. I'm having issues transfering my workspace from MCRT 2025.2 to MCRT 2025.3. It just dosen't want to.

 

"Import error

Failed to import mod element [mod element]

MCreator failed to import one of the element defined in workspace file, as it has missing mod definition.

MCreator will skip that mod.

Your workspace migth not work properly without some mod elements."

Image

And does that with all my mods element.

 

"Import error.

MCreator skipped import of 185 (all the elements in my mod) mod elements due to missing mod definitions.

Workspace might not work properly.

This error was caused by a corrupted workspace file you used for import."

Image

 

Before I got this kind of problem, my MCreator just wouldn't create the graddle project files. It was just loading infinitly.

Image

It's after uninstalling, reinstalling and syncing it with my remote worspace, that it started not uploading my mod elements.

 

I would love to work again on my mod but yet, can't do so because of this.

 

Any help will be appreciated.

Edited by Brocher's Mod Production on Mon, 01/19/2026 - 08:05
Joined Nov 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Hi klemen, thanks for your…
Mon, 01/19/2026 - 08:07

Hi klemen, thanks for your answer, I have updated my post, and wrote what it was being said on the images you can not see.

Joined Dec 2024
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Try to upload the images to…
Mon, 01/19/2026 - 13:47

Try to upload the images to for example imgur and then send a link, it's hard to understand anything without them

Joined Nov 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
that's the thing, I've…
Tue, 01/20/2026 - 08:34

that's the thing, I've downloaded the plugins in the right version, 2025.3. I even use the same plugins on another workspace and it works with no problems.

Joined Dec 2024
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
What plugins do you use? It…
Tue, 01/20/2026 - 09:00

What plugins do you use? It's definitely their fault 

Joined Nov 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
here is the list of the…
Tue, 01/20/2026 - 11:19

here is the list of the plugins that I have in my folder :

  • arraylist
  • attribute modifiers
  • blockstates
  • blockutils
  • chunk manager
  • configuration files
  • dg-dlib-transform
  • file manager
  • fluid control
  • forge mixins
  • ftao
  • generators (from 1.19.2 to 1.21.4)
  • items tooltips
  • just enough recipes
  • loot modifiers
  • marwinekks-minos procedures plus
  • mcreator vcs (remote workspaces)
  • nerdys better naimation
  • nerdys custom entity models
  • nerdys new curios api
  • nerdys sky renderer
  • redwires plugin
  • toasts

 

I'm not sure that the plugins are the problem because, even if I only load the VCS plugin, it still wouldn't load

Failed to import mod element…
Tue, 01/20/2026 - 15:00

Failed to import mod element [mod element]

So, you will need to uncensor this part. If it is any plugin element, reach out to this plugin

You also listed some incompatible plugins here so don't expect too much

Joined Nov 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
It says : Failed to import…
Tue, 01/20/2026 - 15:30

It says :

Failed to import mod element "StoneHammerBlockDestroyedWithTool"

But, when I click "skip mod element", it says the same thing with all my other 185 mod elements.

I've not yet used any plugin elements.

 

Would you mind help me with the incompatible plugins please ?

Joined Nov 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Little update ! I've fixed…
Sun, 01/25/2026 - 02:32

Little update !

I've fixed everything!

It was a pain in the ass but I'll try to explain it for people that have the same problem as me.

 

Before importing my project in MCreator, I've opened every single elements in a IDE (Microsoft VCS in my situation).

At the beginning of the code, it was writen :

<<<<<<< HEAD (Current change)

  "_fv": 79,

=======

  "_fv": 60,

>>>>>>> branch 'master' of [link to my GitHub repo] (Incoming Change)

What I've done is that I've clicked "Accept incomming change" on every sigle one of the 187 elements.

 

When I launched MCRT, I instantaneously got errors, like a red wall. But, it was all from the same root problem.

error: package BrochersSurvivalModModItems does not exist

 

What I did was that I've deleted these folders :

/src
/build
/.gradle

then reopened my workspace.

 

It has rebuilt and compile everything, untill a new error apeared.

"Import error

Failed to import mod element [Stringer]

MCreator failed to import one of the element defined in workspace file, as it has missing mod definition.

MCreator will skip that mod.

Your workspace migth not work properly without some mod elements."

I've skipped it, launched the game, and my mod worked perfectly.

 

I've also had a texture problem. Besides GUIs, no textures (blocks or items) have been imported. I've just imported manually the textures from another file where all the textures of the mod where.

 

 

I hope this may come to help to people in need! 

Now I'm going to sleep (I've worked on this for 3 weeks)

<<<<<<< HEAD (Current change…
Tue, 01/27/2026 - 16:46

<<<<<<< HEAD (Current change)

This was caused by git merge conflict that was left unhandled

Glad to hear you got it resolved, though!