Remote workspaces support (2023.2+)

Supported MCreator versions
2023.2
2023.3
2023.4
2024.1
Tags / plugin type
Java plugin
tree
Downloads:
4218
Upvotes: 61
About the plugin

This plugin is the replacement for the old native VCS (Version Control System) support by MCreator.

 

After 3 years of being a part of the software, it looked like the remote workspaces system is not popular enough to keep it in the core for any longer. The reason for this may be the fact that the integration only supported a limited set of features the involved system (Git API) could offer. So, as the maintainers did not have the time to dedicate to it, the system was migrated to a Java plugin for it to gain a chance to get more features supported faster than if it was included in the core software.

The plugin can be installed in the 3rd snapshot of 2023.2 update and higher versions by anyone using the system in earlier releases, and there will be literally no change in the workspace.

 

Releases for older versions are available on plugin's GitHub page.

Changelog:

2024.1.4 (Draft)

  • <placeholder>

2024.1.3

2024.1.2

  • [Bug fix] Plugin's actions and tab could disappear from workspace

2024.1.1

2024.1.0.1

  • Dropped earlier versions support due to breaking change in supported versions validation

2023.4.1

  • Progress dialogs are now displayed during some time-consuming operations
  • [Bug fix] Conflict resolve dialog could not be resized
  • [Bug fix] Deleting workspace file locally/remotely was making further sync attempts impossible
  • [Bug fix] Checking out different branch had no effect on the workspace
  • [Bug fix] Remote branches could not be deleted
  • [Bug fix] Branches with unmerged commits could not be deleted

2023.3.1

  • Ported to 2023.3
  • Added support for fetching/renaming/deleting branches
  • [Bug fix] Committer name could be set improperly in some cases

2023.2.2

  • Added "Rollback local changes" action
  • [Bug fix] Plugin caused MCreator to freeze on MacOS devices

2023.2.1 (Initial porting)

  • Initial migration from MCreator core
  • New branch dialog now responses to invalid branch name definition
Project members
Maintainer
Former developer
Texture designer
License
GNU General Public License version 3 (GPLv3)

Plugin downloads
2024.1.3 - mcreator-vcs-2024.1.3.zipUploaded on: 04/22/2024 - 18:24   File size: 3.58 MB

Comments

The 2024.1.1 version is missing Push/Pull Buttons, or at least for me. So how do I pish/pull in this version?

I tried getting this for my mod workspace in 1.19.2 (mcreator 2023.2) but neither downloads work. the 2023.4.1 says incompatible version, and the 2024.1.0.1 says missing minversion.

Hello, I am trying to make a commit to the GitHub repository I made for my mod, but whenever I try to do that and error pops up every time saying "not authorized". I am on 2023.4. Does anyone have any ideas how to fix this?

Hi, I’ve encountered an issue with merging (When you choose to keep your changes or theirs, local or remote). I am able to select whose changes I want to keep but whenever I continue after I have chosen what I want to keep, the window remains open and no merging occurs. Am I just not noticing something? I am using 2023.4, Forge for 1.20.1.

Hello, I have the same problem as Oofeiro.
I still use 2023.3 because of a NeoForge plugin, that's only available for that version. I've downloaded the plugin through GitHub. Maybe you could try updating the 2023.3 version to the same one as MCreator's?

Hello, I have a problem
I installed the plugin and put it in the plugins file, but when i try to connect to a remote workspace, it always says "error, the remote repository is not a MCreator workspace or is corrupted" in all cases, even if it was created 5 min ago, and i can't understand how it could be corrupted. And I did everything good, I created a github repository and on mcreator i linked the mod to it.
Help please

You should just create the repository without adding any files or branches manually - in this case it would be empty. It's not possible to link existing local workspace to a non-empty remote repository (with at least one branch).
However, I don't remember the word "corrupt" being used in any of the plugin's messages.
Please consider opening a bug report on the issue tracker and providing more details there (the platform you're using, some screenshots or a video would be useful too).