MCreator is now open source

After months of work on all the things needed for this to happen, MCreator is finally open source. We hope this will make this project even better than ever. Read on!

I hope that by open-sourcing, more developers will help me with development and thus move things faster. Based on the survey I put out a while ago, this is the case, so I can't wait to see how things will go!

The new repository is located on the MCreator GitHub organization page under the following URL:

https://github.com/MCreator/MCreator

Make sure to star the project on GitHub ;)

Contributing

If you are interested in helping with MCreator development, you are welcome to support this project by opening pull requests. Even if you do not code, you can help by contributing translations, in-app tips, or by donating. Read more on contribution on https://github.com/MCreator/MCreator/blob/master/CONTRIBUTING.md.

A new forum section was opened for discussions on features and changes for the developers. This way we can coordinate new features so we can keep things streamlined and prevent two people from doing the same thing. The other place for coordinations will be the issues page on GitHub and pull request drafts.

Due to a lot of work still waiting for me to complete the open-sourcing process (especially changes on the website), I might not be able to reply instantly to early pull requests and issues, but it should get better after the initial changes.

Issue tracker

The issue tracker will be moved from MCreator's website to GitHub. The current tracker will remain archived, but will soon close for any new tickets. Existing tickets will be migrated to GitHub.

Some other changes on the website to reflect open-sourcing will happen in the upcoming days. Issue numbering will restart from #1 after the move too, existing numbers will not be affected.

Big thanks to our trial moderator Shocking Artist who designed the issue templates for the new GitHub issue tracker.

Documentation

Some of the code is documented, but most of it not yet. I will try to improve this as much as possible relative to the time I will have, of course. To help you get started, I will post pages in GitHub Wiki occasionally with some guides on where to find things in the code and how the MCreator is structured and how things work.

Releases

Releases will remain on the website. Anyone can build their own variant anytime, but officially verified binaries supported by Pylo and maintained will be downloadable on this website as it always was.

Please let us know what you think about this major change in the comments. Also, leave any suggestions and concerns here so we can discuss it. Also, who will be the first contributor, we are waiting? ;)

Comments

does this still mean we can still get plugins

Yes, plugins are and still will be a thing.

ok thanks

but i dont use github :(

For people not having GitHub, there are still bug report and feature request forum sections I still regularly check and consider them as much as tickets ;)

ohh yea ok!

Now I just need to practice 1.16 modding and datapacks then I will try to add them.

Wait a minute. This means I can try to add 1.16 myself once I get 1.16 forge to load a workspace. I will be coding trying to add 1.16 for an hour

If you add full stable 1.16 support in an hour, you are officially the best programmer in the world.

It will take way more than an hour. In an hour I could barely add anything

I am just testing how 1.16 mods work.

I will be spending a week on 1.16 support. Then I will take a break for a day and repeat until I finish 1.16 support.

I currently got a basic generator. It loads in properly but mods don't work.

I suggest you wait unit official maintainers start working on this. Forge is not even ready yet at this point for full generator.

Okay.

I have a generator that loads but mods don't compile properly yet.

For feature request will this be opened as issues or is there going to be some kind of alternate way to submit feature requests to you still, or are you just dropping support for this all together. Because I feel like this was one of the reasons why the community has come so close is that we can ask for features and the devs listen to the requests unlike many developers out there.

Feature requests will be moved to GitHub issues too. I will move to their tracker because it integrates with the workflow of development much better.

For people not having GitHub, there are still bug report and feature request forum sections I still regularly check and consider them as much as tickets ;)

POGGERS

Thanks!