Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 2 years ago
All versions
1.2.0-SNAPSHOT
Release
Eclipse 1.2.02 years ago 126
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platforms
Paper
Purpur
Changes
- Merge Ignite/Eclipse files to avoid uneccessary management
- Eclipse gradle plugin :
- Updated to
1.2.0Eclipse - Includes AccessWideners for IDE environment
- Bundles the mixin/mixinextras libraries
- Includes the Eclipse jar for development
- Updated to
- Uses
paper-plugin.yml(or.yaml) for mixin defining instead ofmixin-plugin.json - Fix JVM args from not being provided to new
ProcessBuilder- DOES NOT work for args like--noguiyet, making a Paper PR for access to that in plugin bootstrap - Add
MixinPluginAPI access, meaning you can now cast aJavaPluginto aMixinPlugin, and it will provide nullable methods for getting information from Ignite(if any of those is null, then the plugin is NOT a mixin plugin) - Documents the mixins in Eclipse a bit more
- Rewrite the
ModernPluginLoadingStrategyMixinto just use normal injectors rather than using@Overwrite - Better support for library loading with paper plugins
- With mixin plugins, it is HIGHLY different in classloading, and some instances will frankly just fail to apply. I am working on a new feature that will bundle libraries like Fabric Loom does for mixin plugins, but that will be in
1.3.0along with properMinecraftServeroptionset providers for bootstrapping.
- With mixin plugins, it is HIGHLY different in classloading, and some instances will frankly just fail to apply. I am working on a new feature that will bundle libraries like Fabric Loom does for mixin plugins, but that will be in
- Rewrite
PaperGameLocatorto a newEclipseGameLocatorto be more version-agnostic and fix possible jar-corruption of the server jar during Eclipse process init. - Better cleanup of the Eclipse process
- Some more debugging logs
- Better termination output logs
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:2ri1uTe6:CB76gqXr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2ri1uTe6:CB76gqXr"
}

