Possible 3d Dice bug/issue

I just pushed out an update that should fix this. See here: <a href="https://app.roll20.net/forum/post/1692467/3-slash-10-update-of-holding-is-live/#post-1722379" rel="nofollow">https://app.roll20.net/forum/post/1692467/3-slash-10-update-of-holding-is-live/#post-1722379</a>

GenKitty said: The update you released does not work as described. I just tested, three people each rolled API-spawned dice, that only I should have seen (as the GM). Everyone at the table saw all the dice that were rolled. And of course, this still doesn't help in the case of powercards, where *only* the GM should see the diceroll, regardless of who triggered it. But one step at a time, I guess. :) I don't think I said anything in the update about API-related features. What exactly do you mean by API-spawned dice? Dice that are being created in an API script via sendChat()? Or do you mean that there are inline rolls in a macro that are being sent to the API? It would probably help if you could give a specific example.

That's strange, this isn't the behavior I'm seeing at all. In fact, I'm seeing that no one sees the 3D Dice roll for that macro now (including the person who originally rolled the dice). I simplified it down to: !power --whisper|GM --Result| [[1d20]] Another thing you might do is something like: !test [[1d20]] Just to make sure it's not something the PowerCards script specifically is doing. With the !test command I would basically expect nothing to show up on the screen (since there is no API script backing it), but the dice actually do get rolled (although, again, I'm not seeing them) so it's a good test case for this. Is there anything else you're doing besides just entering that command into the text box? Are you using API Chat Buttons, etc?

Okay, I've tracked down the issue. It seems to be happening with multi-command macros, where inside the macro you are mixing things that everyone can see (that emote) with things that only some players can see (like a whisper or an API script). For example, this also triggers the issue: /me Test /w gm [[1d20]] But this works as expected: /w gm Test /w gm [[1d20]] I'll work on a fix today.