1.2.0
Compatibility
Changes
Added experimental on-tp-commands! With this new release, almost all previous bugs have been solved.
In addition to bug fixes, this release brings on-tp-commands which is a config that allows the console to run commands on the successful teleportation of players!
Example:
cavetp:
aliases:
- cave
- randomcave
type: random
description: Teleport to a random cave!
origin: 0,64,0
min-radius: 100
max-radius: 5000
cost: 100.0
worlds:
- world
biomes:
- forest
- desert
- beach
- jungle
- badlands
- taiga
- snowy_taiga
- frozen_river
y-margin: cave
on-tp-commands: # experimental
- setblock {x} {y} {z} torch # so the player can see
NOTE:
All on-tp-commands are run AFTER the chunk is loaded (or estimated 40 ticks/2 seconds) and the player is teleported regardless of what the command is. There will most definitely be customization for this in the future!
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:QiEB0DYw:LKQA4kmI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QiEB0DYw:LKQA4kmI"
}

