Skip to main content

Troubleshooting

Text shows literal tags like <Bold>text</>​

Cause: The RichTextBlock is missing the style decorator.
Fix: Add AzimuthRichTextStyleDecorator to the Decorator Classes array on your RichTextBlock.

Cause: The RichTextBlock is missing the link decorator.
Fix: Add AzimuthRichTextLinkDecorator to the Decorator Classes array on your RichTextBlock.

All text renders in the same style​

Cause: The DataTable is missing rows for the tag names the parser emits.
Fix: Ensure your DataTable has rows matching the default tag mapping (Bold, Italic, Code, Header1, etc.). Missing rows fall back to Default.

Some characters appear as boxes​

Cause: The font doesn't support those Unicode characters and the sanitizer doesn't have a mapping for them.
Fix: Use the Sanitize Unicode Symbols function (or Convert and Sanitize Markdown). If specific characters are still showing as boxes, they may be uncommon symbols not yet in the mapping table.

Code blocks don't look different from regular text​

Cause: The Code and CodeBlock rows in your DataTable are using the same font as Default.
Fix: Set the Code and CodeBlock rows to use a monospace font (e.g., Courier New) and a distinct color (e.g., Light Green or Cyan).

Strikethrough text looks like normal text​

Known limitation: UE's FRichTextStyleRow does not have a native strikethrough property. The Strikethrough style is applied via the DataTable (typically a muted gray color to suggest struck text), but no line is drawn through the text. This is a Slate rendering limitation, not a parser issue.

The plugin doesn't appear in the Plugins list​

Fix: Ensure the AzimuthMarkdownParser folder is directly inside your project's Plugins/ directory. The folder must contain AzimuthMarkdownParser.uplugin at its root.