Why can we not use 3d dice with API scripts, or, why can we not use functions in macros like we can in API's!!

I know the facts that API calculations are going on in the background and 3d dice rolls happen in the client browser, blah blah, but seriously, there should be a way by now to integrate the function of the 3d dice to conditionals and the like. Many people like the dice, and yet to do some of the things GM's want require calculations are such, especially when playing one of the not supported games on here (a.k.a. EarthDawn). The macros are supposed to allow us to customise things, but with such limited functionality, you gave us scripts...But these should not then be limited in ways the alternative way (which is more limited) is...  Please do something about this.

I agree, Everyone that uses this service probably uses the 3D dice! Also when are they going to fix the black dice so you can see the numbers so it can be used as a color?

The Suggestions forum is where you want to go. Maybe this one suits what you want?: <a href="https://app.roll20.net/forum/post/1239981/obtain-3d-dice-results-for-api-usage" rel="nofollow">https://app.roll20.net/forum/post/1239981/obtain-3d-dice-results-for-api-usage</a>

Depending on what you want, the API can use 3d Dice, it just requires handling in the API script and there are some limitations on how you do it. I expect the reason the API doesn't generally use 3d Dice is how long it takes, combined with how many times it would need to roll.&nbsp; For the Tagmar script, I recently added rolling 3d Dice, so it's fresh in my mind.&nbsp; The API must wait for the dice to finish rolling, which means it must be written in a way that it can be interrupted and resumed later.&nbsp; That's not nearly as trivial as it may sound.&nbsp; Tagmar is just rolling the dice once, but many scripts I've written would be rolling several 10s or 100s of times. If there's a script that you want to see 3d Dice in, I suggest opening a specific post in the API forum to ask about adding support.