Tags
Creators
Details
6.2.0+1.18-forge
Compatibility
Changes
This is a major version that you should update as soon as possible. Here is a detailed change-log:
- Added support for 1.19.3
- Fixed issues with wrong bounds limits (#10)
- Fixed issues regarding the biomes whitelist (#16)
- Improved speed and reliability (#13, #11, #10, #17)
- Updated Forge & Fabric API
- Fixed minor issues
How to update:
- Delete the old .jar file from the mods folder of the server root
- Move the new .jar to the folder mods of the server root
Permissions: randomtp.command.basic - Execute /rtp[DEFAULT: ALL] randomtp.command.interdim - Execute /dimensionrtp [DEFAULT: ALL] randomtp.command.interbiome - Execute /biomertp [DEFAULT: ALL] randomtp.cooldown.exempt - Ignore cooldown [DEFAULT: OP]
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:rfrPFqYK:W8eQ9s3c"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rfrPFqYK:W8eQ9s3c"
}

