All versions
1.218
Release
1.21810 months ago 3,085
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
- Fixed lagging
- Added title when teleport
- Added actionbar when teleport (update the config and lang file)
Config.yml:
# RtpZone Plugin Config
# How often (in seconds) players should be teleported within a zone
teleport-interval: 30
# RTP (random teleportation) boundaries in the world
# Players will be teleported within this square area (center: 0,0)
x-limit: 4000
z-limit: 5000
# Settings for messages after a successful teleport
teleport-messages:
# Should a large 'title' message appear in the center of the screen? (true/false)
title:
enabled: true
# Should an 'actionbar' message appear above the hotbar? (true/false)
actionbar:
enabled: true
# Minimum Y-coordinate where players can be teleported
# This helps avoid teleporting too deep (e.g., near bedrock)
min-rtp-y: 60
# Default world name where zones teleport players
default-teleport-world: world
# Plugin language. Available options: hu, en, de
language: en
update-checker:
# This is sening messages por operators if there is an update (true/false)
enabled: true
# Zone border particle effect settings
zone-border-particles:
enabled: true # Should particle effects be enabled? (true/false)
color-red: 255 # Red component of the particle color (0-255)
color-green: 0 # Green component of the particle color (0-255)
color-blue: 0 # Blue component of the particle color (0-255)
size: 1.0 # Size of the particles (floating-point number, e.g., 1.0)
duration-seconds: 3 # How long the particle effect should last (in seconds)
density: 0.5 # How densely the particles should appear (the lower the number, the denser, e.g., 0.5)
# Debug mode
debug: false
# Do not change this!!
config-version: 1
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:7riYU27G:dYp5k77b"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7riYU27G:dYp5k77b"
}

