All Classes and Interfaces
Class
Description
We generally will use "client" dependencies when we have to decide between client and server,
since client libraries will usually be a superset of the server libraries.
Utilities for trying to detect in which IDE Gradle is running.
Used to prevent accidental leakage of internal methods into build script DSLs.
The main plugin class.
Model of a mod.
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.
Extends the basic taks for running NFRT with the properties that apply to all subcommands
working with NeoForge or NeoForm data.
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 disambiguation rule will select native dependencies based on the operating system Gradle is currently running on.
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.