Alright, after some further investigation and tests, I may have found out why this error was occuring as well as a fix for it. Here is the original macro, a Melee roll: #Melee /em @{selected|token_name} attacks! (@{selected|token_name} uses no AP.) ► MELEE /roll @{selected|BODY} + @{selected|Melee} + @{selected|WeaponMEL} The @{selected|Melee} field referred to a attribute whose information was left blank, assuming the player wouldn't have put any points/dice into it. As a result, while the appropriate dice were rolled, there appeared to be some sort of chat error displaying the results, probably due to the blank information field. (It would've ended up looking like this in the chat had it possibly worked: d4 + + d4.) This was confirmed with removing information from the same general field for a Ranged macro I had set up. The same error then occurred for that roll. The easiest way to remedy this was to simply provide a value of 0 to the information field in question. I was under the assumption that the system would have assumed an automatic 0 for any blank attribute field.
