Tags
Creators
Details
Licensed MIT
Published last year
Updated 5 months ago
All versions
1.0.3
Release
xJumPads 1.0.35 months ago 279
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
xJumPads v1.0.3 - Live Edit & Dynamic Animations! ๐
โจ Live Customization
- In-Game Editing: Added
/jp particle <name> <type>and/jp animation <name> <type>to customize JumpPads on the fly! No need to edit config files manually. - Tab Completion: Intelligent tab completion for all Minecraft particles and our new custom animation presets, making the setup extremely easy.
๐จ Premium Visuals
- Dynamic Animations: Choose from new preset animations for your JumpPads:
LEVITATION,SPIN, andSMASH! Watch your players fly in style. - Ambient Block Sounds: You can now enable passive ambient sounds on idle JumpPad blocks (
idle-particles.sound) to make them feel alive! - Centered Effects: All launch sounds and particles are now perfectly anchored to the block itself instead of the player location, giving a much more realistic and premium effect.
โ๏ธ Engine & Optimization
- O(1) Spatial Optimization: Re-engineered the JumpPad detection algorithm. It now checks exact block locations via HashMaps, significantly reducing CPU usage during player movement. Supports thousands of players without dropping a single TPS!
- Flexible Permissions: You can now set
permissions.usetodefaultornoneinconfig.ymlif you want all players to use pads by default without checking any permission nodes. - Sleek Update Checker: Redesigned update notifications in-game for a much cleaner look, with support for Spanish!
Enjoy the ultimate JumpPad experience!
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:MjPDa0DW:Ji3WqnUc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MjPDa0DW:Ji3WqnUc"
}

