Text Display Dialogue
Official compatibility
| Element | Reference |
|---|---|
TypeWriter | Required. Use the official TypeWriter release supported by the extension release. |
| Related extensions | Install the related extensions listed on this page before using entries that depend on them. |
- Voxel Store — Available on the BTC Studio Voxel store.
The TextDisplay Dialogue Extension transforms chat interactions into immersive, floating 3D text in the game world using Minecraft's TextDisplay entities.
Features
- World-Space Rendering — Float text above characters or points.
- Dynamic Animations — Typing effects, billboards, and scaling.
- Interactive Options — Clickable floating menu choices.
- Performance — Client-side packet entities (zero lag).
Entries
- Dialogue — Spoken Dialogue: Simple speech bubble. Interactive Option: Choices menu. (two same entries with one for world position and one for player relative position)
- Cinematics — Spoken Cinematic: Timeline-based dialogue.
User guide
- 1. Explore Entries — This extension provides the following entries. Add them in your Typewriter page to get started: - spoken - option - spoken_cinematic
Interface Variables
| Placeholder | Description |
|---|---|
%typewriter_textdisplaydialogue_timer% | Remaining dialogue time. |
Troubleshooting
The extension is not visible
Check that the installed release matches the supported TypeWriter release and that the related extensions listed in the compatibility section are present.
An entry is missing
In the Typewriter Web panel, use the Search bar or the + button to find or create the entry with its exact identifier. Entry IDs and field names are case-sensitive; do not translate them.
The entry saves but nothing happens
Check that the entry is connected to the trigger, command, objective, event, or menu interaction required by its type. Test with optional permissions and criteria removed, then add them back one at a time.
An integration does not work
Verify the dependency and version shown in the extension card, then check the server log for the first error. Do not replace a missing dependency with a similarly named plugin unless the extension source explicitly supports it.