Currently, when 3D dice are rolled via API, their results are not retained and the API just rerolls them in the background. Being able to use the API at the same time as 3D dice without worrying about what I actually rolled would be awesome.
I think I would rather be able to show a fake 3d dice from
the API that rolls like a normal one but shows a number specified in the
function call, letting you use the already available roll functions but represented
as 3d dice on the table.
The problem with that is the 3D dice are rolled with a physics engine, so telling it to roll a specific number would probably be a lot harder than just getting the number it rolled. The ideal solution would be to modify the current methods to take 3D dice into account so if they're used, the method waits to collect the result, and if they're not used then they roll like they do now.
Well, technically, you could run the physics simulation, then set the faces such that the correct number is showing at the end, then play the physics simulation back for display. (That's how we'd do it in the video game industry. =D)
In <a href="https://app.roll20.net/forum/post/2220114/client-side-3d-dice-dont-show-in-api-commands/?pageforid=2223514#post-2223514" rel="nofollow">https://app.roll20.net/forum/post/2220114/client-side-3d-dice-dont-show-in-api-commands/?pageforid=2223514#post-2223514</a> , Riley suggested to provide the API with some "3D Dice replay" method, so that when the API rolls a dice, it has the option to show the corresponding 3D roll. I think that would solve the issue nicely.