Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

Macro Generating avatar name on every line in chat

Macro stopped function as expected (avatar every six lines or after emote) without changing the Macro at all. This change occurred since I last touched the campaign and made the macro on Jan 22nd. Macro in question (unchanged between different results): [[(2d6-6?{Mod with +/-|+0})/4]] Damage [[1d?{Damage|10}]] [[(2d6-6?{Mod with +/-|+0})/4]] Damage [[1d?{Damage|10}]] [[(2d6-6?{Mod with +/-|+0})/4]] Damage [[1d?{Damage|10}]] [[(2d6-6?{Mod with +/-|+0})/4]] Damage [[1d?{Damage|10}]] [[(2d6-6?{Mod with +/-|+0})/4]] Damage [[1d?{Damage|10}]] [[(2d6-6?{Mod with +/-|+0})/4]] Damage [[1d?{Damage|10}]] This generate the 'bad' output every time regardless of where i put the macro despite it working before I have cleared the chat log (i'm the GM) as i know it can get wonky, but it made no change. The effect is persistant for every used macro, and is cross campaigns. Macro now produces this as a result: Previous working variation: (far more legible)
Macros seem to break down after the second line [[2d6]] [[2d6]][[2d6]] versus [[2d6]] [[2d6]] [[2d6]]
Fully reloading the we page will cause it to re-render in proper form. Which leads me to beleive that it is some type of issue with my browser: System dump for reference: OS Type OS Version Browser Type IP Address Javascript Enabled Cookies Enabled Color Depth Screen Resolution Browser Window Size Flash Version User Agent Windows Windows 8.1 Chrome [[REDACTED]] Yes Yes 24 1600 x 900 1234 x 717 20.0.-1 Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36
Hey, wyatt w. Thanks for your bug report! I've brought this thread to the attention of the Roll20 Dev Team, who will take a look.
I think this should be fixed now. Thanks!