My game group is loving the bot so far! However, bug report: we just rolled an 11 on a 1d10 sbr check? The person rolling had to try twice and got a "This application did not respond" the first time, which may have been related or may not.
2 years ago(+1)
This was, in fact, purely the result of me accidentally telling Sparks to roll a d12 for these instead of a d10; that has been fixed as of posting this comment, so you should be good to go. I'm unsure about how the "did not respond" error came to be; it's possible it might just be an error on the host's end. Please let me know if it continues to be an issue, or if you find specific conditions that can reproduce it!
2 years ago(+1)
Thanks so much! This has now been fixed as well. As a heads up, Sparks currently responds with a somewhat generic message for 0d SbR rolls because the various SbR systems are somewhat inconsistent about how they deal with such things; this might be patched in a future update if the scene settles on something concrete.