It was first seen on the Developer server and reported there during testing. It was supposed to be fixed...and I think it may have been, at least temporarily. That said, once those updates/changes were pushed to the Live/Production servers it seems to have crept back in occasionally. I think it has something to do with a new added "custom roll" parsing feature. As a workaround, try adding a space in front of your "=" in the table roll portion of your macro, like so; /w Vega &{template:default} {{name=a rumor }}{{ =[[1t[rumors]]]}}}