Tags
Creators
Details
Licensed MIT
Published 4 months ago
All versions
1.3.0-1.21.10
Release
PRT 1.3.0 for 1.21.104 months ago 22
Compatibility
Minecraft: Java Edition
1.21.9–1.21.10
Platforms
Fabric
Quilt
Supported environments
Client-side
Changes
This massive update was made possible with the support of KSEPSP
Breaking Changes
– In rpt:arm_transform, the game variable arm has been renamed to holdArm
New Features:
- Patch System: Allows you to separate vanilla Resource Packs from RPT.
- Swapper System: Texture replacement based on player and item parameters for armor, spyglass, and carved pumpkins.
- First-Person Transformation System: Define custom positions and even animations for the first-person view.
Additions
- New game variables added to
rpt:arm_transform:swing— a value from 0 to 1 representing the hit animation progress.swingArm— 1 if the attacking arm is the right one, -1 if it's the left.useArm— 1 if the item is being used in the main hand, -1 if in the offhand.useTick— the remaining ticks of item use.delta— a value between 0 and 1 representing the frame progress (partial ticks).
- Added a new field
attacktorpt:arm_transform(defaults totrue). If set tofalse, the vanilla attack animation will not play in third-person view. - New global game variables added:
delta— a value between 0 and 1 representing the frame progress.motionX,motionZ,speed,horizontalSpeed— holder's movement and speed data.onGround,isSprinting,isCrouching,isInWater,isInLava,isSwimming,isFallFlying— entity status flags.attackCooldown,attackProgress,usageProgress— data for hit and usage animations.
- Added the
oppositefield forrpt:arm_transform— accepts the same structure astransformbut applies transformations to the opposite arm.
Fixes:
rpt:arm_transformnow works correctly with variables.- Many other minor bug fixes and improvements.
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:kW70KuE2:LETrsDPy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kW70KuE2:LETrsDPy"
}![[RPT] Resource Packs Tweaks](https://cdn.modrinth.com/data/kW70KuE2/477978e2663643fd47c7e11ba6cc61da15cb089a_96.webp)

