Embers Text API

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.4 (2026-09-16) - Markup renders in text that mods draw as a plain string, such as Better Advancements titles, which come from `getString()` and never reached the component parser. `Font.drawInBatch(String)`, `Font.prepareText(String)` and `Font.width(String)` route strings with real markup through the component path. Plain text with a stray `<` or `>` is untouched. `Font.split(String)` and `wordWrapHeight(String)` still measure the raw string, so a wrapped plain-string label may wrap early. - `<neon>` halos now follow every drawn quad of a glyph: they rotate with `<pendulum>` and `<swing>`, clip to each `<glitch>` slice, use the fill colour and grow by the border width with `<outline>`, and match the random glyph drawn by `<obfuscate>`. - SDF fonts render with a cleaner edge. The text shader now measures the pixel footprint of each glyph from the atlas mapping itself, so rotated text (`<pendulum>`, `<swing>`) gets the same one pixel edge as straight text, the old edge sharpening that thinned every stroke is gone, and small text gets a light stem darkening that fades out above roughly GUI scale 4. `<bold>` on an SDF font that has no `_bold` variant now emboldens instead of drawing nothing extra, and a custom `px_range` in a font manifest is honoured by the shader rather than assumed to be 8. Glyph bearings now use the real margin of each baked glyph instead of a fixed pad, so wide and narrow letters no longer sit up to half a unit apart from where the font places them. The on-disk SDF cache format bumped to version 2 and rebuilds itself on first launch. - Unknown or out-of-range effect params log one warning per effect and param per session, with a pointer to the docs. - The KubeJS binding now ships on Forge 1.20.1, Fabric 1.20.1 and NeoForge 26.1 as well as NeoForge 1.21.1. The `EmbersText` global and the `EmbersTextEvents.itemTooltip` client event are the same on all four. The remaining targets have no KubeJS release to bind to. - `EmbersText.effects()` returns a sorted list of every registered effect name, so a script can see what the installed version accepts. - `EmbersText.clearItemNames()` drops every rule registered with `itemName`, so a startup script can reload from a clean rule set.

# Changelog ## v3.0.3 (2026-08-10) - A `<scroll>` span is now a single unbreakable unit of layout. Multi-line scroll content garbled into overlapping tiles because the effect measured its width from the per-frame `x` progression, which restarts on every wrapped line, so it sized the whole marquee from the first line alone. A scroll span no longer wraps and reserves only its viewport width. Text written after `</scroll>` therefore starts one viewport past the marquee rather than past the entire hidden string. - New `[clamp]` attribute and `clampToScreen(boolean)` builder method. Screen clamping stays on by default; turn it off for a message that is meant to sit partly off screen. Clamping also no longer inverts on a message larger than the window, which used to snap it to the wrong corner. - The anvil rename limit now counts visible characters. Vanilla's 50 still applies, but markup tags no longer count toward it, so `<rainbow>Excalibur</rainbow>` is 9 characters rather than 28. A 256-character raw ceiling keeps a name from being padded with unlimited markup. On 1.20.1 and 1.21.1 the text field rejects an over-long name as you type; on 26.1 and 26.2 the server declines the rename, because those versions removed the text-field filter hook. - **Removed** the `anvil.nameMaxLength` server config option. It is replaced by the rule above and needs no setting. On 1.20.1 it never worked at all, because the mixin targeted `setItemName` while the length constant lives in `validateName`. - The continuous message effects `breathe`, `drift`, `float`, `grow`, `rock`, `spin` and `vibrate` take three new timing params, so they can run in bursts instead of looping forever: `every` (seconds between bursts, 0 for continuous), `hold` (seconds a burst lasts) and `delay` (seconds before the first burst). Each burst restarts the effect's own clock at zero, so a sine-driven effect enters and leaves at rest rather than snapping mid-swing. Existing messages are unaffected; `every` defaults to 0. - `<item>` and `<entity>` now take hover and click from an enclosing `<hover>` or `<click>` tag. The parser rebuilt icon spans from scratch and dropped everything but the icon's own attributes, so wrapping an icon in `<click>` did nothing. - New `tooltip` attribute on `<item>` and `<entity>`. `tooltip=true` shows the game's own tooltip for that item or entity, built from the tag's `count` and `nbt`; any other value is used as literal tooltip text. - `<hover>` accepts `action=show_item` and `action=show_entity`, so ordinary text can carry an item or entity tooltip too. - The hover region of an inline icon now matches the sprite. It was the icon's layout advance, which is deliberately 4px narrower than the 16px sprite so icons tuck into surrounding text, leaving the right edge dead. Chat is now hit-tested from the drawn sprite rather than the advance. - Hover tooltips now work in mod GUIs, not just chat. Vanilla only hit-tests text in the handful of screens that implement it, so interactive markup in FTB Quests or any other custom UI had nothing to hook. Each interactive glyph's on-screen rect is now recorded as it is drawn and tested against the cursor in any screen, clipped to the active scissor so scrolled-out text is not hoverable. 1.20.1 and 1.21.1 only; 26.1 and 26.2 use a different text pipeline and are not covered yet. - Fixed inline icons vanishing once they carried a hover or click event. Deriving a style through `withHoverEvent`/`withClickEvent` dropped the icon's registry id, so the tooltip appeared over empty space. This also restores icons combined with `<type>` and `<obfuscate>`, which lost them the same way. - Fixed the hover and click region of an inline icon. Icons draw 16px wide but rode on a single space, so only about 4px responded to the cursor, and line wrapping measured them the same way.

# Changelog ## v3.0.3 (2026-08-10) - A `<scroll>` span is now a single unbreakable unit of layout. Multi-line scroll content garbled into overlapping tiles because the effect measured its width from the per-frame `x` progression, which restarts on every wrapped line, so it sized the whole marquee from the first line alone. A scroll span no longer wraps and reserves only its viewport width. Text written after `</scroll>` therefore starts one viewport past the marquee rather than past the entire hidden string. - New `[clamp]` attribute and `clampToScreen(boolean)` builder method. Screen clamping stays on by default; turn it off for a message that is meant to sit partly off screen. Clamping also no longer inverts on a message larger than the window, which used to snap it to the wrong corner. - The anvil rename limit now counts visible characters. Vanilla's 50 still applies, but markup tags no longer count toward it, so `<rainbow>Excalibur</rainbow>` is 9 characters rather than 28. A 256-character raw ceiling keeps a name from being padded with unlimited markup. On 1.20.1 and 1.21.1 the text field rejects an over-long name as you type; on 26.1 and 26.2 the server declines the rename, because those versions removed the text-field filter hook. - **Removed** the `anvil.nameMaxLength` server config option. It is replaced by the rule above and needs no setting. On 1.20.1 it never worked at all, because the mixin targeted `setItemName` while the length constant lives in `validateName`. - The continuous message effects `breathe`, `drift`, `float`, `grow`, `rock`, `spin` and `vibrate` take three new timing params, so they can run in bursts instead of looping forever: `every` (seconds between bursts, 0 for continuous), `hold` (seconds a burst lasts) and `delay` (seconds before the first burst). Each burst restarts the effect's own clock at zero, so a sine-driven effect enters and leaves at rest rather than snapping mid-swing. Existing messages are unaffected; `every` defaults to 0. - `<item>` and `<entity>` now take hover and click from an enclosing `<hover>` or `<click>` tag. The parser rebuilt icon spans from scratch and dropped everything but the icon's own attributes, so wrapping an icon in `<click>` did nothing. - New `tooltip` attribute on `<item>` and `<entity>`. `tooltip=true` shows the game's own tooltip for that item or entity, built from the tag's `count` and `nbt`; any other value is used as literal tooltip text. - `<hover>` accepts `action=show_item` and `action=show_entity`, so ordinary text can carry an item or entity tooltip too. - The hover region of an inline icon now matches the sprite. It was the icon's layout advance, which is deliberately 4px narrower than the 16px sprite so icons tuck into surrounding text, leaving the right edge dead. Chat is now hit-tested from the drawn sprite rather than the advance. - Hover tooltips now work in mod GUIs, not just chat. Vanilla only hit-tests text in the handful of screens that implement it, so interactive markup in FTB Quests or any other custom UI had nothing to hook. Each interactive glyph's on-screen rect is now recorded as it is drawn and tested against the cursor in any screen, clipped to the active scissor so scrolled-out text is not hoverable. 1.20.1 and 1.21.1 only; 26.1 and 26.2 use a different text pipeline and are not covered yet. - Fixed inline icons vanishing once they carried a hover or click event. Deriving a style through `withHoverEvent`/`withClickEvent` dropped the icon's registry id, so the tooltip appeared over empty space. This also restores icons combined with `<type>` and `<obfuscate>`, which lost them the same way. - Fixed the hover and click region of an inline icon. Icons draw 16px wide but rode on a single space, so only about 4px responded to the cursor, and line wrapping measured them the same way.