Tags
Creators
Details
0.6.0
Compatibility
Required content
Changes
Emote 0.6.0
Highlights
-
Added a web converter for turning BD Engine projects into Emote datapacks.
- Import projects directly in the browser and edit emote metadata.
- Preview the model and manually assign head, body, arm, and leg parts.
- The previous Python converter has been replaced by the web converter.
-
Redesigned the emote datapack format.
- Emote metadata is now stored in
data/<namespace>/emote.jsoninstead of a root-levelemote-datapack.json. - A single datapack can now contain multiple emotes.
- Example emote datapacks have been updated to the new format.
- Emote metadata is now stored in
-
Redesigned emote permission configuration.
packs.jsonnow controls disabled emotes and permission-based emote access.*can be used to grant access to every enabled emote.- The old
emote_permissionsetting has been removed.
New Commands
/emote list— Lists all registered emotes./emote stop-all— Stops every active or pending emote./emote enable <namespace>— Enables an emote and reloads the emote list./emote disable <namespace>— Disables an emote and stops all active instances of it.
Playback Improvements
- Improved restoration of player state when an emote ends or is interrupted.
- Added equipment visibility handling during emote playback.
- Added support for stopping all emotes or all instances of a specific namespace.
- Added ordered skin-part markers for emotes made from multiple model pieces.
- Improved player skin-part detection and texture application.
Configuration and Stability
- Added
schema_versiontoconfig.json. - Invalid configuration files now leave the currently loaded configuration unchanged.
- Improved validation for invalid metadata, missing functions, duplicate namespaces, and duplicate command names.
- Enabling or disabling an emote through commands now automatically updates
packs.json. - Standardized indentation and line endings across the project.
Important
Emote datapacks and packs.json use a new format in version 0.6.0. Datapacks and configuration files created for older versions must be converted or updated using the new web converter and documentation.
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:qUF0jygw:ITdZrWfZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qUF0jygw:ITdZrWfZ"
}

