So I think there are two sides to this going on.
1) API-side: The API can now generate 3D Dice rolls using sendChat(). There's no interaction (in terms of the user "rolling" them) client-side, but you can do that now and see 3D Dice get rolled.
2) Client-side: However, the way that many API scripts (including PowerCards) works is by letting the dice rolls happen first on the client-side, and then taking the results of those rolls and doing something with them. The way the 3D Dice roller works for rolls from the client is, it does the roll on the QuantumRoll server, and then you won't see the results of the roll until the chat message displays. Since it's an API command, and those messages are passed to the API server instead of being displayed on the client, there is no message displayed, and so the 3D Dice rolls never happen. This (as you said) can lead to confusion because with the new agency feature you are doing something and expecting a result, but it never happens.
Unfortunately, you can't use the new sendChat() supporting 3D Dice function to re-play a 3D roll, only generate new ones.
I guess the two options here are:
1) Just turn off the 3D Dice (agency) features when you are doing API commands, since you will never see the 3D Dice get rolled anyway
2) Play the 3D Dice roll right away when you are in an API command (instead of waiting for a message). The only downside I see with this is that what you see get rolled on the screen may be totally different than the result you get in chat, depending on what the API script you are using does with the dice results.
Thoughts?
