Links
Tags
Creators
Details
0.9.0-beta.1-neoforge
Compatibility
Required content
Changes
Emotify 0.9.0-beta.1
This release adds NeoForge support for Minecraft 26.3, including the new rendering pipeline, full improved transparency support, and the updated server configuration type.
Highlights
- Added a dedicated NeoForge build for Minecraft 26.3 with client, singleplayer, and dedicated server support.
- Reworked emotion rendering for the 26.3 ordered submit pipeline. Emotions are now drawn after translucent terrain, so water, portals, and other translucent blocks no longer show through them.
- Added support for Minecraft's improved transparency mode with dedicated Emotify shaders and order-independent translucency pipelines. Emotions now render correctly in both transparency modes.
- Adapted the emotion picker to the new 26.3 mouse and keyboard numbering: left click and the
1–9keys select a quick slot, right click clears it, and the picker scrollbar and settings focus handling work as before. - Moved the server configuration to NeoForge's synced configuration type. The file is now
config/emotify-server.tomland can be overridden per world through<world>/syncedconfig/emotify-server.toml. - Built against NeoForge 26.3.0.88 and Kotlin for Forge 6.4.0.
- Kept the Emotify protocol, the client configuration in
config/emotify-client.toml, the emoji catalog, and animation timing unchanged, so 0.9.0-beta.1 stays compatible with existing client settings and other Emotify clients and servers.
Requirements
- Minecraft 26.3
- NeoForge 26.3.0.88 or newer
- Kotlin for Forge 6.4.0 or a newer compatible 6.x release
- Java 25
Players who want to send and see emotions must install the Emotify client matching their loader and Minecraft version. Other players can join normally.
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:2ZS962dj:LZQFMp20"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2ZS962dj:LZQFMp20"
}

