Links
Tags
Creators
Details
All versions
1.1
Release
ParCool+ / Compatibility Addon NeoForge Edition 1.14 months ago 11.6K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Changelog
All notable changes to ParCool+ / Compatibility Addon (NeoForge) are documented here.
[1.1] - 2026-04-01
Added
- Entity Model Features (EMF) client integration: registers EMF’s
registerVanillaModelCondition(via reflection) so that during selected ParCool parkour actions the player can use the vanilla model path, improving poses when using CEM player models from resource packs together with Entity Texture Features (ETF) / EMF. - Optional mod metadata in
neoforge.mods.tomlfor Better Combat, Carry On, Player Animator, ETF, and EMF (compat loads only when those mods are present).
Notes
- Fast Run / Fast Swim are intentionally not included in the EMF vanilla-model condition so Player Animator can still take priority there.
- Paraglider-style cases are handled in ParCool itself; this addon does not add a separate Paraglider module.
Requirements (this release)
- Minecraft 1.21.1, NeoForge (see
gradle.propertiesfor pinned NeoForge build). - ParCool ≥ 3.4.3.1 (required).
Added
- Initial NeoForge 1.21.1 release of the compatibility addon fork.
- Better Combat integration to reduce animation clashes with ParCool moves.
- Carry On integration to block ParCool actions while carrying.
- Player Animator integration so Player Animator can win in conflicting animation cases.
- Mixin plugin scaffolding (
parcool_compat_addon.mixins.json) for future / conditional mixins.
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:YpPfINZw:zSCsEKfr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YpPfINZw:zSCsEKfr"
}

