1.0.1.2
Compatibility
Changes
Changelog – EnderShare v1.0.2.2
✔ New Feature It is now possible to configure the default and admin permissions in the config.yml file. This configuration is generated by default when the plugin is first run, and you can modify it as needed:
//Commands that ALL players are allowed to use by default. default-allowed-commands:
- endershare.share
- endershare.unshare
- endershare.partner
- endershare.info
//Commands that ONLY ADMINS (OPs) are allowed to use by default. admin-allowed-commands:
- endershare.use // /ec (open enderchest)
- endershare.reset // /ec reset
- endershare.version // /ec version
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:cYgdRLca:6JPrbRBU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cYgdRLca:6JPrbRBU"
}

