Getting Started

Setup Tool#

1. Check your email for a setup email from Light Side with your access token
2. Download the setup tool from the email and import it into your Unity project. The setup window opens automatically — paste your token and click Set Up
3. Done! UniText is installed. You can manage versions anytime via Light Side → UniText Setup in the Unity menu bar

1.1 Canvas text (UniText)#

Use the GameObject menu to create ready-to-use Canvas UniText objects:

• GameObject›UI (Canvas)›UniText›Text — text with default font and size
• GameObject›UI (Canvas)›UniText›Button — button with UniText label (Image + Button + UniText child)

Canvas and EventSystem are created automatically if not present. Default font stack from Project Settings → UniText is applied to all created components.

You can also override default prefabs in Project Settings → UniText (Text Prefab, Button Prefab) — the menu will instantiate your prefab instead.

1.2 World-space text (UniTextWorld)#

Use the menu to create a ready-to-go world-space text object:

• GameObject›UI (World)›UniText›World Text

The menu creates a UniTextWorld scaled to 0.01 (so world units line up with your typical 3D scene), and auto-adds a UniTextWorldRaycaster to Camera.main so pointer events work out of the box (see §4.4). Override the prefab in Project Settings›UniText›World Text Prefab.

World-space text authoring is identical to Canvas text — same FontStack, FontSize, alignment, modifiers, styles, language, and so on. The component also exposes Unity's standard sorting knobs:

1.3 How world-space rendering works#

You never attach a MeshRenderer to a UniTextWorld. An invisible UniTextWorldBatcher in the scene subscribes to UniTextWorld events and assembles combined meshes:

• All active UniTextWorld components sharing the same (material, SortingLayer, OrderInLayer, SortingGroup) are batched into one draw call.
• Large groups are split into multiple shards automatically (target shard size configured via UniTextSettings.WorldBatcherShardTargetVertexCount, default 8192 vertices).
• Each batched group respects Unity's sorting model, so world-space text interleaves correctly with SpriteRenderer and other renderers per-instance.
• When a component moves, only its slice of the shard's vertex buffer is rewritten (no full rebuild for transform-only changes).

The batcher is fully transparent — you don't configure it. If you need to observe the render pipeline from outside (custom batchers, debug overlays), UniTextWorld exposes public events: static Activated / Deactivated, per-instance RenderDataAvailable / RenderDataCleared / SortingChanged / ParentChanged, and a UniTextWorld.Active list of currently enabled instances.

2.1 Creating a UniTextFont Asset#

Context Menu (from fonts already in the project):

1. Import your font files (.ttf, .otf, or .ttc) into Unity
2. Select one or multiple fonts in the Project window
3. Right-click → Create›UniText›Font Asset
4. A .asset file is created next to each source font

Supports batch creation — select 10 fonts, get 10 assets in one click.

UniText Tools Window (also useful for creating from fonts outside the project):

If the font file is somewhere on your computer but not imported into the Unity project:

1. Open Tools›UniText›Tools
2. Drag-and-drop font files from the Project window, or click Browse Files to pick fonts from anywhere on your computer
3. Click Create N UniText Font Asset(s)
4. For external fonts, you will be prompted for an output folder within Assets

This is also useful for quick drag-and-drop workflow without manually importing fonts first.

2.2 Font Inspector Settings#

Select a UniTextFont asset to configure in the Inspector:

After changing SDF Detail or Glyph Overrides, click Apply to rebuild the atlas. Revert discards pending changes.

A Glyph Picker is built into the inspector: type text to preview glyph rendering, select individual glyphs from the grid, and add tile size overrides directly.

The Inspector also shows:

• Face Info — family name, style, weight class, italic flag (read-only, extracted from font data)
• Variable Font Axes — if the font is variable, shows available axes with min/default/max values
• Font Data Status — whether font bytes are embedded
• Runtime Data — glyph count, character count
• Atlas Preview — SDF, MSDF, and Emoji atlas texture slices

2.3 Creating a UniTextFontStack (Font Collection)#

UniTextFontStack organizes fonts into Font Families. Each family has:

• a primary font and optional faces (bold, italic, light, etc.) — the same family, different weights/styles;
• an optional name — a user-facing identifier addressable from markup (see §5 and FontModifier);
• an optional preferredLanguage — a BCP 47 tag that biases codepoint resolution toward this family when the active language matches (see §5).

Families are searched in order for glyph fallback.

There are two creation modes when you select multiple UniTextFont assets:

Font Stack (Combined) — Grouped by Family#

1. Select 2+ UniTextFont assets in the Project window
2. Right-click → Create›UniText›Font Stack (Combined)
3. Fonts are automatically grouped by familyName. The closest-to-Regular font becomes the primary; others become faces.

When rendering "Hello مرحبا עולם":

• "Hello" — Inter family has Latin glyphs, used directly
• "مرحبا" — Inter has no Arabic glyphs, falls back to NotoSansArabic family
• "עולם" — Falls back to NotoSansHebrew family

When <b> is applied, the system uses CSS §5.2 weight matching to find the best face within the same family (e.g., Inter-Bold). If no matching face exists, synthesis (fake bold/italic) is applied.

Use case: Multilingual text with real bold/italic variants. One component handles any language.

Font Stack (Per Font) — Individual Stacks#

1. Select 1+ UniTextFont assets in the Project window
2. Right-click → Create›UniText›Font Stack (Per Font)
3. Creates one separate UniTextFontStack for each selected font

Use case: When different components use different fonts. Swap font stacks per component.

Variable Fonts#

Variable fonts are strongly recommended over static font files. A single variable font file replaces dozens of static weights/widths:

Variable font axes are controlled via modifiers. <b> and <i> automatically set the appropriate axes when the font supports them. For direct control, use the VariationModifier with <var> tags.

Three-Tier Face Resolution#

When a modifier requests bold or italic, the system resolves in order:

1. Variable font axes — if the font has wght/ital/slnt axes, set them directly
2. Static font faces — find the closest matching face by weight/italic in the family
3. Synthesis — apply fake bold (SDF dilate) or fake italic (shear transform)

Fallback Stack Chaining#

UniTextFontStack has a fallbackStack field that references anotherUniTextFontStack. The system searches primary fonts in each family first, then walks the fallbackStack chain. Circular references are handled automatically.

All stacks get full language support through one shared reference.

2.4 UniText Tools Window#

Open via Tools›UniText›Tools. Three tabs:

Tab 1: Create Font Asset#

Batch creation of UniTextFont assets from source files.

Adding fonts:

• Drag & drop — drop .ttf/.otf/.ttc files into the drop area
• Browse Files — opens file dialog with multi-select
• Project selection — selecting font files in the Project window auto-adds them

Each entry shows the font name and file size. Click Create N UniText Font Asset(s) to generate all assets.

Additional features:

• Copy All Characters — extracts every codepoint the font supports and copies to clipboard. Useful for checking font coverage or as input for the Font Subsetter

Output: Project fonts (within Assets) are saved next to the source file. External fonts (outside Assets) prompt for output folder.

Tab 2: Font Subsetter#

Create optimized subset fonts by keeping or removing specific character ranges. Reduces font file size for builds where you don't need full Unicode coverage.

Keep Mode — only selected characters remain in the font:

• Select script ranges (Latin, Cyrillic, Arabic, etc.) and/or type custom text
• The output font contains only those characters (plus GSUB-related composed forms)
• Example: Keep only "Basic Latin + Cyrillic" for a game targeting English/Russian

Remove Mode — selected characters are removed from the font:

• Select script ranges and/or type custom text to remove
• Intelligent composition detection: combined characters (emoji sequences, ligatures) are removed as glyphs while preserving their component codepoints
• Two-pass process: (1) Codepoint removal with GSUB closure (handles contextual forms), (2) Composition glyph removal without closure (preserves components)

Available script ranges (30 sets in 10 groups):

Output: Saves a new .ttf file with the suffix _subset. Reports original size, subset size, and reduction percentage.

Practical scenarios:

Tab 3: Dictionary Builder#

Builds word segmentation dictionary assets for SE Asian scripts (Thai, Lao, Khmer, Myanmar) that don't use spaces between words.

1. Drag-and-drop a word list text file (one word per line)
2. Select the target script
3. Click Build to compile a WordSegmentationDictionary asset

The compiled dictionary is configured via Project Settings›UniText›Word Segmentation›Dictionaries. UniText ships with a Thai dictionary (26K words from ICU).

2.5 Materials#

Materials for the base text pass (SDF Face, SDF Base, MSDF Face, MSDF Base) and the emoji pass are managed automatically by UniTextMaterialCache — there is no manual material assignment on UniText.

Outline and shadow effects render as extra quads appended to the same mesh as the face (not as separate CanvasRenderer objects). Any number of outline / shadow modifiers can be layered on the same text without extra sub-meshes.

If you want to apply a custom material / shader to a text range, see §6.

3.1 Architecture: Rule + Modifier#

The system separates what to parse from what to do:

• Parse Rule (IParseRule) — finds patterns in text and produces ranges with optional parameters
• Modifier (BaseModifier) — applies a visual or structural effect to those ranges

There is no hard coupling between tags and modifiers. Any parse rule can drive any modifier. The tag name, the syntax, and even the parsing strategy are all independent from the effect being applied. A <highlight> tag can trigger a ColorModifier. A **markdown** wrapper can trigger an OutlineModifier. You decide.

Example: The same BoldModifier works with completely different syntaxes:

And the same TagRule (tagName="b") can be paired with any modifier — BoldModifier, ColorModifier, or your own custom modifier.

3.2 Built-in Modifiers#

The table below shows default pairings (how presets configure them). These are conventions, not constraints — you can reassign any tag to any modifier.

3.3 Custom Tags with Default Parameters#

TagRule has a defaultParameter field that lets you create custom tags with pre-configured values. This way your text stays clean — no need to repeat parameter values in every tag.

Example: Create a <warning> tag that always applies red color:

Now in text:

• <warning>error occurred</warning> — uses default red (#FF0000)
• <warning=#FFA500>caution</warning> — overrides with orange

Multi-parameter defaults: For modifiers with multiple parameters (like OutlineModifier: dilate, color), defaults fill in missing values:

• <glow>text</glow> — dilate 0.3, green outline
• <glow=0.5>text</glow> — dilate 0.5, green outline (color from default)

This works because TagRule merges text parameters with defaults: values from the tag take priority, remaining parameters come from defaultParameter.

MarkdownWrapRule also supports defaultParameter the same way.

3.4 Parse Rule Types#

Tag-Based Rules#

All tag-based rules use the universal TagRule class with a configurable tag name. Parameters are always optional. Self-closing is syntax-driven (<tag/> or <tag=value/>).

Markdown-Style Rules#

Utility Rules#

Protection Rules (standalone)#

Protection rules shield their content from being consumed by any other parse rule. They are standalone — they implement IParseRule.IsStandalone = true and register without a paired modifier (the rule acts on its own). The text is passed through unaltered except that the delimiters themselves are stripped.

Register standalone rules with AddRule:

AddRule enforces IParseRule.IsStandalone == true — passing a non-standalone rule logs an error and does nothing (use AddStyle with a modifier for those). Your own rules can opt into standalone behavior by overriding IsStandalone => true.

3.5 Parameter Formats Reference#

The tag names below (<color>, <font>, <mat>, …) are the conventional names used by the built-in presets — they are not hard-coded into the modifiers. Any modifier can be registered under any name via Style.Tag(new XxxModifier(), "yourName"), or driven by MarkdownWrapRule / RangeRule / StringParseRule / a custom rule with no tag at all (see §3.1). The parameter syntax shown for each modifier is what the modifier itself parses, regardless of how the range was matched.

Color (ColorModifier)#

• Hex: #RGB, #RRGGBB, #RRGGBBAA
• Named (20 colors): white, black, red, green, blue, yellow, cyan, magenta, orange, purple, gray, lime, brown, pink, navy, teal, olive, maroon, silver, gold

Size (SizeModifier)#

• Absolute: <size=24> — 24 pixels
• Percentage: <size=150%> — 150% of base size
• Relative: <size=+10> / <size=-5> — offset from base

Gradient (GradientModifier)#

• Format: <gradient=name[,shape][,angle]>
• Shapes: linear (default), radial, angular
• Angle: 0–360 degrees (0=right, 90=up). Used by linear and angular

Examples:

• <gradient=rainbow> — linear, horizontal
• <gradient=rainbow,radial> — radial from center
• <gradient=rainbow,angular,90> — conic sweep, rotated 90°
• <gradient=rainbow,linear,45> — linear, rotated 45°

Gradients are defined in the UniTextGradients asset (Project Settings → UniText → Gradients).

Letter Spacing (LetterSpacingModifier)#

• Format: spacing[,monospace]
• Pixels: <cspace=5> — 5px extra spacing
• Em units: <cspace=0.1em> — 0.1 em extra spacing
• Monospace: <cspace=0.5em,true> — equal advance width for all glyphs
• For cursive scripts (Arabic, Syriac, etc.), positive spacing renders visual tatweel (kashida) to preserve connections

Outline (OutlineModifier)#

• <outline> — default (dilate=0.2, black)
• <outline=0.3> — custom dilate
• <outline=#FF0000> — custom color
• <outline=0.3,#FF0000> — both

Shadow (ShadowModifier)#

• <shadow> — default (black 50% alpha)
• <shadow=#00000080> — custom color
• <shadow=0.1,#000,2,2,0.5> — dilate, color, offsetX, offsetY, softness

Variable Font Axes (VariationModifier)#

• Positional axis values in order: wght, wdth, ital, slnt, opsz
• Use ~ to skip an axis
• Absolute: <var=700> — weight 700
• Percentage: <var=150%> — 150% of default weight
• Delta: <var=+200> — +200 from default weight
• Multiple axes: <var=700,80> — weight 700, width 80
• Skip axes: <var=~,~,~,-12> — only set slant to -12

Ellipsis (EllipsisModifier)#

• <ellipsis=1> — truncate end (default): Hello Wo...
• <ellipsis=0> — truncate start: ...o World
• <ellipsis=0.5> — truncate middle: Hel...rld
• Any float 0–1 for fine-grained control

Font (FontModifier)#

• Parameter is a FontFamily.name from the component's font stack
• <font=pixel>Score</font> — render "Score" in the family named pixel

Language (LanguageModifier)#

• Parameter is a BCP 47 tag
• <lang=zh-Hans>汉字</lang>, <lang=ja>...</lang>, <lang=ko>...</lang>, <lang=en-US>...</lang>

Material (MaterialModifier)#

• Parameter is an optional tint color (same syntax as Color)
• <mat>text</mat> — use the material's tint as-is
• <mat=#FF8800>text</mat> — multiply the vertex color by orange

3.6 Adding Styles to a Component#

In the Inspector#

1. Expand Styles list on the UniText component
2. Click + — a searchable selector opens with predefined presets (Bold, Italic, Color, Font, Language, Material, Markdown variants, Protection rules, and more)
3. Select a preset — both the Rule and Modifier are configured automatically

Each entry is a Rule+Modifier pair. Tags from the Rule are parsed in text, and the Modifier applies the effect to matched ranges. You can also configure Rule and Modifier manually for custom combinations.

Via Code — Fluent Builders#

Style exposes three static builders that cover the common cases:

For custom combinations (StringParseRule, CompositeParseRule, custom rules) use the explicit form:

Remove at runtime:

Querying and Mutating Styles at Runtime#

SetWholeText / ClearWholeText / ToggleWholeText operate on the component's local Styles list only — they never mutate Style Presets (those are shared assets).

3.7 Style Preset — Shared Configuration#

Problem: You have 50 UniText components that all need the same set of modifiers (bold, italic, color, links). Setting up each one manually is tedious and error-prone.

Solution: Style Preset is a ScriptableObject that stores a reusable list of Rule+Modifier pairs.

Setup#

1. Assets›Create›UniText›Style Preset
2. Add your modifier pairs:

3. On each UniText component, add this config to the Style Presets list

Benefits#

• Single source of truth — change the config, all components update
• No duplication — define modifiers once, reference everywhere
• Combinable — a component can have multiple configs plus its own local Styles. They all work together
• Version control friendly — one asset to track rather than per-component settings

Local vs Config#

A component's effective set of modifiers = its local Styles + all Style Presets.

Runtime API#

Useful for toggling a markup configuration at runtime (e.g., apply a "chat formatting" preset while the chat panel is open, remove it when it closes) without building individual styles.

3.8 RangeRule — Applying Modifiers Without Markup#

RangeRule lets you apply a modifier to specific text ranges programmatically, without any tags in the text itself.

Apply to All Text#

To apply a modifier to the entire text (e.g., make everything a specific color), use the range "..":

Range Syntax#

RangeRule uses C#-style range notation:

RangeEx.WholeText is the canonical ".." constant, and RangeEx.IsWholeText(expr) accepts any equivalent form ("..", "..^0", "0..").

Multiple Ranges#

Practical Scenarios#

3.9 StringParseRule — Literal Pattern Matching#

StringParseRule matches literal string patterns in text (no XML/HTML syntax):

3.10 CompositeParseRule — Combining Rules#

CompositeParseRule groups multiple rules into one. It tries child rules in order and returns the first match:

3.11 Priority System#

Parse rules have a Priority property that controls matching order (higher = matched first):

This prevents conflicts: <link=url>https://example.com</link> won't be double-matched by both TagRule and RawUrlParseRule.

3.12 Creating Custom Parse Rules#

Implement IParseRule to create your own markup syntax:

Simplest Approach — Use TagRule#

If your syntax follows the <tag>content</tag> pattern, use the built-in TagRule with a custom tag name — no subclassing needed:

Parameters are always optional. Self-closing is purely syntax-driven (<tag/> or <tag=value/>).

3.13 Creating Custom Modifiers#

UniText has several modifier base classes for different use cases:

Pattern 1: Text Transformation (BaseModifier)#

For modifiers that transform codepoints before rendering (like uppercase):

Pattern 2: Per-Glyph Visual Effect (GlyphModifier<T>)#

For modifiers that change glyph appearance during mesh generation (color, underline, etc.):

Pattern 3: Effect Quads (EffectModifier)#

For effects like outline, shadow, glow — duplicate geometry rendered behind/ahead of the face, painted per effect:

EnqueueEffectQuad records a request for an extra quad that renders behind the face in registration order. All outline-modifier quads render before all shadow-modifier quads, which render before the face — painter order is grouped per modifier, not per glyph.

Pattern 4: Sub-mesh With Its Own Material (SubMeshModifier)#

For effects that need a separate Material / shader (like MaterialModifier). Inherit SubMeshModifier and override ShouldIncludeCurrentGlyph, GetMaterialForSlot, GetRenderOrder, GetSortIndex — see MaterialModifier.cs for a full reference.

Pattern 5: Interactive Region (InteractiveModifier)#

For clickable/hoverable text regions:

Modifier Lifecycle#

Best Practices for Custom Modifiers#

• No new T[] at runtime — use UniTextArrayPool<T>.Rent/Return or buffers.GetOrCreateAttributeData<T>()
• Subscribe in OnEnable, unsubscribe in OnDisable — prevents stale callbacks
• Use PrepareForParallel() for anything that calls a Unity API (Material.GetFloat(), transform reads, etc.)
• Address the face quad via gen.faceBaseIdx, not gen.vertexCount - 4
• Skip color (emoji) glyphs in effects — if (gen.font.IsColor) return;

4.1 Click and Hover Events#

4.2 Hit Testing#

For custom interaction logic:

4.3 Text Highlighter#

The Highlighter property controls visual feedback — clicks, hover, and programmatic selection. It lives on UniTextBase, so it works identically on Canvas and world-space text.

The built-in DefaultTextHighlighter provides click flash (with fade-out), hover tint, and selection highlight:

Custom Highlighters#

Extend TextHighlighter (or DefaultTextHighlighter to keep its click/hover/selection logic). The two CreateHighlightRenderer overloads — one taking UniText, one taking UniTextWorld — are the type-safe extension points: override either or both to plug a custom visual on the chosen backend. Inside event handlers, call CreateHighlightRenderer(name, order) (no owner argument) — it dispatches to the correct typed overload based on the actual owner.

To customize only the visual on one backend while keeping the default click flash / hover / selection logic, subclass DefaultTextHighlighter and override only the relevant CreateHighlightRenderer overload(s).

HighlightOrder.Behind renders below the text (selection, hover glow), HighlightOrder.Above renders above it (click flash, cursor).

4.4 World-Space Pointer Routing (UniTextWorldRaycaster)#

Canvas text receives EventSystem pointer events automatically through the Canvas's GraphicRaycaster. For world-space text, add a UniTextWorldRaycaster component to the camera that should pick up pointer events:

The raycaster is not added automatically — pick the camera explicitly. If a UniTextWorld with RaycastTarget = true enters a play-mode scene without any UniTextWorldRaycaster, a one-time warning is logged with the same instruction.

Properties:

• BlockingObjects (None / TwoD / ThreeD / All) — physical geometry that should occlude clicks between the camera and the text. Leave as None if the scene already has a PhysicsRaycaster / Physics2DRaycaster on the same camera (Unity's EventSystem distance-sorts across raycasters automatically).
• BlockingMask — layer mask used when BlockingObjects is non-None.

Per-instance opt-out: UniTextWorld.RaycastTarget (default true). Set to false on purely decorative text — the raycaster skips it entirely, the same way Canvas Graphic.raycastTarget = false works for UniText.

Once the raycaster is on the camera, UniTextWorld receives the same events as UniText: TextClicked, RangeClicked, RangeEntered, RangeExited, HoverChanged, plus link / hashtag / custom interactive range events.

4.5 Text Resolver (IUniTextResolver)#

The resolver hook substitutes a component's source text before parsing / shaping / layout, without writing to the serialized text field. Scenes and prefabs stay clean — ideal for editor-time localization preview, template expansion, or runtime key-to-string binding.

TryResolve may run on a worker thread — don't call Unity APIs directly inside it; populate caches in PrepareForParallel and read them from TryResolve. To know whether a resolver is currently active, inspect uniText.TextOverride & TextOverrideSource.Resolver.

5.1 Three places to set the language#

UniText.Language is a runtime shortcut: the setter finds or creates a whole-text LanguageModifier style in the component's local Styles list. There's no serialized inspector field — components that never set a language see nothing extra.

5.2 Per-range language in markup#

Itemization splits runs on language boundaries, so each run shapes with its own OpenType language tag.

5.3 Picking the right font family by language#

Attach preferredLanguage to each region-specific family in one stack:

With UniText.Language = "zh-Hans", codepoints are resolved against the SC family first; unmatched codepoints fall through the normal chain as usual. A matching family wins over the default fallback order for that codepoint.

5.4 Naming families (FontFamily.name + FontModifier)#

You can give each family a user-facing name and address it from markup or code:

A matched name wins over both preferredLanguage selection and the default fallback chain. If the chosen family doesn't have a glyph for a particular codepoint, the normal fallback chain still kicks in for that codepoint. Unknown names log a one-time warning.

6.1 Quick start — use a ready material#

UniText ships example materials in UniText/Defaults/Materials/:

Set up a MaterialModifier in the inspector — paired with a TagRule whose tagName you choose (mat is the convention used here) — and point its Material field at one of these. From code:

For UniTextWorld, you can also assign these materials as the component's base material instead of using MaterialModifier (useful for whole-text effects, no tag setup required).

6.2 Authoring your own shader#

Use the asset creation menu:

Assets›Create›UniText›Custom Material Shader

This scaffolds a new .shader file pre-wired for MaterialModifier — includes UniText_Custom.cginc, binds _MainTex as the glyph atlas Texture2DArray, exposes the standard UV layout UniText writes. Rename it, tweak the fragment function, you're done.

Three example shaders ship as starting points (in UniText/Shaders/Templates/Examples/):

• UniText/Custom/Dissolve
• UniText/Custom/Hologram
• UniText/Custom/Rainbow

6.3 Compose modes#

MaterialModifier.renderOrder controls how the custom material composes with the base text pass on the range:

6.4 Per-text and per-glyph shader data#

• Per-text constants — ConstantUv2 / ConstantUv3 (Vector4 each) are written into TEXCOORD2 / TEXCOORD3 of every glyph vertex in this modifier's sub-mesh. Animate them at runtime without touching Material.Set* (which would affect every component sharing the cached material clone):
  csharp
• Per-glyph writer — set glyphDataWriter (a MaterialGlyphWriter delegate) to compute uv2 / uv3 per glyph at sub-mesh build time. Useful for staggered effects (wave, cascade, per-character dissolve).
• Emoji material slot — emojiMaterial accepts a separate material for emoji glyphs in the range. Leave null and emoji render through the base emoji pass (the modifier does nothing for them).

6.5 Noise texture generator#

Many custom shaders need noise textures. Tools›UniText›Noise Generator produces seamless grayscale value-noise / FBM PNG assets (64–1024 px, configurable seed / frequency / octaves / lacunarity / gain / invert / tileable). The shipped Dissolve and Hologram examples use this.

6.6 Lit shaders for world-space text#

Two SDF/emoji shader variants with lighting are provided for 3D scenes:

• UniText/Lit/SDF — SDF text that picks up ambient + one directional light + fog
• UniText/Lit/Emoji — same but for emoji

Assign them via UniTextWorld's material or through MaterialModifier. _LightInfluence controls the mix between unlit and fully lit.

Basic Usage#

Clickable Links#

Markdown Links and Auto-URL Detection#

Inline Objects (Icons in Text)#

Lists#

Apply Color to Entire Text (RangeRule)#

Whole-text via component API#

Language and font switching#

Emoji#

World-Space text#

Custom Material via MaterialModifier#