Tags
Creators
Details
1.1.0
Compatibility
Changes
Add 'lockout' functionality. Tested on 1.21.3
Adds this section to the config.yml:
# Should people be prevented from using homes they set before their permissions were adjusted to be lower? (i.e. they
# had permission to set 5 homes before, and now they only have permission to set 3)
lockout:
enabled: false
home: true
homelist: false
deletehome: false #dunno why you'd enable this unless you want people to be completely locked out but okay
Adds this line in the locale.yml, under 'errors'
cannot-use-command: "<red>You currently have more than <dark_red><bold><value></bold></dark_red> homes. In order to use <gray><command></gray> you must first delete some homes.</red>"
Players that have homes.count.bypass will not be affected by this setting
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:eQKpUT7q:ayJIEHCs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eQKpUT7q:ayJIEHCs"
}

