Included content
| Name | |
|---|---|
type - This parameter allows you to specify the type of homes output to text or menu, usage: /homes -type <text|menu>, if not specified, it will default to the one in config.yml./zhomes parse can now be parsed with MiniPlaceholders, allowing you to use placeholders from both MiniPlaceholders and PlaceholderAPI at the same time, without any issues. Also you can now parse without specifing the player.config.yml comments are now translated with the language file (If it's a custom language file, it will fallback to english)NAME, this column is used to store the name of the player, it helps with the offline player getter, allowing you to get the name of the player even if they are offline, and also helps with the performance of the plugin, as it reduces the number of queries to the database when getting the name of the player./homes:home-string - The string that will be used to display the home in the list of homes, it supports placeholders, you can use %home% to display the name of the home and also supports MiniPlaceholders placeholders.others.home-string - The string that will be used to display the home in the list of homes when the player is viewing other player's homes, it supports placeholders, you can use %home% to display the name of the home, and %player% to display the owner of the home and also supports MiniPlaceholders placeholders./zhomes nearhomes & /homes default home-strings now have hover & click effects to teleport to the home. And /zhomes nearhomes has a click effect on the player name to filter the search to the player's homes.Full Changelog: https://github.com/yL3oft/zHomes/compare/3.0.0...3.0.1
| Name | |
|---|---|
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.
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:veAp6a0M:AsOSpJbI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:veAp6a0M:AsOSpJbI"
}