MCreator is a Java mod-making IDE with a graphical front end and a code editor

Two ways in, a visual interface and a code editor

MCreator is a piece of software for making Minecraft Java Edition mods, Minecraft Bedrock Edition add-ons, resource packs and data packs. The project description puts the two entry points plainly: an intuitive easy to learn interface, or an integrated code editor.

That pairing is what distinguishes MCreator from a bare code generator or a bare IDE. The visual route means a mod can be assembled from predefined pieces without writing Java, and the repository topics name blockly, code-generator and ide alongside minecraft, minecraft-tool, mod-maker and stem. The editor route means the same project can be opened and edited as code when the predefined pieces are not enough, rather than the tool being a dead end once you outgrow it.

The stated audience is broad. The description says it is used worldwide by Minecraft players, aspiring mod developers, for education, online classes and STEM workshops, and the site has a dedicated education page at mcreator.net/education. That is a meaningful signal about the design. A tool used in a classroom has to be installable on a machine an administrator controls, has to produce a result a student can show, and has to hide as much of the build toolchain as possible, because a workshop is not the place to debug a Gradle dependency resolution.

The application is written in Java, the build is Gradle, and the repository layout is a conventional Java project with src/, platform/, plugins/, lib/ and gradle/ directories, plus settings.gradle and build.gradle at the top level.

This repository is the source, the binaries are elsewhere

The README opens with a point that changes what a visitor should expect from the repository. This repository page is for people looking to contribute to MCreator. To download the MCreator distribution and to engage in the community, you go to mcreator.net.

That split is worth understanding before you clone anything. The GitHub repository is the source of the application, and the site is the distribution channel and the community hub. The download link goes to mcreator.net/download, and the support page at mcreator.net/support holds the support resources, the forums and the knowledge base.

There is a third distribution channel with an interesting twist. You can also download MCreator from the Microsoft Store as a donation to the project, and the README notes that you get automatic updates as a bonus. Buying the app through the store is framed as a donation rather than a purchase, which is an unusual arrangement and explains how a GPL application with a trademark policy can sit in a storefront.

The releases are dated with a three-part version, 2026.3.41718 on 2026-10-11, then 2026.3.38715 on 2026-09-20 and 2026.2.33518 on 2026-08-14. The pattern suggests a year.release.build sequence, so a user can compare two builds at a glance. The last push to the repository was on 2026-10-14, and the repository is not archived.

There is also a Javadoc badge pointing at mcreator.github.io/MCreator, so the generated API documentation for the modding framework is published as a site rather than only as a build artefact.

Building from source needs a recursive clone and Gradle

The development instructions are short, and the one non-obvious flag is the important one.

git clone --recursive https://github.com/MCreator/MCreator.git

The --recursive flag is not optional in practice. A Gradle project of this size normally pulls in submodules, and a plain clone leaves those directories empty, which produces a build failure that does not obviously point at the cause.

MCreator uses the Gradle build system to manage building and exporting, and the runMCreator task runs a test MCreator. The README recommends using IntelliJ IDEA for development and testing, and points at the MCreator developers wiki for the development process and tips. The wiki being a separate destination matters, because the README is a starting point rather than a development manual.

The build layout in the repository explains the multi-target nature of the project. The platform/ directory is the application itself, src/ is the source, plugins/ holds the plug-in side, and lib/ holds bundled libraries. There is a build.gradle and settings.gradle for the Gradle build, gradlew and gradlew.bat wrappers, gradle.properties, and a crowdin.yml.

The workflow badges in the README show a test workflow on the master branch, and a code quality gate runs through the pull request process. The contributing guidelines live in CONTRIBUTING.md, and the README also has an explicit rule for contributions: you must sign the MCreator CLA before the code can be used, handled through a cla-assistant.io integration. For an open source project, a required CLA is a meaningful policy, and it is the first thing a potential contributor needs to know.

The licence has exceptions, and the trademark does not transfer

The licensing section is the most carefully worded part of the README, and it is worth reading in full before you redistribute anything.

MCreator is licensed under GPL-3.0, with exceptions implemented as specified in section 7 of GPL-3.0, if not otherwise stated in source files or other files of the project. Copyright 2020 Pylo and contributors. There is a LICENSE.txt at the top of the tree, plus a LICENSE-header.txt, which is a per-file header used to mark the licence on source files that are not otherwise covered by the top level statement.

Section 7 of the GPL is the mechanism for additional permissions, and the effect here is that some files carry an exception to the default terms. The phrase if not otherwise stated in source files or other files of the project is the important part, because it means the per-file terms vary.

The trademark policy is separate and specific. MCreator is a trademark of Pylo, and custom distributions of the software may not include the Pylo or MCreator trademark, that is the trademark name and the logo, so as not to confuse the software with the official distribution. The brand files in the repository are explicitly not covered by the GPL-3.0 licence.

That gives a workable arrangement for an educational tool. A school can build and distribute a modified MCreator for its own classroom, and it cannot ship the official logo and call the thing MCreator.

Third-party licensing is handled in the repository rather than in a single file. License files, attributions and credits for the third-party libraries and projects are located in the license subdirectory, which is a large collection for a project of this size.

Microsoft's mappings come with their own conditions

The section on code generators and Minecraft mappings is the one that most directly affects the person making a mod rather than the person making the tool.

The README says some code generators use official Minecraft mappings, and that the use of these mappings is covered under a license by Microsoft, and that you should be fully aware of this license and the fact that your mod may use these mappings. The quoted license text says the mappings are provided as-is and you bear the risk of using them, that you may copy and use them for development purposes but may not redistribute the mappings complete and unmodified, that Microsoft makes no warranties, express or implied, and that use and modification of the document or the source code in any form of Minecraft: Java Edition is governed by the Minecraft End User License Agreement.

That is a real constraint on distribution. If a generated mod embeds the mappings, the mod author inherits the obligation not to redistribute them complete and unmodified, which is a different position from the one that vanilla Minecraft players are in.

The README also states, in a notice of its own, that MCreator is not an official Minecraft product and is not approved by or associated with Mojang or Microsoft. That disclaimer is consistent with the trademark position and with the use of the mappings, and it is the reason the project can exist at all in this form.

The trade for a mod author is a workable one: the tool generates code against the official names, so the mod works with the current game, and the mod author accepts a licence obligation in exchange for not having to reverse engineer the obfuscated names by hand.

Translations are a separate contribution stream

The README gives translations their own section, and the mechanism is Crowdin.

There is a crowdin.yml at the top of the repository, and the tip points at translate.mcreator.net, where the README says you can join to translate MCreator into your language, and suggests the language if it is not on the list yet.

The crowdin.yml at the top of the repository ties the portal to the codebase, so translation work sits alongside the source rather than in a separate repository.

For a tool used in classrooms, this is more than a nicety. A class in a country where English is not the language of instruction is a realistic place for a Minecraft mod, and an interface in the students' language is a large difference between a workshop where everyone follows along and one where the teacher narrates. The existence of a public translation portal with a language request mechanism suggests the project treats this as an ongoing contribution stream rather than a one-off.

The primary language of the repository is Java, and the licence file mentions Pylo as the copyright holder, with a donate link to mcreator.net/donate in the badges, which is a small indication of how the project is funded.

Editorial conclusion

MCreator suits someone who wants to make a Minecraft mod without writing the whole thing from scratch in a raw Forge or Fabric setup, and it is the wrong tool for a modder who already works in a normal Java IDE and wants the full Gradle project directly. Before contributing, note that the project requires a signed MCreator CLA before code can be used, and read the licence section, because the GPL-3.0 grant carries the section 7 exceptions and the Minecraft mappings are licensed separately by Microsoft. Verify first that the output format matches your target, since Java Edition mods, Bedrock add-ons, resource packs and data packs are different artefacts.

Frequently asked questions

Official sources

1. Issues
2. MCreator/MCreator on GitHub
3. Project website
4. README
5. Releases