Text Animator tags using square brackets do not accept modifiers.

[pigggo]

What is the current behavior?

Text Animator tags using square brackets (ie. [rainb]) do not accept modifiers. Replacing the square brackets with angle brackets fixes the issue, but makes formatting less apparent and results in a warning.

Please provide the steps to reproduce, and if possible a minimal demo of the problem:

1. Add a modifier to a Text Animator tag in a Yarn Script, using square brackets.

What is the expected behavior?

Modifiers like a & s should be processed in the same way they are when wrapped in angle brackets.

Please tell us about your environment

• Operating System: Win 11
• Yarn Spinner Version: 3.2.4
• Extension Version: 3.2.113
• Unity Version: 6000.3.17f1

Other information

Add tags

Core, Text Animator, VSCode

[TheMartianLife]

This is by design, as anything in square brackets is processed by Yarn Spinner with the assumption that it will be Yarn Spinner markup. To enable the feature you ask, we'd have to disable any validation of Yarn Spinner markup tag content, which would doubtless result in the much more common case of people mis-typing a YS tag going undetected.

However, you can use the Yarn Spinner markup syntax in a way that it is compliant with both and YS will just pass the content through its markup system and onto Text Animator. This requires using [commandName=paramaterValue] or [commandName parameterKey=parameterValue] syntax. For your example, I believe that would look like [shake amplitude={a*2} speed={s*2}], but I only glanced at the TA docs so you'll have to double-check me.

That said, if you say that using the angle brackets instead (which makes the markup skip YS processing and go straight to TA) "makes formatting less apparent and results in a warning", there may be something we can do about that part to make it more friendly to use where desirable. I assume the less apparent part is because it doesn't syntax highlight? And what is the warning?

[pigggo]

Hi! Just tested the [commandName=paramaterValue] fix, and that seems to work for setting the parameters (ie. [shake a=2 s=10]) but not for multiplying the base like in the default Text Animator syntax. As for it being less apparent, yes, just due to lack of highlighting. I just did a little test and found that there are two warnings that stem from using the Text Animator syntax, attached below.

if at the end of a line:

if at the start of a line: