1.0.5
Compatibility
Changes
ParkourPro & ParkourProLite โ v1.0.5 A focused bug-fix and quality-of-life update addressing several reported issues and adding a handful of useful improvements.
๐ Bug Fixes Death handling โ Players who die during a parkour run now keep their inventory and respawn at their last checkpoint or reset location, instead of being sent to world spawn. Inventory restore โ Parkour items are now properly cleared before the player's saved inventory is restored, fixing a bug where items wouldn't return to slots 3, 4, and 5. Pressure plate spam โ The "already in parkour" message is now debounced (10-second cooldown), so stepping on a plate repeatedly no longer floods chat. Command block teleports โ Teleports triggered by command blocks no longer accidentally cancel an active parkour run. Admin bypass scope โ Admin bypass now only applies to /parkour subcommands, not to all commands while in parkour. Wizard double-fire โ Item-use events in the creation wizard are debounced to prevent double activation on 1.8.
โจ Item Lore Rework (ParkourPro only)
The hidden ยง0PK: marker previously appended to item lore has been removed entirely. Item type is now detected by material + display name, giving you full control over lore. Default lore in config.yml is now &6PK:&eTELEPORT, &6PK:&eRESET, and &6PK:&eCANCEL โ fully editable or removable.
๐ฌ Messages Any message in messages.yml can now be silenced by setting it to "" โ no message will be sent at all.
๐ค Discord (ParkourPro only)
The /scoreboard command description and option description are now configurable via config.yml:
yamldiscord: command-description: "Show the top players for a parkour" option-description: "Name of the parkour (auto-detected if only one exists)"
/parkour reload now re-registers the Discord slash command instantly โ no server restart needed when changing descriptions. The parkour argument for /scoreboard is now optional โ if only one parkour exists, it is auto-detected.
Thanks for all the reports and feedback that made this update possible. As always, feel free to open an issue or reach out if you run into anything!
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:i0Ccz6aS:6dBwSjqD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:i0Ccz6aS:6dBwSjqD"
}

