All Classes and Interfaces
Class
Description
Used to customize the groups of tasks generated by MDG.
The primary task for creating the Minecraft artifacts that mods will be compiled against,
using the NFRT CLI.
Holds data files (such as ATs) to be used or exposed.
Access Transformers and Interface Injection Data are treated in a common way as "collections of data files",
which can be declared via a
DSL, and have an associated configuration for internal
use by the plugin and the publication of these files.Use the NFRT CLI to download the asset index and assets for the Minecraft version used by the
underlying NeoForge/NeoForm configuration.
Utilities for trying to detect in which IDE Gradle is running.
Implementing classes are responsible for registering
ideSyncTask with their IDE.Used to prevent accidental leakage of internal methods into build script DSLs.
Applies defaults for the Gradle attributes introduced by the Minecraft Dependencies modules.
The source of this attribute is the list of dependencies declared by the server and client Minecraft distributions.
The workflow needed to produce artifacts and assets for compiling and running a mod.
The main plugin class.
After modding has been enabled, this will be attached as an extension to the project.
Model of a mod.
Internal API provided to the NeoForge development build scripts.
This is the top-level
neoForge extension, used to configure the moddev plugin.Configures aspects of the NeoForm Runtime (NFRT), which is used by this plugin to produce
the Minecraft artifacts for compiling and mods.
Applies basic configuration for NFRT tasks.
Base task implementation for running the NFRT CLI, regardless of which sub-command is used.
When launching other Java programs externally, we have to pass through system properties that
change network settings, such as proxies and TLS trust settings.
This attribute is used to differentiate between the different native libraries used by Minecraft.
Allows configuration of Parchment mappings for userdev.
This plugin acts in different roles depending on where it is applied:
At the project-level, it will add the required repositories for moddev.
At the settings-level, it will add the required repositories to the dependency management block, and add a marker plugin to the Gradle instance to prevent the
repositories from being added again at the project-level.
By extending JavaExec, we allow IntelliJ to automatically attach a debugger to the forked JVM, making
these runs easy and nice to work with.
Model of a run.
Used to enable and configure the JUnit integration.
Sourced from the userdev config json.
Models the changing capabilities of the modding platform and Vanilla, which we tie to the Minecraft version.