Possible issue with nesting macros

Hi, I'm fairly new to Roll20 (thank you for some great software!) and am not certain that what I'm reporting is a bug, but it does seem a bit "off" for how the macros work. I have a Dice Roller nesting macro that I picked up from a tutorial video. When I click the button that appears on my macro bar, it calls up a box in the text sidebar where I can click other buttons connected to dice rolling (one to roll a d4, one for a d6, and so on). The roller has worked fine for weeks, but I've found that if I try to make this macro available to the players in my game (by choosing the option in the macro setup to let all players view it), they cannot click on the buttons; if I remove the player permissions, the macro no longer works for me (the GM) either, beyond appearing in the text box (the buttons can no longer be clicked). In order to fix this, I've had to set up the macro all over again from scratch. I tried to duplicate the issue, and the same problem occurred. I've found a workaround that works better for me so I'm not trying to find a correction for myself, but I thought I'd report it in case this is an actual issue. I'm using Roll20 on the latest version of Firefox, with the latest updates to Windows 10.

Hi, Jason D. It sounds like the macro might use Advanced Usage for Roll Queries , which states: At this time, reopening a Macro saved under the Collections tab of the Sidebar causes HTML entities within to be reverted; if the Macro is then saved, so are those reversions. This behaviour is not present within Abilities . Does this sound like the issue you're experiencing?

As an addition to what Silvyre said, it sounds like the roller is using the  API Command Buttons to initiate rolls via the advanced syntax at the bottom of the wiki page. This does have the same problem as the advanced usage for roll queries that he linked to above as it also requires html replacement to function correctly. It'd help to determine if this is a bug or not if you could post the macro code.

Hi Silvyre and Scott C., thanks for your replies. Silvyre, what you posted about Advanced Usage for Roll Queries certainly could be the issue. It's possible that I messed with something (or even tried to and then corrected it), then clicked save and messed the whole thing up. Without any further problems, I'm going to assume that you're correct. Thanks for the heads up. Scott C., thanks for the further explanation; since it's also linked to what Silvyre said, it sounds likely that that is the problem. Is it still worth looking at the macro code if things seem to be working fine, and would posting it as it's written cause any problems with how it appears here? I followed your API Command Buttons link and those characters are the same kind of characters that this macro code uses, which also makes me think that you and Silvyre found the issue (which is not a bug, if I understand both of you correctly). To both of you, thanks again for your time.

Yep, if that's what is in the code and you had it saved as a global macro, the problem was that the html entities got parsed when you saved the macro with your changes for players.