Tags
Creators
Details
Licensed ARR
Published 9 months ago
Updated 9 months ago
All versions
BETA-1.0
Beta
Beta9 months ago 84
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog - v1.0.0-beta.1
Major Update: The Animation Overhaul
This version introduces a completely rewritten animation engine, moving away from basic interpolation to a custom rigid-body physics system.
🛠 New Features & Improvements
- New Animation Engine: Replaced "snapping" door transitions with smooth, eased movements running at 20 ticks per second.
- Rigid Body Rotation: Re-engineered block handling so all parts of a door move as a single unit. Individual blocks no longer "spin" around their own centers during door rotation.
- Advanced Garage Tracks: Implemented a two-stage animation path for Garage Doors. They now lift vertically before tucking back into the ceiling.
- Auto-Orientation Detection: The plugin now intelligently detects the facing direction of doors to ensure Garage and Slider paths are calculated correctly.
- Easing Profiles: Added
SMOOTH,BOUNCE, andLINEAReasing options to the/pp gui. - Synchronized Colliders: Fixed "ghost-blocking" by ensuring the physical collision entity (Shulker) glides in real-time with the visual blocks.
⚠️ Beta Status Notice
- This is the first Beta release of the new animation logic.
- Compatibility: Doors created in extremely old versions of PivotPoly may need to be re-created to utilize the new rigid body system.
- Feedback: Please report any animation glitches or "stuck" doors to our issue tracker.
🐛 Bug Fixes
- Fixed a compilation error regarding
AxisAngle4fmismatch. - Fixed an issue where door blocks would appear stationary if they were passengers of the root hinge.
- Optimized memory usage for long-running door animations.
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:2wA4M2il:hoa8u5du"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2wA4M2il:hoa8u5du"
}

