GoDice v2.0 compatibility (Foundry v12)

[digitalshadowhawk]

Not sure if this is an issue with Unfulfilled Rolls or with GoDice Bluetooth Dice, but when I go into the dice configuration windows in Foundry v12, GoDice doesn't show up as a dice provider. I did notice in the console for Foundry that fulfillable-roll.mjs and unfulfilled-rolls.mjs both use deprecated features.

Additionally, the latest version of GoDice allowed on Foundry v11 (which still works with Unfulfilled Rolls) is 1.6, but the minimum version available for Foundry v12 is GoDice 2.0. Looking at their github, it looks like they rewrote their resolver for v12, so you may have to do the same.

[darkwon]

I noticed this as well. It appears @digitalshadowhawk that FoundryVTT handles Bluetooth rolls directly now. Open Configure Settings > Core >Configure Dice and set the Dice provider to Go Dice / Pixel / Foundry or whatever you are using.

[coffiarts]

Thank you very much, @darkwon - saved my life.
I was having the same issue as @digitalshadowhawk since v12.
It's still confusing though. One should mention that you also have to clear existing provider settings from the Unfulfilled Rolls settings. Otherwise you get weird effects, with additional "zombie rolls" being added to you intended roll.

[coffiarts]

Or to be more precise: With the new change in v12, shouldn't GoDice now work even completely without Unfulfilled Rolls? Or am I wrong?
I ran a test and completely disabled UR, and my GoDice are still working.

[cclloyd]

I noticed this as well. It appears @digitalshadowhawk that FoundryVTT handles Bluetooth rolls directly now. Open Configure Settings > Core >Configure Dice and set the Dice provider to Go Dice / Pixel / Foundry or whatever you are using.

Not only did this fix it, but for my PIxel dice, I didnt even need this module anymore. Only the pixel module to add the dice.