(DerQualle) text formatting not applied through data script

[timber osprey]

Hey, im trying to announce some text which I have defined in a data script, but my formattting like <n>,<&5> etc is not being applied but also announced.
This is my script:
https://paste.denizenscript.com/View/108347
And the output in the chat is:
<&5>This is a great announcement! Type:<n><gold>/checkpoints<n><&5>to see how many points you have.

How can I fix this? I bet there is a tag for it 😄

[full prairie]

(DerQualle) text formatting not applied through data script

[full prairie]

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

[bold thorn]

!t parsed_key

[olive mirage]

Cannot Specify Searched Tag

Multiple possible tags: <ScriptTag.parsed_key[<key_name>]>, <yaml[<id>].parsed_key[<path>]>.

[bold thorn]

!t ScriptTag.parsed_key

[olive mirage]

Tag: <ScriptTag.parsed_key[<key_name>]>

Returns the value from a data key on the script as an ElementTag, ListTag, or MapTag.
Will automatically parse any tags contained within the value of the key, preserving key data structure
(meaning, a tag that returns a ListTag, inside a data list, will insert a ListTag inside the returned ListTag, as you would expect).

Returns

ObjectTag

[bold thorn]

Alternatively

!t parsed

[olive mirage]

Cannot Specify Searched Tag

Multiple possible tags: <ElementTag.parsed>, <ScriptTag.parsed_key[<key_name>]>, <yaml[<id>].parsed_key[<path>]>.

[bold thorn]

!t ElementTag.parsed

[olive mirage]

Tag: <ElementTag.parsed>

Returns the element, with any contained tags parsed.
WARNING: THIS TAG IS DANGEROUS TO USE, DO NOT USE IT UNLESS
YOU KNOW WHAT YOU ARE DOING. USE AT YOUR OWN RISK.

Group

conversion

Returns

ObjectTag

[timber osprey]

thats the one. Thank you very much!

[bold thorn]

For data scripts, use .parsed_key

[timber osprey]

ok 🙂

[bold thorn]

Since it does should not use user-input.

[vernal mesa]

Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

@timber osprey

[rocky hinge]

i would highly suggest using

!t parsed_color

[olive mirage]

Cannot Find Searched Tag

Unknown tag.

Possible Confusion

Did you mean to search for elementtag.parse_color?

[olive mirage]

Tag: <ElementTag.parse_color[(<prefix>)]>

Returns the element with all color codes parsed.
Optionally, specify a character to prefix the color ids. Defaults to '&' if not specified.
This allows old-style colors like '&b', or Essentials-style hex codes like '&#ff00ff'
See also !tag ElementTag.parse_minimessage

Group

text manipulation

Returns

ElementTag

[rocky hinge]

this instead

only relegate it to colors, and using specific find-replace for other tags

[deep jolt]

wot

[rocky hinge]

?

[deep jolt]

Why would you do that on a data key

That's doesn't take user input

It's not parsing chat

[rocky hinge]

i prefer to stay on the safe then sorry side, for when i decide to use the same system but for arbitrary stuff. i guess can be personal preference in this case ¯_(ツ)_/¯

[deep jolt]

If you take user input, yeah it makes sense to not parse any tag they yeet into it. But if you do not, parsed_key is totally fine here.