@ is one character that you should not have to ever replace within a Roll Query (although it is a replacement you'll usually want to make when dealing with API Command Buttons). Rest assured, though, that line breaks work fine within Roll Queries. Note that you will not be able to subject @{selected|token_name} to character replacements: Advanced Usage for Roll Queries said: Due to the order of operations , @{Attribute}, %{Ability} and #Macro calls are converted to their assigned values
before Roll Queries are executed. That is to say, the vertical bar and
closing brace characters that exist as the syntax of Attribute and
Ability calls are replaced before those characters are able to prove
problematic to a Roll Query that they are nested within. On the flip
side, if the assigned value of a nested Attribute, Ability or Macro
contains any problematic characters, that nested item will cause its
Roll Query to break as surely as if that item's assigned value was
inserted directly into its Roll Query in place of its call. So, if the
assigned value of your nested Attribute, Ability or Macro does
contain problematic characters, consider replacing any or all instances
of that nested item's call with that item's assigned value, and then
subjecting that assigned value to the above character replacements. All
said, subjecting any Attribute, Ability or Macro calls to any
character replacements will, under most use cases, cause that call to
fail!
