1.0.2
Compatibility
Changes
You asked, we listened! > Thanks to the amazing feedback from the community, this update introduces the highly requested /tpahere command! Important Note for existing users: To make the new command work properly, please add the new message string to your messages.yml file (instructions below), or simply delete your old messages.yml to let the plugin generate the updated one.
Add this line under the 'tpa-request' section, right below 'target-msg'
target-msg-here: "<gray>ᴘʟᴀʏᴇʀ <#ffff55>%player% <gray>ᴡᴀɴᴛs ʏᴏᴜ ᴛᴏ ᴛᴇʟᴇᴘᴏʀᴛ ᴛᴏ ᴛʜᴇᴍ."
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:l8yEFN9X:vxxkOYcv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l8yEFN9X:vxxkOYcv"
}

