In foundry 1.9, the Roll object's roll() method was converted to an async method that returned a Promise<Roll> instead of just a Roll. Correcting the issue just involved calling .then(resultingRoll => {...}) to let the script access the result of the Roll object so it could call Roll.toMessage() (instead of calling Promise<Roll>.toMessage(), which is what's been generating the UI error we've been seeing).
This is a fix for issue [65]
In foundry 1.9, the
Roll
object'sroll()
method was converted to anasync
method that returned aPromise<Roll>
instead of just aRoll
. Correcting the issue just involved calling.then(resultingRoll => {...})
to let the script access the result of theRoll
object so it could callRoll.toMessage()
(instead of callingPromise<Roll>.toMessage()
, which is what's been generating the UI error we've been seeing).