Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 weeks ago
Updated 8 hours ago
All versions
0.2.31
Release
RP Engine 0.2.3123 hours ago 72
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.4
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
More model events, animation fixes, and chat text fixes
Integrations
- Model break events now identify the specific model copy and hitbox that was hit.
- Model interaction events now work with Studio models and include the specific model copy and clicked position.
- Custom actions can now run once a model is placed, with access to the placed model and its source item stack.
- Model seat events now include the specific model copy and seat vehicle.
- Entity death events now expose the killer and let integrations modify the drops.
- Item use events now include the clicked block face.
- Resource pack send events now include the built pack, with an ID that matches Bukkit's resource pack status events.
Fixed
- Models already in the world now animate when playback starts after an animation is added through Studio.
- Fixed blank letters in chat text effects and incorrect rendering of animated rank tags.
0.2.29: The same, published twice
- No changes from 0.2.28: the same
ModelPlaceEvent.stack()was built twice on one evening and released under both numbers.
0.2.28: The item a model is placed from, for developers
- For developers:
ModelPlaceEvent.stack()is the stack in the player's hand a model, piece or vehicle is being placed from, so a listener can read what the item carries (its persistent data, name, lore) and move it onto the placement. Null when a plugin placed it withModels.place.
0.2.27: /rp models finds Studio models
- Fixed:
/rp modelsonly listed models placed from a content folder, so a Studio model standing right beside you came back as "No models". Studio models are listed now too, asstudio:<id>. - For developers:
Models.animateis for a model put on an entity withbind, and answers false for a placed one. The javadoc now says so, and shows the call that plays on a placed model:at(entity)andplayon the placement.
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:T9lWNa2Y:66FjmHTL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:T9lWNa2Y:66FjmHTL"
}

