Minecraft Development for IntelliJ: a plugin for mod and server plugin projects

What MinecraftDev solves for mod and server plugin authors

A Minecraft modding project is not a normal Java or Kotlin project. The code references classes that only exist after a platform's build tooling has decompiled and remapped the game jar, mixin classes are rewritten at load time, and the same source tree may be compiled against several loaders. A plain IDE sees unresolved symbols everywhere. MinecraftDev is an IntelliJ IDEA plugin that gives special support for these projects, and its supported platform list is the clearest statement of who it is for: Spigot (including Paper), Sponge, Architectury, Minecraft Forge, NeoForge, Fabric, Mixins, BungeeCord (including Waterfall), Velocity and Adventure. That list spans two different audiences. Server plugin authors on Spigot, Paper, Sponge, BungeeCord and Velocity write against a stable API and mostly care about navigation, inspections and project setup. Client and mod authors on Fabric, Forge, NeoForge and Architectury work with generated sources and mixins, where the IDE has to understand tooling output. If your work is neither, the plugin has nothing to offer you.

How the plugin fits into an IntelliJ project

MinecraftDev is distributed as an IntelliJ platform plugin, so the mechanism is the platform's own extension points rather than a separate server or daemon. The README points to the JetBrains plugin repository as the distribution channel and to https://mcdev.io for information about the project; the repository itself is a Gradle build using the Gradle IntelliJ Plugin, which downloads IntelliJ dependencies and packages the plugin. The source tree carries platform icons under src/main/resources/assets/icons/platform and a mixin-test-data directory at the top level, which tells you mixin handling is a first-class concern rather than an afterthought. Code generation is part of the build: the README states that code is generated during the build task and that ./gradlew generate runs generation without a full build, adding that the task is necessary to work on the code without errors before the initial build. That is a useful signal about how the plugin is put together, and it is also a warning for anyone building from source: a fresh clone is not immediately compilable in the IDE until generation has run. What the README does not describe is the internal architecture, the individual inspections, or how the plugin discovers a project's platform. Those are undocumented in the README.

Installing MinecraftDev from the JetBrains plugin repository

The README gives one installation path and it is the IDE's own plugin browser, not a manual download. Open File -> Settings -> Plugins, click Browse Repositories at the bottom of the window, and search for Minecraft. Install from there and restart IntelliJ to activate the plugin. The plugin is also listed on the JetBrains plugin repository at plugins.jetbrains.com/plugin/8327 if you prefer to check the listing first.

There is no command-line install step in the README, and no configuration file to edit. After the restart, opening a supported project should give you the platform-aware behaviour the plugin advertises; the README does not enumerate what changes in the editor, so treat the first project you open as the real test.

If you want to build the plugin itself rather than install it, the README requires JDK 21 available to Gradle and gives these commands:

./gradlew build
./gradlew runIde
./gradlew generate
./gradlew format

The build output zip lands in build/distributions, runIde launches a sandboxed IntelliJ with the plugin loaded, generate runs code generation on its own, and format applies ktlint. For IDE setup the README recommends two Gradle tasks, which configure ktlint style settings and add a pre-commit formatting hook:

./gradlew ktlintApplyToIdea addKtlintFormatGitPreCommitHook

JDK 21 is the only stated prerequisite, and the README suggests Adoptium if you need to install it. Nothing in the README describes uninstalling or downgrading the plugin.

Where MinecraftDev is the wrong tool

The plugin is an IDE extension, so it only helps inside IntelliJ IDEA. If your team builds on the command line and edits in VS Code, Eclipse or vim, MinecraftDev does nothing for you, and no part of it is reusable outside the IntelliJ platform. The same applies to CI: the README documents Gradle tasks for building and testing the plugin itself, not a headless checker you can drop into a pipeline for your mod. A second limitation is version coupling. The releases are named against IDEA release lines, with 1.8.22-2026.2, 1.8.22-2026.1 and 1.8.22-2025.3 all published on 2026-08-31. That naming is a strong hint that the plugin tracks platform versions rather than abstracting over them, and it means an older IDEA build may not have a matching release. The README does not state a minimum supported IDEA version, so this is something to confirm in the plugin repository listing rather than assume. Finally, the documentation is thin. Installation, dependencies, building and the style guide are covered; project configuration, supported Gradle plugin versions and troubleshooting are not. If you need a documented configuration surface, this is not it.

MinecraftDev compared with generic JVM IDE tooling

The real alternative is not another Minecraft plugin; it is using IntelliJ IDEA with its built-in Java and Kotlin support plus your platform's Gradle or Maven plugin, and accepting that generated sources and mixins will look broken until you configure source roots by hand. That approach is more work per project but has no version coupling to a third-party plugin and no extra extension to keep updated. A second alternative is the platform's own tooling, for example the Gradle plugins published by Fabric or Forge, which handle decompilation, remapping and run configurations. Those solve the build problem; MinecraftDev addresses the editing problem. They are complementary, not competing, and the difference in approach matters: build tooling produces the artifacts and run tasks, while an IntelliJ plugin changes what the editor understands about the code you are reading. If your pain is that gradlew runIde does not launch, a plugin will not fix it. If your pain is that every game class shows as unresolved in the editor, build tooling alone will not fix that either.

Maintenance, releases and the LGPL-3.0 licence

The repository is not archived and the last push was on 2026-09-09, with the most recent releases published on 2026-08-31 for three IDEA lines. That is a recent cadence, and the README also references nightly builds for 2025.3, 2026.1 and 2026.2 through a TeamCity instance, plus an OS test workflow on GitHub Actions. For a plugin that must track IntelliJ platform releases, that structure is what you would expect. The upgrade cost is the part to think about: because releases are keyed to IDEA versions, upgrading your IDE can put you ahead of the newest plugin release, and the README does not document rollback or a compatibility matrix. Budget for checking the plugin repository listing after each IDE upgrade. The licence is LGPLv3.0-only, per the README and license.txt. For most users this is a non-issue, since you install a binary plugin rather than link against it. If you fork the plugin or embed its code in your own product, the LGPL's terms on derivative works and source availability apply, and that is a question for a lawyer rather than for this article. The README does not discuss commercial use or redistribution.

Editorial conclusion

Adopt MinecraftDev if your mod or plugin work already happens inside IntelliJ IDEA and you want platform-aware editing for Fabric, Forge, NeoForge, Spigot, Sponge, BungeeCord or Velocity without leaving the IDE. Skip it if you build from the command line in another editor, or if you need a documented configuration surface; the README covers installation, building the plugin and the style guide, and nothing about settings or rollback. Verify first that your IDEA build matches a release line: the current releases are 1.8.22-2026.2, 1.8.22-2026.1 and 1.8.22-2025.3, published on 2026-08-31, and the plugin repository will show whether your IDE version is covered.

Frequently asked questions

Official sources

1. License: LGPL-3.0
2. minecraft-dev/MinecraftDev on GitHub
3. Project website
4. README
5. Releases