Reuse Your Work

Profiles

A Profile is the best home for defaults shared by many text objects, including default effects, typewriter behavior, and how direct TMP writes are handled. Assign a profile to a prefab or scene object, then keep only meaningful local overrides.

Profiles collect the defaults that should stay consistent across a game or feature.

Project and shared settings

Project Settings control global defaults, markup syntax, the effect catalog, and motion policy. Shared Settings are useful when several objects should point to one reusable configuration. Clear an assigned profile whenever you need to return to complete inline control.

What you can create

• Profiles and Shared Settings
• Typewriter Presets and Typewriter Motion Presets
• Character Timings and Word Timings
• Markup Syntax and Tag Expansion Sheets
• Audio Sets, sound actions, and input actions
• Effect Curves, including Linear, Bounce, Step, Hold, and Custom, plus Once, Loop, finite Ping-Pong, and Weighted playback assets

Choose the right reusable asset

• Profile: complete defaults shared by many Text Studio objects.
• Typewriter Preset: reveal, timing, motion, loop, wait, skip, and hide behavior.
• Typewriter Motion Preset: reusable Reveal or Hide motion stack.
• Character Timings or Word Timings: pacing rules only.
• Composed Effect: ordered reusable visual treatment.
• Effect Curve: reusable progress shape.
• Effect Playback: reusable temporal envelope.
• Markup Syntax: project authoring delimiter policy.
• Tag Expansion Sheet: project vocabulary that expands into reviewed markup.
• Audio Set: reusable glyph clips and marker cues.

Use shared assets for decisions that should remain consistent. Use Inline settings for a deliberate local exception. When a Profile is assigned it temporarily supplies profile-owned defaults, but Text Studio retains the full local configuration and restores it when the profile is cleared.

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.