You're correct in that that is pretty much how Roll Templates are nested within a Roll Query . However, you're not doing that here—there is no Roll Query in your macro, and hence no reason for HTML entities to be used. (In this thread , it was necessary to use HTML entities because much of your Roll Template was nested within your ?{Augmented?} Roll Query.) As an aside: one should not replace the syntax of Attributes/Abilities with HTML entities due to the way the order of operations works (Attributes/Abilities are expanded before Roll Queries are executed, i.e. before the syntax has a chance to become problematic to the Roll Query). Replacing the syntax of an Attribute call will, under most use cases, cause that Attribute call to break. See: Advanced Usage for Roll Queries