
forge-essentials
Forge Essentials aims to provide a suite of powerful fully server-side utilities to make running, administrating and using a server better and easier. This mod only needs to be installed on the server and should not be installed at all on the client.
Tags
Creators
Details
12.5.1
Compatibility
Changes
What's Changed
- 1.12.2/scripting improvements phase 1 by @spacebuilder2020 in https://github.com/ForgeEssentials/ForgeEssentials/pull/2698
- Fix Craft command and add the ability to use color in the rename comm… by @spacebuilder2020 in https://github.com/ForgeEssentials/ForgeEssentials/pull/2700
- 1.12.2/client fixes by @spacebuilder2020 in https://github.com/ForgeEssentials/ForgeEssentials/pull/2702
- Fix listing user perms and fetching uuids by @spacebuilder2020 in https://github.com/ForgeEssentials/ForgeEssentials/pull/2710
Full Changelog: https://github.com/ForgeEssentials/ForgeEssentials/compare/12.5.0...12.5.1
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:jnuVxwKf:WJkMFHWI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jnuVxwKf:WJkMFHWI"
}
