Reuse Your Work
Behavior Profiles
A Behavior Profile supplies opt-in behavior shared by many Text Studio objects. It has three independent domains: Default Effects, Typewriter, and Reactions. Enable only the domains that should be inherited. A dialogue family can share cadence without forcing the same effects, while a HUD family can share finite feedback without changing reveal behavior. Appearance and Writing keep their own authoring owners.
Assign the profile from Content. The component continues to retain its complete local configuration behind every supplied domain. Clearing the profile, disabling a domain on the profile, or assigning a profile that does not provide that domain restores the local behavior instead of replacing it with defaults.
Behavior Profiles do not own project-wide catalogs, markup grammar, renderer policy, or motion policy. Those remain in Project Settings. They also do not own Source. Text Studio keeps the authored line local or under the explicit external text source.
Domain | What the Profile Supplies |
|---|---|
Default Effects | Reusable Reveal, Active, and Hide effects. |
Typewriter | Typewriter settings for reveal and hide timing. |
Reactions | Reusable finite responses to text events. |
Project Settings and Behavior Ownership
Project Settings own global policy: built-in defaults, the effect catalog, Markup Syntax, Tag Expansion Sheets, motion policy, renderer and integration discovery, and validation. Use them for choices that should be consistent even before a scene object or profile is selected.
- Project Settings: global catalogs, syntax, defaults, motion, capability discovery, and validation.
- Behavior Profile: opt-in Default Effects, Typewriter, and Reactions behavior for a group of objects.
- Reusable preset or effect asset: one focused recipe that can be referenced by profiles or objects.
- Component-local settings: the complete authored fallback and the right place for a deliberate exception.
The component has no separate shared-settings source. This ownership model prevents one asset from silently taking over unrelated behavior and makes it clear what returns when an assignment changes.
What You Can Create
- Behavior Profiles with independent Default Effects, Typewriter, and Reactions domains.
- 2D Appearance Styles for persistent layered visual design.
- Writing Styles plus optional Writing Font and exact Phrase path assets.
- Complete Design Presets that assign established assets without adding runtime ownership.
- Typewriter Presets with optional Reveal and Hide effects.
- Character Timings and Word Timings assets.
- Composed Effects, Curve Profiles, and Effect Playback assets.
- Markup Syntax assets and Tag Expansion Sheets.
- Audio Sets, sound actions, custom actions, and input-action mappings.
- Effect Code payloads for reviewed, dependency-aware sharing.
Choose the Right Reusable Asset
- Behavior Profile: opt-in default effects or typewriter behavior shared by a family of Text Studio objects.
- 2D Appearance Style: persistent whole-object paint, edge, depth, surface, editorial, and title-animation layers.
- Writing Style: reveal-driven ink coverage, outline tracing, or authored handwriting with explicit source requirements.
- Complete Design Preset: an apply-once bundle of Appearance, Writing, and Behavior Profile references.
- Typewriter Preset: reveal unit, cadence, motion, loop, wait, skip, and hide behavior.
- Character Timings or Word Timings: pacing and punctuation rules only.
- Composed Effect: an ordered, renderer-aware visual treatment.
- Curve Profile: a reusable normalized progress shape.
- Effect Playback: a reusable time envelope and persistence policy.
- Markup Syntax: the project's delimiter and escaping policy.
- Tag Expansion Sheet: compact project vocabulary expanded into reviewed markup.
- Audio Set: reusable glyph clips, marker cues, and playback policy.
Use a shared asset when the decision should change everywhere that references it. Use Inline settings for one deliberate exception. A Behavior Profile temporarily supplies only its enabled domains; Text Studio preserves and restores the complete local configuration behind them.
Project Settings and Catalog Ownership
Text Studio Project Settings define global defaults, the active syntax policy, project effect and action registrations, tag expansion sheets, motion policy, and runtime loading behavior. Runtime registrations have the highest priority, project entries remain available underneath, and built-ins remain the final fallback.
Effect Code
Effect Code is for portable treatments. Copy from the composer, review the metadata and required dependencies, then import into another project. Conflicting identities are resolved without silently overwriting unrelated assets. Keep package-owned extension IDs namespaced and preserve missing dependencies until their add-on is installed.