Mod API

Other Fabric mods can use EmoteApi.getInstance() to register and play emotes and listen for Emote events.

Gradle dependency

Emote is available from Modrinth Maven. Add the Modrinth Maven repository:

build.gradle

repositories {
    exclusiveContent {
        forRepository {
            maven {
                name = "Modrinth"
                url = "https://api.modrinth.com/maven"
            }
        }
        filter {
            includeGroup "maven.modrinth"
        }
    }
}

Replace [VERSION_ID] with the Modrinth version ID of the Emote file you want to use. Use the ID assigned to the version by Modrinth, not its display name.

build.gradle

dependencies {
    implementation "maven.modrinth:qUF0jygw:[VERSION_ID]"
}

Use the Emote version list to find a file for your target Minecraft version and its version ID.

Declare the Emote dependency in fabric.mod.json as well:

fabric.mod.json

{
  "depends": {
    "emote": "*"
  }
}

---

API scope

The API currently provides:

• Runtime emote registration and removal
• Starting and stopping player emotes
• Current playback-state queries
• Cancellable playback-request listeners
• Playback start and stop lifecycle listeners
• Named animation callback listeners

API calls that change state must run on the Minecraft server thread.

EmoteApi.play is a trusted server-side playback entry point. The calling mod is responsible for applying any desired standalone, disabled-ID, player-permission, and cooldown policy. Emote still requires a loaded ID, dispatches cancellable playback-request events, and enforces playback-engine limits and failures.