Tags
Creators
Details
All versions
3.0.0+neoforge-26.2
Release
Ember's Text API 3.0.0 (NeoForge 26.2)5 months ago 72
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Changes
Changelog
v3.0.0 — 2026-06-21
- NeoForge and Fabric support for MC 26.1.x and 26.2, including the neon glow and SDF text pipeline ported to 26.2's new bind-group render API. The FTB Quests and Emojiful integrations are not present on 26.2.
- FTB Quests composer: an ETA button on the quest text editor opens a composer with effect and preset pickers, a font picker, per-parameter controls, and a live preview that writes the composed markup back into the editor. Available on 1.20.1, 1.21.1, and 26.1.
- Effect parameters reworked for consistent naming with multiple accepted aliases per parameter. Gradient and rainbow gained an angle; rainbow gained length, saturation, and brightness; neon gained flicker controls.
<shadow>is now independent of the host text's drop shadow, so it renders even where the host draws without one (such as FTB Quests titles), and an explicit shadow color is no longer dimmed.- Twemoji coexistence: Twemoji's emoji render alongside ETA markup.
- Lang tag
argsnow supports escaping commas with a backslash so a single argument can contain commas:<lang key='commands.give.success.single' args='$9\,000'>passes$9,000as one argument. A literal backslash is written\\. - Emojiful compat: text effects now apply to chat messages on Forge 1.20.1. The render hook targeted the dev-mapped method name, which silently no-ops against the SRG-named build that ships in production. The integration also reads Emojiful's renderer state through accessor mixins instead of reflection.
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:OVSg4uGN:AB7rY4t7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OVSg4uGN:AB7rY4t7"
}

