Tags
Creators
Details
6.0.0-SNAPSHOT
Compatibility
Changes
Infinite Parkour Reborn 6.0.0
Infinite Parkour, IPPlus, and Infinite Elytra Parkour are now combined into one plugin.
Important upgrade information
- Remove the old IPPlus and IEP jars before installing this update.
- Only the new Infinite Parkour Reborn jar should remain installed.
- Stop the server and back up your plugin folders before upgrading.
Missing legacy files are copied automatically:
| Legacy location | New location |
|---|---|
plugins/IPPlus |
plugins/IP/plus |
plugins/IEP |
plugins/IP/elytra |
Existing files are not overwritten, and the original folders are left untouched.
Added
- All former IPPlus game modes
- Multiplayer lobbies and player invitations
- Team Survival and Duels
- Procedurally generated elytra parkour
- Multiple elytra modes and course styles
- Automatic legacy data migration
- Compatibility testing for every supported Paper version
Changed
- Combined Infinite Parkour, IPPlus, and Infinite Elytra Parkour into one jar
- Preserved
/parkour,/ip,/ipp, and/iep - Updated removed and deprecated Paper API usage
- Updated the build system for current Java and Paper versions
- Improved plugin shutdown and reload cleanup
- Improved PlaceholderAPI hook cleanup
Dependencies
- Removed the external
vilibdependency - Removed PaperLib
- Removed the VoidGen requirement
- Added a built-in native void-world generator
- Included the required foundation code directly in the plugin
Supported servers
| Paper version | Required Java version |
|---|---|
| Paper 1.21.11 | Java 21 |
| Paper 26.1.2 | Java 25 |
| Paper 26.2 | Java 25 |
The same jar works across all supported versions.
Fixed
- Fixed custom Bukkit events sharing the same
HandlerList - Fixed lifecycle cleanup for optional integrations
- Fixed several incompatibilities with current Paper APIs
- Fixed legacy components and removed API calls
- Improved cleanup of running tasks, players, worlds, and hooks during shutdown
Links
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:f0CFJW6m:kj90hmhm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:f0CFJW6m:kj90hmhm"
}

